Localizing OnSite

Supported Languages

OnSite supports the same set of languages delivered for Web Central:

  • Chinese Simplified

  • Dutch

  • French

  • German

  • Italian

  • Spanish

For the above six default languages, OnSite users change their device’s language and region. They will then see OnSite in their own language. The date, time, and numeric format will follow the device’s settings.

Recommended Procedure for Other Languages

Note : OnSite does not support right-to-left languages yet as it requires significant development effort.

For non-supported languages, you can work with Archibus Business Partners to localize your language in OnSite (front-end) and Archibus (back-end) and get the strings translated and published.

  1. Business Partners set up the language for their clients by following the instructions described in Adding Languages and Locales to the afm-config.xml File .

  2. Business Partners use the Archibus Localization Kit to localize the strings from the Archibus back-end. This includes messages as well as field names, titles, and enum fields defined in the database.

  3. Business Partners work with translators to localize the OnSite front-end strings.

    • Business Partners send Eptura their request. They include the translator's contact information and the back-end language field (lang_01, lang_02, or lang_03) that they use for their client.

    • Eptura invites these translators to the Crowdin project (free to translators) so that the translators can input the translations for the localized strings. They may ask questions from Crowdin directly if they need to clarify or understand the context of strings.

    • Business Partners review the localized strings to ensure accuracy. Once the localized strings are finalized, Business Partners notify Eptura to verify.

  4. Eptura provides the Business Partners with a pre-release build of the OnSite app to allow them to verify the translations in the app.

  5. Once Business Partners approve the translation, Eptura makes a new official OnSite build (front-end only) and publishes it to the app stores.

Notes

  • When testing the translation, you must set the locale of the approver and requestor to the same locale as the OnSite technician. This ensures that the references to the wr.priority_label field display correctly.

  • When new strings are added to OnSite with each release, Business Partners follow the above steps to get their new localized strings published.

  • If the non-default language has the potential to generate revenue, Eptura might consider adding the language to the default list and then manage the localization internally.