Translating the Locale file - EcoSys - Administration & Configuration - Hexagon

EcoSys System Administration

Language
English
Product
EcoSys
Search by Category
Administration & Configuration
EcoSys Version
9.1

Any translation service or software can he used to translate the EcoSys localization file.

EcoSys recommends Phrase.com as it supports:

  • Machine translation using Google, Microsoft, or other services

  • Branching to better control the translation process

  • Managing keys so only keys need to be translated after an upgrade.

  • Allows to perform a full review of machine translations and has a specific feature set to manage them

The following best practices and settings are provided to ensure a successful translation using Phrase.com.

Preserving parameter references and system variables

In EcoSys, parameter references like ‘@=Project’ and system variables like [Minor Period ID] can be used in the column captions and other places that will be translated. When using machine translation, Phrase will try to translate every word, and the translation of these variables will cause issues in EcoSys as they need to be in English and have a special meaning. To avoid translating these types of strings, there are two server settings that can be configured in EcoSys when using Phrase.

The following server settings must be added to the system (not set by default).

server.locale.export.noTranslateDirectiveStart=[NOTRANSLATE]

server.locale.export.noTranslateDirectiveEnd=[/NOTRANSLATE]

When set, the locale file exported from EcoSys will wrap the required strings with NOTRANSLATE, but leaves the text that should be translated unaffected.

Example

Actuals [NOTRANSLATE][Minor Period ID][/NOTRANSLATE]

EcoSys: Change Approval for "[NOTRANSLATE]@=ManualChange[/NOTRANSLATE]“

Phrase will not translate the strings between the tags while translating the other text and will remove the tags when producing the language specific file.

HTML in caption and batch descriptions

For HTML in Captions and batch description, Phrase will translate only the words and leave the HTML content.

Example

This process will set the status of an issue to Closed. Closed issue can no longer be edited .\n<br>\n<br>\n Verify the <b>Project</b> selected below, verify the <b>Issue</b> selected below, enter a <b>Comment</b> to be stored in the log, and <b>Run</b> the process.

Este proceso establecerá el estado de un problema en Cerrado. El problema cerrado ya no se puede editar.\n<br>\n<br>\nVerifique el <b>proyecto</b> seleccionado a continuación, verifique el <b>problema</b> seleccionado a continuación, ingrese un <b>comentario</b> que se almacenará en el registro y <b>ejecute</b> el proceso.

Screen Layout HTML Panels

Phrase will attempt to translate HTML panel content in our locale files. Depending on the complexity of the HTML document, it can be successful or might leave it as ‘not translated’. HTML panel content can be wrapped in NOTRANSLATE using the server setting server.locale.export.doNotTranslateSLHtmlContent.enabled (Default false).

Importing a locale file to Phrase

When importing a locale file to Phrase, the following options must be set:

  • File Format – Java Properties (.properties)

  • Language – Use existing and select en

  • Encoding – UTF-8

  • Check ‘Use pre-translation’

Downloading a locale file from Phrase

When downloading a locale file from Phrase the following options must be set

  • File Format – Java Properties (.properties)

  • Uncheck ‘Escape single quotes’

  • Check ‘Omit separator space’

  • Check ‘Include empty translations

    • Select ‘en’ as the fallback language

    • Check ‘Include translated keys’

  • Check ‘Include unverified translations’

  • Check ‘Escape meta-chars’

  • Set encoding to ‘UTF-8’

The downloaded locale file must be renamed to a proper java locale.