UTF-32 - Revision history

Dan Tobias at 02:37, 21 May 2019

2019-05-21T02:37:22Z

Dan Tobias at 19:52, 19 May 2019

2019-05-19T19:52:52Z

Dan Tobias at 19:51, 19 May 2019

2019-05-19T19:51:02Z

Jsummers at 21:46, 14 April 2016

2016-04-14T21:46:04Z

Jsummers at 21:43, 14 April 2016

2016-04-14T21:43:34Z

Jsummers at 22:25, 4 March 2016

2016-03-04T22:25:46Z

Dan Tobias at 18:08, 17 February 2013

2013-02-17T18:08:17Z

Dan Tobias: Clarify endianness

2013-02-17T18:06:18Z

Clarify endianness

Dan Tobias at 06:39, 17 November 2012

2012-11-17T06:39:40Z

Gmcgath: Removed "Text Encoding"; redundant with "Character Encodings"

2012-11-10T06:21:11Z

Removed "Text Encoding"; redundant with "Character Encodings"

@@ Line 2: / Line 2: @@
 |formattype=electronic
 |subcat=Character encoding
 |charset=UTF-32
 |charsetaliases=csUTF32

@@ Line 10: / Line 10: @@
 UTF-32 is also known as '''UCS-4'''. There may be some subtle philosophical differences between the terms "UTF-32" and "UCS-4", but for all practical purposes they are synonyms.
-As with UTF-16, this format exists in both big- and small-[[Endianness|endian]] varieties; since the relevant units are 32-bit chunks (not pairs of 16-bit chunks as the longer sequences of UTF-16 are), the endianness is applied to the entire 32 bits (4 bytes), meaning that the [[Byte Order Mark]] (zero-width no-break space) U+FEFF is encoded as byte sequence 00 00 FE FF in the big-endian version and FF FE 00 00 in the little-endian one (with all four bytes reversed from one version to the other).
+As with UTF-16, this format exists in both big- and small-[[Endianness|endian]] varieties; since the relevant units are 32-bit chunks (not pairs of 16-bit chunks as the longer sequences of UTF-16 are), the endianness is applied to the entire 32 bits (4 bytes), meaning that the [[Byte Order Mark]] (zero-width no-break space) U+FEFF is encoded as byte sequence 00 00 FE FF in the big-endian version and FF FE 00 00 in the little-endian one (with all four bytes reversed from one version to the other). IANA has assigned the charset identifiers UTF-32BE (MIBenum 1018) and UTF-32LE (MIBenum 1019) to these variants.
 == Links ==

@@ Line 2: / Line 2: @@
 |formattype=electronic
 |subcat=Character encoding
 }}
 '''UCS Transformation Format—32-bit''' ('''UTF-32''') is the trivial 32-bit [[Unicode]] character encoding. It encodes a sequence of Unicode code points in a sequence of 32-bit integers. 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.

@@ Line 3: / Line 3: @@
 |subcat=Character encoding
 }}
-'''UCS Transformation Format—32-bit''' ('''UTF-32''') is the trivial 32-bit [[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 the trivial 32-bit [[Unicode]] character encoding. It encodes a sequence of Unicode code points in a sequence of 32-bit integers. 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.
 UTF-32 is also known as '''UCS-4'''. There may be some subtle philosophical differences between the terms "UTF-32" and "UCS-4", but for all practical purposes they are synonyms.

@@ Line 3: / Line 3: @@
 |subcat=Character encoding
 }}
-'''UCS Transformation Format—32-bit''' (UTF-32, also known as UCS-4) 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 the trivial 32-bit [[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.
 As with UTF-16, this format exists in both big- and small-[[Endianness|endian]] varieties; since the relevant units are 32-bit chunks (not pairs of 16-bit chunks as the longer sequences of UTF-16 are), the endianness is applied to the entire 32 bits (4 bytes), meaning that the [[Byte Order Mark]] (zero-width no-break space) U+FEFF is encoded as byte sequence 00 00 FE FF in the big-endian version and FF FE 00 00 in the little-endian one (with all four bytes reversed from one version to the other).

@@ Line 3: / Line 3: @@
 |subcat=Character Encodings
 }}
-'''[[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]
+As with UTF-16, this format exists in both big- and small-[[Endianness|endian]] varieties; since the relevant units are 32-bit chunks (not pairs of 16-bit chunks as the longer sequences of UTF-16 are), the endianness is applied to the entire 32 bits (4 bytes), meaning that the [[Byte Order Mark]] (zero-width no-break space) U+FEFF is encoded as byte sequence 00 00 FE FF in the big-endian version and FF FE 00 00 in the little-endian one (with all four bytes reversed from one version to the other).

← Older revision		Revision as of 06:39, 17 November 2012
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]]	+	[http://www.unicode.org/faq/utf_bom.html#UTF32 UTF-32 FAQ]

← Older revision		Revision as of 06:21, 10 November 2012
Line 6:		Line 6:

	[[http://www.unicode.org/faq/utf_bom.html#UTF32 UTF-32 FAQ]]		[[http://www.unicode.org/faq/utf_bom.html#UTF32 UTF-32 FAQ]]
−
−	~~[[Category:Text encoding]]~~