-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translation #99
Comments
You can use l10n.js on osem's strings in order to read the language of the browser and get osem automatically translated to the translated languages on Transifex. |
The "normal" rails translation uses yaml files. http://guides.rubyonrails.org/i18n.html |
Transifex supports yaml files. We have to create the strings in en-US format and send it to transifex. |
This is live now, although broken as it can't read the api key from the config. |
To translation you need to navigate from project's page as following: https://www.transifex.com/organization/opensuse-community/dashboard/osem -> Translation button -> Select language -> Select Resource Assuming you have signed up yourself as a translator for OSEM, to translate in German, for example, you go to: In order for the translations to be visible, they need to be deployed: If we have published translations, we should be seeing a language selector (bottom right corder). |
Works now |
…ob_active_record-4.1.5 Update delayed_job_active_record: 4.1.4 → 4.1.5 (patch)
Setting up translation tool for OSEM.
Transifex is for free for open source projects:
https://www.transifex.com/projects/p/osem
But I have no idea how to produce the initial translation file that must be uploaded in transifex, so that the translation can begin.
Supported formats for translation file:
http://docs.transifex.com/developer/formats/
The text was updated successfully, but these errors were encountered: