UTF-32
From Just Solve the File Format Problem
(Difference between revisions)
(Removed "Text Encoding"; redundant with "Character Encodings") |
Dan Tobias (Talk | contribs) |
||
| Line 5: | Line 5: | ||
'''[[UCS]] Transformation Format—32-bit''' (UTF-32) is a [[Unicode]] character encoding. There is a one-to-one mapping of Unicode code points to 32-bit values, so all characters require the same number of bits. Since the largest code points can be expressed in only 21 bits, this encoding is inherently wasteful of space; [[UTF-8]] or [[UTF-16]] is a more efficient coding in most cases. UTF-32 does provide computational simplicity and is more often used for in-memory storage of characters than for stored documents. | '''[[UCS]] Transformation Format—32-bit''' (UTF-32) is a [[Unicode]] character encoding. There is a one-to-one mapping of Unicode code points to 32-bit values, so all characters require the same number of bits. Since the largest code points can be expressed in only 21 bits, this encoding is inherently wasteful of space; [[UTF-8]] or [[UTF-16]] is a more efficient coding in most cases. UTF-32 does provide computational simplicity and is more often used for in-memory storage of characters than for stored documents. | ||
| − | + | [http://www.unicode.org/faq/utf_bom.html#UTF32 UTF-32 FAQ] | |
Revision as of 06:39, 17 November 2012
UCS Transformation Format—32-bit (UTF-32) is a Unicode character encoding. There is a one-to-one mapping of Unicode code points to 32-bit values, so all characters require the same number of bits. Since the largest code points can be expressed in only 21 bits, this encoding is inherently wasteful of space; UTF-8 or UTF-16 is a more efficient coding in most cases. UTF-32 does provide computational simplicity and is more often used for in-memory storage of characters than for stored documents.
