![]() ![]() Ask the translator to send a new XLIFF file for the language code.Reasons to use a country-qualified code may be best handled by case #2.) Determine the proper code for the locale.When adding a new, completely distinct locale, we:.Case #2 describes an existing exception, which can serve as a model if we eventually implement others. Mostly, we just ask the translators to provide a new locale, based on our English master ( en-GB). See instead Establish a new translation locale, for initiating a new, separate translation locale. Once you do get the updates arranged, check them in and go through the process to Convey current versions of strings for translation. ![]() Based on the Spanish translation locale file mapping the key "Server changed to ]" to "Servidor cambiado a ) strings, for which see Editing app literals - Details.Spanish rendering: Acerca de SpiderOak Blue These examples embody the essentials, for the impatient. When new locales are added or existing mappings changes, Maintaining Translations from the wrapped text, as keys, to equivalent, translated strings in each of the locale files.Įditing app literals Editing app literals - ExamplesĪdding or editing localized strings is slightly different in code versus in templates, but we use the same approach for both.After which we Coordinate with translators to get corresponding updates to our translations.Any changes to app literals need to be applied to the translations.The following sections are organized around specific app maintenance tasks which involve app literal strings, and describe how to use our localization provisions properly specifically for those tasks. We use html10n.js to implement our app's localization. XLIFF externalization for translator coordination.Receive and incorporate translated strings from translators.Convey current versions of strings for translation.Conveying translation updates to and from the Translators.Register a new translation file in the app's master index.SpiderOak Mobile Client App Localization Maintenance ![]()
0 Comments
Leave a Reply. |