internationalization

I am trying to use I18n.transliterate to "normalize" some text with accented characters so I can analyze and compare it with different languages. However, when using this method the following error pops out I18n::InvalidLocale: :en is not a valid locale from /home/xxx/.rvm/gems/ruby-2.1.5/gems/i18n-0.7.0/lib/i18n.rb:284:in `enforce_available_locales!' from /home/xxx/.rvm/gems/ruby-2.1.5/gems/i18n-0.7.0/lib/i18n.rb:235:in `transliterate' from (irb):2 from /home/xxx/.rvm/rubies/ruby-2.1.5/bin/irb:11:in `<main>' I have made some searches for this problem and I only found solutions related to

I have one string that can be translated in varius part of my code in two different way. Now if Use django-admin makemessages -l it I get in django.po this: #: pingapi/ping.py:17 pingapi/nots.py:10 msgid "may" msgstr "maggio" But I would want two different translation: #: pingapi/ping.py:17 msgid "may" msgstr "posso" #: pingapi/nots.py:10 msgid "may" msgstr "maggio" If I run django-admin compilemessage with the translation file posted up, I get: Error: errors happened while running msgmerge error 'duplicate message definition' Any Hints? I'm using Django. You can use gettext's context for that

They talk about locale-specific files here http://docs.angularjs.org/guide/i18n but don't mention where to get them (the official AngularJS repo doesn't contain them). So where does one obtain these locale files? You can also get them with bower : bower install angular-i18n It is the official bower distribution that mirrors the files at https://code.angularjs.org/ More info at https://github.com/angular/bower-angular-i18n tenifre Lastest stable version i18n files at here: http://code.angularjs.org/1.0.3/i18n/ You can also find other versions at here: http://code.angularjs.org/ You can also get

I want to make a translation my_translation with an optional parameter. For example: > I18n.t('my_translation') => "This is my translation" > I18n.t('my_translation', parameter: 1) => "This is my translation with an optional parameter which value is 1" Is this possible? Yes, definitely. You just write the translations like this: my_translation: This is my translation with an optional parameter which value is %{parameter} Is the parameter really optional? In above translation, you have to provide all parameters. UPDATE: Sorry, I answered too soon. I don't think it's easy to do. Maybe the

I'd like to internationalize the strings of my view.yml, I can't find how to do this. I have a solution that is bad, in my opinion: metas: title: <?php echo sfContext::getInstance()->getI18n()->__('TITLE'); ?> I'd like to find a way to do it without calling "sfConfig::getInstance()". Is it possible? Never ever use sfContext for I18n in Configuration-Files! In such a case use the setTitle function in the View (not the controller) <?php $sf_response->setTitle(__('TITLE'));?> Since include_title() does not translate what it finds in view.yml, I made this very simple function in my custom helper:

I have a website that will eventually display multiple languages. I notice the common fonts used in web CSS (ex: Arial, Verdana, Times New Roman, Tahoma) and even the newer Vista/Office 2007/VS2008 fonts (Calibri,Cambria, Candara, Corbel, etc) are significantly larger (~350K) than your average (US only?) TTF font (~50k) so these fonts contain most/all the major character sets that common languages (Spanish, French, German, etc) use. My question is, would somebody confirm that these fonts listed above are acceptable for international use of the major (let's say top 8) spoken languages? If so,

I want to do some basic i18n in my application I loaded the i18n plugin (from require.js) to my Application and created a directory nls in which i have several files e.g. project.js I set up the default location in main.js file like config : { i18n : { locale : 'de-de' } } I now want to use the files in my View / Template. Can somebody explain to me how this is done? The templates are setup in one template.js file My View: define(['marionette', 'templates', 'i18n!nls/project'], function (marionette, templates, msg) { return marionette.CompositeView.extend({ template : templates.project }); });