UTF-9
From Just Solve the File Format Problem
(Difference between revisions)
m (Grammatical fix) |
Dan Tobias (Talk | contribs) |
||
| (2 intermediate revisions by one user not shown) | |||
| Line 2: | Line 2: | ||
|formattype=electronic | |formattype=electronic | ||
|subcat=Character encoding | |subcat=Character encoding | ||
| + | |subcat2=Unicode | ||
|released=2005 | |released=2005 | ||
}} | }} | ||
| − | '''UTF-9''' is a [[Unicode]] [[Character Encodings|character encoding]] introduced by the standards document RFC 4042 in 2005. UTF-9 and its sibling [[UTF-18]] allow for efficient coding of Unicode characters on machines based on 36-bit words, using 9 and 18 bits per code point, respectively. Although | + | '''UTF-9''' is a [[Unicode]] [[Character Encodings|character encoding]] introduced by the standards document RFC 4042 in 2005. UTF-9 and its sibling [[UTF-18]] allow for efficient coding of Unicode characters on machines based on 36-bit words, using 9 and 18 bits per code point, respectively. Although they are completely valid in a technical sense, they are largely humorous, as virtually all computers designed after the early-mid 1980s use word sizes of powers of two, making these encodings largely obsolete. |
| + | |||
| + | == Software == | ||
| + | * [https://github.com/enricobacis/utf9]: A converter written in [[Python]] (Pip package utf9) | ||
== Links == | == Links == | ||
Latest revision as of 02:36, 21 May 2019
UTF-9 is a Unicode character encoding introduced by the standards document RFC 4042 in 2005. UTF-9 and its sibling UTF-18 allow for efficient coding of Unicode characters on machines based on 36-bit words, using 9 and 18 bits per code point, respectively. Although they are completely valid in a technical sense, they are largely humorous, as virtually all computers designed after the early-mid 1980s use word sizes of powers of two, making these encodings largely obsolete.
[edit] Software
[edit] Links
- RFC 4042
- Wikipedia:April Fools' Day Request for Comments#2005: Very short Wikipedia entry on RFC 4042
