Windows encodings

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
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", or in some cases (also somewhat misleadingly), "multi-byte" encodings.
+
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

File Format
Name Windows encodings
Ontology

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

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox