Foreign Language Translation
Following are known issues with the Foreign Language Translation utility:
1) The mechanism that determines when an EM must be rebuilt doesn't always cause EM regeneration at the right time. We're saving 'needs EM rebuild' information in the SysAdmin Application record, but this isn't always propogated down to Applications' Processes, and EMs in need of regeneration can be passed over.
(ECR #4769)
Current Workaround: Any time you make edits to your Language Translation dictionaries, delete all of your Application's EMs, forcing them to rebuild.
2) The 'Language ID' mechanism can cause unpredictable errors. The language ID can be specified in four different places:
Currently, the only place where the 'Language ID' can be specified without causing problems is in the USER record. If you specify a Language ID in any of the other locations, EMs may get rebuilt unexpectedly, or generate unexpected EM generation or runtime messages.
(ECR #4769)
Current workaround: Blank out the 'Language ID' at the SysAdmin, DB, and DB/Appl levels, using 'Language ID' only in the USER record.
3) EM building under foreign Languages can take much longer that EM building under the home language.
(ECR #4769)
Exporting, then re-Importing the Language DDs clears this condition up. It may be a function of Language DDs being stored as variable-length files.
4) Untranslated entries in an Application's Translation tables can "block" translations that would otherwise occur within the SysAdmin Translation tables.
(ECR #5164)
Workaround: If you make an entry into the SysAdmin translation table, delete any corresponding entries in your applications' translation tables.
5) If the translation setup information is changed (either within an application, or when porting a translation over to another machine), the translation hash is changed, and translated entries won't be found and applied to the current application.
(ECR #5165)
'Setup info' is that found in SysAdmin, Language Translation, Languages, on the 2nd screen for each language specified.)
Release 4.1 will have an option that will reset hash values.
Current workaround: Make sure your translation setup information is bit for bit identical when transporting applications, and do not make any changes in translation setup information once your translation process has started.
Comments:
Read what other users have said about this page or add your own comments.
--
ChrisBrower - 2011-06-08