Translate Amahi

We plan to support localization in the upcoming transition to rails 2.3, which has localization support included.

For the time being, here is the en.yml file set of sentences to translate (in a format called yml, ready for rails 2.3).

(that's formatted) the raw file is at raw en.yml

Basically what the translation consists of is this:

• duplicate an original file, change the name to something appropriate (e.g. de.yml for german, fr for french)
• change the strings after the colon to the end of the line for the new language.

That's it! you can do it by cut and paste or with git:

   git clone git://git.amahi.org/amahi.git
   cd amahi/platform/platform/html/config/locales
   cp en.yml yourlocale.yml
   [edit the yourlocale.yml file]
   git commit yourlocale.yml

For brownie points, you can also add those to

 amahi/platform/platform/html/app/controllers/setup_controller.rb

To find the code of your language, please visit the iso codes page Columns 6 is the name of the language *in the native language* (we need that) and column 1 is the ISO code

Please put them here in alphabetical order so that the user can more easily find his/hers!

Here is how to submit a patch directly with git or you can send your locale file by email or post it in the forums or amahi-devel list.

Here is the original localization thread in the forums.

Translation Tips

Do NOT

• Do not translate things inside Template:... because these are variables

{{count}}

• If you see something you do not understand, please let us know, do not change it

Do

• You may want to use the Auto translate links if you feel it helps reduce typing
• Preserve parenthesis and other marks, like period at the end, etc.
• Preserve the intent of the phrase to the extent that you can :)
• Preserve any HTML in the strings (adapt as necessary)
• If you are not too sure (and even if you are), it's a good idea to go to a popular native site for news or email or a portal and see how they login users, how they cover technology and use the words they use there. Try to use a popular site, not a techy site