Windows encodings
From Just Solve the File Format Problem
(Difference between revisions)
Line 5: | Line 5: | ||
'''Windows encodings''' refers to the various legacy character encodings used by the non-[[Unicode]] Microsoft Windows API, and most non-Unicode-aware Windows applications. (GUI applications, anyway. Windows ''console'' applications default to using the [[MS-DOS encodings]] in many cases.) | '''Windows encodings''' refers to the various legacy character encodings used by the non-[[Unicode]] Microsoft Windows API, and most non-Unicode-aware Windows applications. (GUI applications, anyway. Windows ''console'' applications default to using the [[MS-DOS encodings]] in many cases.) | ||
− | In Windows jargon, these encodings are misleadingly called "ANSI", | + | In Windows jargon, these encodings are misleadingly called "ANSI". Together with the [[MS-DOS encodings]], they are sometimes called the "multi-byte" encodings. |
All too many file formats use one of these encodings, with no reliable way to determine which one. | All too many file formats use one of these encodings, with no reliable way to determine which one. |
Revision as of 17:39, 25 January 2018
Windows encodings refers to the various legacy character encodings used by the non-Unicode Microsoft Windows API, and most non-Unicode-aware Windows applications. (GUI applications, anyway. Windows console applications default to using the MS-DOS encodings in many cases.)
In Windows jargon, these encodings are misleadingly called "ANSI". Together with the MS-DOS encodings, they are sometimes called the "multi-byte" encodings.
All too many file formats use one of these encodings, with no reliable way to determine which one.
List of encodings
- Windows 1252 (ISO 8859-1 plus additional characters)
- Windows 1255 (Hebrew)
- Windows 1256 (Arabic, Farsi, Urdu)
- Windows 1257 (Baltic Rim)
- Windows 1258 (Vietnamese)