Search Online Knowledge Base
        Support Home     TRADOS Web Site     Contact Us  

Frequently Asked

Search the
Knowledge Base

Support Information

What's new in



Feedback on
the Support Centre


> Article View

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)


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.


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.


Set the default system locale of your computer back to US English.

Then, change the registry of the computer as follows:

  1. From the Start menu, select Run.
  2. Type in "regedit" (as shown, without the quotes). The Registry Editor opens.
  3. Locate the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage
  4. In this key, highlight the string 1252 (on the right-hand side in the registry editor).
  5. Right-click on the string, and select Modify.
  6. 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).
  7. Click OK to accept the change, and exit the Registry Editor.
  8. Reset the system default locale to the Eastern European Language and the problem of corrupted extended characters should now be resolved


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

© Trados GmbH 2000 - 2001. All rights reserved.
last update: 07 August 2001
TRADOS makes no representations about the suitability of the information contained in this document and related graphics for any purpose. All information in this document is provided "as is" without warranty of any kind. TRADOS and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall TRADOS and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use of information available in this or related documents.
The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. TRADOS and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.