Summary
Translation Services have been updated to include the following new features and enhancements:
- Ability to translate a List Of Values (LOV) using an asynchronous translation service.
- Increased functionality when searching for translation status in both the workbench and the Web UI.
- A new asynchronous translation service option (File Exchange Service).
- Addition of 'List Of Values' option in the Change Translation Setup dialog window.
- Addition of Asynchronous Translation Message Processor, allowing for batching translation requests.
- New mechanism to only send LOV values that require translation.
Details
Translating List Of Values via an asynchronous translation service
The asynchronous translation framework has been expanded to include support for a List Of Values (LOV), bringing the asynchronous translation capabilities in line with current non-asynchronous translation functionality.
For more information on asynchronous translations, see the Asynchronous Translations documentation here. For more information on translations, see the Translations documentation here.
Searching for translation status within the workbench and the Web UI
Users now have the ability to search for an LOV based on the translation status of the LOV values. Previously, the translation search was limited to only those LOV values that had not been translated. Now, when ‘List Of Values’ is selected from the ‘Type’ dropdown on the Translation Status search criteria selector, all language and translation status parameters are available. This change brings LOV into closer alignment with the translation capabilities that already exist for other kinds of data in STEP.
For more information on the searching for translation status, see the Searching for Translation Status topic in the Translations documentation here.
In a related update, users are now able to search for the translation status of products, classifications, assets, attributes, and LOV in the Web UI using the new Translation Status search criteria. Accessible in the Advanced Search screen, the Translation Status search criteria enables users to create granular searches for objects with any of four translation statuses ('Re-Translation Needed,' 'In Progress,' 'Up to Date,' and 'Not Translated'). The searches can be further refined by applying additional criteria like object type and language (source or target).
For more information regarding configuring the Advanced Search screen with Search Criteria, see the Advanced Search Initial Configuration topic in the Advanced Search topic in the Web User Interfaces / Web UI Setup and User Guide documentation here. For more information regarding translations, see the Translations topic in the System Setup / Super User Guide documentation here.
File Exchange Service
The File Exchange Service is a new asynchronous translation service that can be used to manually export / import translation files into folders; no translation service API is needed. This feature is an excellent option for users that do not currently have a contract with any of the translation services currently supported, such as Lionbridge and SDL, but need a way in which to send and receive files for translation.
For more information regarding the File Exchange Service, see the Configuring an Asynchronous File Exchange Service topic within the Asynchronous Translations documentation here.
List Of Values option included in the Change Translation Setup tool
List Of Values has now been added as a selectable option within the Change Translation Setup tool. This allows users to be able to update / override the translation setup for a List Of Values. For more information, see the Changing Translation Status and Setup topic in the Translations documentation here.
Asynchronous Translation Message Processor
The new Asynchronous Translation Message Processor plugin will allow those users with the async-translation component installed in their system the ability to schedule a translation job that contains a list of objects that need translation. Scheduling is possible via a bulk update that is executed on a Collection that contains a number of objects. The bulk update is configured with a business action that generates a derived event for each of the objects in the collection.
For more information on the new Asynchronous Translation Message Processor, see the Asynchronous Translation Message Processor Processing Plugin Parameters and Triggers documentation here.
Only send LOV values that require translation
LOV submitted by either asynchronous or non-asynchronous translation services will now only send those LOV values that require translation. When an LOV is selected for translation, the new logic will (for each of the values in the LOV) compare the current source value with the last successfully translated source value. If there is a difference, the LOV value will be tagged with <TranslatableText>. The image below shows an example of a LOV taken from an XML file, with the <Translatable Text> tags highlighted for the value within the list.
To access and use the Asynchronous Translation Message Processor, the 'external-async-kernel' add-on component must be activated on your system in addition to the normal update procedures for 9.2 and any other activation noted above.
To access and use the File Exchange Service, the 'file-exchange-translation' add-on component must be activated on your system in addition to the normal update procedures for 9.2 and any other activation noted above.
To ensure that asynchronous or non-asynchronous translation services only send LOV values that require translation, the 'translation-extension-lov' add-on component must be activated on your system for 9.2 through 9.2-MP2 in addition to the normal update procedures and any other activation noted above. For those on 9.2-MP3 (and beyond), the functionality is built into baseline and no separate add-on component installation is needed for this particular functionality.
See your Stibo Systems’ account manager for details regarding any applicable licensing for translation services.