UTF-EBCDIC

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
Line 2: Line 2:
 
|formattype=electronic
 
|formattype=electronic
 
|subcat=Character encoding
 
|subcat=Character encoding
 +
|subcat2=Unicode
 
}}
 
}}
 
'''UTF-EBCDIC''' is a character encoding based on [[UTF-8]] but engineered to be more friendly to systems using [[EBCDIC]] rather than [[ASCII]]-based character sets. It is designed to allow raw code points in the [[C1 controls]] range in order to encode EBCDIC control characters, and the characters are sent through a reversible transformation so that they are encoded in their EBCDIC code positions rather than those of ASCII. This encoding has not had much use, even on mainframes that still use EBCDIC, since they have usually been set up to use [[UTF-16]] directly in applications requiring full Unicode support.
 
'''UTF-EBCDIC''' is a character encoding based on [[UTF-8]] but engineered to be more friendly to systems using [[EBCDIC]] rather than [[ASCII]]-based character sets. It is designed to allow raw code points in the [[C1 controls]] range in order to encode EBCDIC control characters, and the characters are sent through a reversible transformation so that they are encoded in their EBCDIC code positions rather than those of ASCII. This encoding has not had much use, even on mainframes that still use EBCDIC, since they have usually been set up to use [[UTF-16]] directly in applications requiring full Unicode support.

Revision as of 02:37, 21 May 2019

File Format
Name UTF-EBCDIC
Ontology

UTF-EBCDIC is a character encoding based on UTF-8 but engineered to be more friendly to systems using EBCDIC rather than ASCII-based character sets. It is designed to allow raw code points in the C1 controls range in order to encode EBCDIC control characters, and the characters are sent through a reversible transformation so that they are encoded in their EBCDIC code positions rather than those of ASCII. This encoding has not had much use, even on mainframes that still use EBCDIC, since they have usually been set up to use UTF-16 directly in applications requiring full Unicode support.

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox