Skip to content

Translation

Jump to bottom Edit New page
wvengen edited this page Jun 13, 2013 · 19 revisions

Adapting software for multiple languages consists of three areas:

  1. Internationalisation (i18n) - adding support in the software to lookup texts. This is mostly a programmer's job.
  2. Translation - translating texts and phrases to different languages. This is a translator's job.
  3. Localisation (l10n) - supporting different number formats, currencies, date representations, etc.

Translators

You can work on translations using localeapp in project 4867 (sign up to edit). We're working on adding a special foodsoft installation for translation where these changes are immediately visible.

Translating software can be tricky, as texts are often very short, sometimes with an unclear context. Please read the translation notes, and feel free to add to them.

Developers

Translations live in the files config/locales/:lang.yml. For some hints on moving from texts in templates to internationalized texts, please see translating templates.

When adding a translation, please add them to localeapp too. This can be done by adding the keys manually (using localeapp or the web interface), or re-importing the whole file (but DO CHECK that you don't overwrite updated translations in localeapp!!!). Then pull changes so that the files contain what is returned from localeapp, which may have different whitespace and such than your edit. We'd like to keep it clean.

We're discussing about details on doing that on our mailing list. TODO this need to be smoothed out in a no-fail step-by-step flow

Foodsoft translation instance

To aid translators, a foodsoft instance for translators is setup on heroku. We need to solve bug #128 first. (TODO expand this, incl. the launch and update script)

Local foodcoop-specific translations

Foodcoops may use a slightly modified version of foodsoft. They need their own localeapp project and heroku app.

Related links

Add a custom footer
Add a custom sidebar
Clone this wiki locally