Translations

We use OneSky to manage translation of all the i18n strings.

How does it work?

All of the User Interface (UI) for OneBody is written in a way that English text is pulled from these files. Likewise, if a different locale is selected, then other strings are selected.

That means translating the UI is a matter of creating a set of files for a given language.

To make this a bit more manageable, we use Translation.io to track all these different strings.

When a string is changed in English, then we update the English strings in OneSky, and matching strings in other languages are marked as "outdated".

Translators

Here is a list of translations in the works:

Language/Locality	Translators
Afrikaans	https://github.com/attieretief
Chinese (Simplified)	https://github.com/oppih, https://github.com/qijun-jiang
Czech	https://github.com/jsuchome, https://github.com/josefkauc
Danish	https://github.com/khebbie
Dutch (Netherlands)	https://github.com/stephanvd
French	https://github.com/MaximeGir
German	https://github.com/metaxy, https://github.com/pgeorgi
Japanese	https://github.com/juanpaulo
Portuguese	https://github.com/gustavobim, https://github.com/theprogramer
Romanian	https://github.com/georgebejan
Russian	https://github.com/rosko
Spanish (Mexico)

How can I help?

Let us know which language you'd like to help with! Join the #onebody channel on Slack Chat, send us a tweet on Twitter, or send an email to the Google Group