Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Lokalise is the Translation Management System used at RBI for handling User Interface strings translation.

Access

If you are a translator, FZ owner, or content manager and want to contribute translations for your market, please reach out to the CSM team to gain access rights.

Projects

Once your user account has been provisioned, logging in to Lokalise will list all the projects you have access to.

The international mobile/web app is handled in the Intl Whitelabel Consumer App project.

Working on Translations

Choose the Right Language

Unless you are handling multiple languages across regions, you always want to work on regional language variants, i.e. always choose “Spanish (Spain)” over “Spanish”.

In some particular cases, markets can share common strings via a “parent” language.

For example, German (Switzerland) and German (Germany) share common translations via the German language.

When making translation updates to a regional variant that contains a parent language, please note any subsequent changes to the parent language won’t be propagated to the regional variant.

Example:

  • German, keyName: “Translation for parent German language”

  • German (Switzerland), keyName: “Translation specific to German in Switzerland”

Later…

  • German, keyName: “Translation for parent German language” → “Updated translation for parent German language”

  • German (Switzerland), keyName: “Translation specific to German in Switzerland”

Editor Environment

Lokalise has a full-fledged translations editor, and covering how it works is out of the scope of this document.

To learn more about specifics on using the translations editor, please head to https://docs.lokalise.com/en/articles/2967175-onboarding-guide-for-translators.

Syncronization

Once translations have been edited and saved via the Lokalise editor, they will make their way to the application automatically.

String updates are synchronized twice per day, at 10:00 and 22:00 UTC respectively. After the updates have been published, an application restart or website refresh is required to get the up-to-date contents. String updates are only propagated to the latest application version.

  • No labels