You translate a file in Trados Studio. You notice that
If you are aware what character encoding was used when creating the file: When you go to Advanced > Active Document Settings, you notice that the Source Encoding is set to a different character encoding than the file was created with. |
Workaround: Add byte order mark to source fileConvert the source file to an encoding that uses a byte order mark (BOM).Example: You can add a byte order mark to a text file using Notepad++ (third party application):
Note: If you wish to apply this workaround to a bigger number of files or Notepad++ cannot detect the encoding of the file correctly, the OpenExchange application File Encoding Converter may be useful. Workaround: Specify encoding when opening single file for translationWhen opening a single file for translation, its encoding can be specified:
If your target file does not have the desired encoding, you can apply following workarounds instead: Workaround: Specify target file encoding in Trados Studio
Workaround: Re-save target with desired encodingRe-save the target file in the desired encoding - e.g. in Notepad++ or the OpenExchange application File Encoding Converter. (See Workaround: Add byte order mark to source file)Warning: If the source file encoding was not detected as desired, incorrect characters may have been extracted when opening the file. When choosing this approach, review the target file thoroughly! Problem persists?
Technical issue but no PSMA?
If you identify systematic encoding detection issues affecting a greater number of files when using a native Trados file type, SDL is happy to receive your feedback to evaluate whether the encoding detection used by Trados Studio can be improved further to accommodate as many files as possible. However, please bear in mind that in general encoding detection cannot be perfect. If encoding detection issues occur only for very specific files, we recommend that you apply above workarounds. |
Your file does not specify what character encoding it uses (it does not use a Byte order mark). Trados has to guess the character encoding of the file. This process is not foolproof because it depends on statistical data. Therefore, the character encoding may be guessed incorrectly, characters are not displayed correctly in the editor view. Since the detected encoding of the source file influences of the encoding Trados uses to save the target file, characters may not appear as expected when viewing the target file in a specific application. |