|
Bug: Characters in Eastern European languages are not displayed correctly in TagEditor and after clean up
Applies to:
TWB - 3, TWB - 5
Environment:
WORD - ANY (ANY)
OS:
WINDOWS 2000 - ANY (ANY)
SYMPTOMS
In matches that are retrieved during interactive translation, extended characters in Eastern European languages like Czech, Slovak, etc. are not displayed correctly in Word and in TagEdito. It is also not possible to type the correct characters in TagEditor instead of the corrupted ones. Also after a cleanup of BIF files, such characters do not display correctly in the target files.
EXPLANATION
The problem has only been reported for US Windows 2000 operating systems with the default system locale changed to an Eastern European language. It occurs with Edition 3 and TRADOS 5. It appears that the operating system is pointing to a wrong code page. The fix below is reported to solve all problems occurring around the special characters in Translator's Workbench and TagEditor Edition 3 and TRADOS 5.
STEPS
Set the default system locale of your computer back to US English.
Then, change the registry of the computer as follows:
- From the Start menu, select Run.
- Type in "regedit" (as shown, without the quotes). The Registry Editor opens.
- Locate the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
- In this key, highlight the string 1252 (on the right-hand side in the registry editor).
- Right-click on the string, and select Modify.
- In the Edit String dialog, change the Value Data to c_xxxx.nls, where xxxx is the value for the code page of your target language. For example, if you target language is Czech, set the value to c_1250.nls (for Greek: c_1253.nls).
- Click OK to accept the change, and exit the Registry Editor.
- Reset the system default locale to the Eastern European Language and the problem of corrupted extended characters should now be resolved
REFERENCE
For a related issue involving damaged font tables in translation memories resulting in similar symptoms, see Troubleshooting incorrect extended characters in translation memory or target segments.
STATUS:
Closed
Article ID: 984
Created: 10/05/2001 05:50:02
Last updated: 10/26/2001 11:24:17
|