Encoding of TXT Files

If checked out TXT files contain special characters (e.g., Asian or Cyrillic characters), the display can seem to be incorrect in a text editor like Notepad.

drittprogramm_notepad_unicode_sonderzeichen-falsch-dargestellt

However, this is merely a display problem of the editor. The check-out from Across is correct.

The problem is related to the encoding of the source file. As it was not encoded in Unicode or not recognized as Unicode by the MS Office API, a different encoding was assigned. While some programs like Notepad are not able to display the special characters, MS Word and Internet Explorer do not have any problems.

When you open the file in the Internet Explorer, the correct encoding is selected automatically, or you can select it via View > Encoding. The special characters are displayed correctly:

drittprogramm_ie_unicode_sonderzeichen-korrekt-dargestellt

When opening the file in MS Word, a dialog will ask you for the encoding with which the file is to be opened. Usually, the correct encoding is preselected.

drittprogramm_ms-word_unicode_sonderzeichen_kodierungsauswahl

If this is not the case, select the correct encoding. You can now open the document. Special characters will be displayed correctly:

drittprogramm_ms-word_unicode_sonderzeichen-korrekt-dargestellt

When saving the document as TXT file in Word, you can also select a different encoding:

drittprogramm_ms-word_unicode_sonderzeichen_kodierung-beim-speichern-auswaehlen

If you select the correct encoding or UTF-8, Notepad will also be able to display the file correctly:

drittprogramm_notepad_unicode_sonderzeichen-korrekt-dargestellt