ECAP now supports UI Language Management

SELISE deployed a translation tool for ECAP based applications to mitigate the hassle of localization. The upgrade is available for all customers on AWS and will be rolled out over the course of June.

Translations of specific words are often context based, and can only be determined after viewing the entire UI. The word ‘toolkit’ in English can be translated to German as ‘Werkzeugkasten’, or ‘Bausatz’, or even ‘Anwendungssystem’. The translator then has to pick which word is best suited for the application.

Another typical example is the case of a fixed-width button label, where words translated from English to French do not fit the original dimensions. To keep the original button in place, the developer may choose a different French word, perhaps a synonym in order to fit the space.

Translators and developers therefore require tools with which they can collaboratively manipulate and assign translations to specific text elements.

SELISE has created UILM as a built-in CAT (Computer Aided Translation) tool to address the above challenges while offering a self-service collaboration space inside applications for translators.

What can the new UI Language Manager do?

Help translators and administrators manage and incorporate translations without having to go through the hassle of reporting, explaining and documenting translation bugs in issue trackers, language memory tools and spreadsheets.

Help developers of large teams find duplicate keys and gives access to the applications Translation Memory (TM).

Help DevOps work more efficiently prior and after release dates by providing a fully automated continuous integration system to administrators and translators.

How does it work?

The ‘Administrator’ invites ‘Translators’ as users to the software. Translators can make changes and additions to keys within applications. The process is as follows:

Once the user confirms all the additions and changes to individual keys, they click on the ‘Go Live!’ button. ‘Go Live!’ connects the application to the CI pipeline, triggering the creation of a new build for the system. The changes made to localization keys are integrated, without having to involve a developer.

Leave a Reply

Your email address will not be published. Required fields are marked *

+1
Share
Share
Tweet