Variable-width encoding: Difference between revisions

Revision as of 15:39, 7 June 2007

Latest revision as of 21:26, 14 February 2025

(93 intermediate revisions by 67 users not shown)

Line 1:

{{more citations needed|date=December 2009}}

A '''variable-width encoding''' is a type of [[character encoding]] scheme in which codes of differing lengths are used to encode a [[character set]] (a repertoire of symbols) for representation in a [[computer]]. Most common variable-width encodings are '''multibyte encodings''', which use varying numbers of [[byte]]s ([[octet (computing)|octet]]s) to encode different characters.

{{Short description|Type of character encoding scheme}}{{Merge|Variable-length code

(Some authors, notably in Microsoft documentation, use the term ''multibyte character set,'' which is a [[misnomer]] since representation size is an attribute of the encoding, not of the character set.)

| date = February 2025

}}{{About|the storage of text in computers|the transmission of data across noisy channels|variable-length code}}

{{Use dmy dates|date=December 2023}}

A '''variable-width encoding''' is a type of [[character encoding]] scheme in which codes of differing lengths are used to encode a [[character set]] (a repertoire of symbols) for representation, usually in a [[computer]].<ref>{{Cite RFC|last=Crispin|first=M.|date=1 April 2005|title=UTF-9 and UTF-18 Efficient Transformation Formats of Unicode|doi=10.17487/rfc4042|doi-access=}}</ref>{{efn|The concept long precedes the advent of the electronic computer, however, as seen with [[Morse code]].}} Most common variable-width encodings are '''multibyte encodings''' (aka '''MBCS''' – '''multi-byte character set'''), which use varying numbers of [[byte]]s ([[octet (computing)|octetoctets]]s) to encode different characters. (Some authors, notably in [[Microsoft]] documentation, use the term ''multibyte character set,'' which is a [[misnomer]], because representation size is an attribute of the encoding, not of the character set.)

Early variable -width encodings using less than a byte per character were sometimes used to pack English text into lessfewer bytes in [[adventure game]]s for early [[microcomputersmicrocomputer]]s. However [[disk storage|diskdisks]]s (which unlike tapes allowed random access allowing text to be loaded on demand), increases in computer memory and general purpose [[compression algorithm]]s have rendered such tricks largely redundantobsolete.

Multibyte encodings are usually the result of a need to increase the number of characters which can be encoded without breaking [[backward compatibility]] with an existing constraint. For example, with one byte (8 &nbsp;bits) per character, one can encode 256 possible characters; in order to encode more than 256 characters, the obvious choice would be to use two or more bytes per encoding unit, two bytes (16 &nbsp;bits) would allow 65,536 possible characters, but such a change would break compatibility with existing systems and therefore might not be feasible at all.{{efn|As a real-life example of this, [[UTF-16]], which represents the most common characters in exactly the manner just described (and uses pairs of 16-bit code units for less-common characters) never gained traction as an encoding for text intended for interchange due to its incompatibility with the ubiquitous 7-/8-bit [[ASCII]] encoding, with its intended role instead being taken by [[UTF-8]], which ''does'' preserve ASCII compatibility.}}

==General structure==

Since the aim of a multibyte encoding system is to minimise changes to existing application software, some characters must retain their pre-existing single-unit codes, even while other characters have multiple units in their codes. The result is that there are three sorts of units in a variable-width encoding: '''singletons''', which consist of a single unit, '''lead units''', which come first in a multiunit sequence, and '''trail units''', which come afterwards in a multiunit sequence. Input and display software obviously needs to know about the structure of the multibyte encoding scheme, but other software generally doesn't need to know if a pair of bytes represent two separate characters or just one character.

For example, the four character string "[[I Love New York|I{{unicode|♥}}NYI♥NY]]" is encoded in [[UTF-8]] like this (shown as [[hexadecimal]] byte values): <span style="color:green">{{mono|49</span> <span style="color:red">{{maroon|E2</span>}} <span{{navy style="(color:blue">)|99</span>}} <span{{navy style="(color:blue">)|A5</span>}} <span style="color:green">4E</span> <span style="color:green">59</span>}}. Of the six units in that sequence, <span style="color:green">49</span>, <span style="color:green">4E</span>, and <span style="color:green">59</span> are singletons (for ''I, N,'' and ''Y''), <span style="color:red">{{maroon|E2</span>}} is a lead unit and <span{{navy style="(color:blue">)|99</span>}} and <span{{navy style="(color:blue">)|A5</span>}} are trail units. The heart symbol is represented by the combination of the lead unit and the two trail units.

UTF-8 makes it easy for a program to identify the three sorts of units, assince they arefall into separate keptvalue apartranges. Older variable-width encodings are typically not soas well -designed, as in themsince the trail and lead unitsranges may use the same values, and in some all three sorts use overlapping valuesoverlap. Where there is overlap, aA text processing application that deals with the variable-width encoding must then scan the text from the beginning of all definitive sequences in order to identify the various units properly and interpret the text correctly. In such encodings, one is liable to encounter false positives when searching for a string in the middle of the text. For example, if the hexadecimal values DE and, DF and, E0, and E1 can all be either lead units or trail units, then a search for the two-unit sequence DF E0 can yield a false positive in the sequence DE DF E0 E1, which consists of two consecutive two-unit sequences DE DF E0 E1. There is also the danger that a single corrupted or lost unit may render the whole interpretation of a large run of multiunit sequences totally differentincorrect. In a variable-width encoding where all three sortstypes of units are disjunct, string searching always works without false positives, and (provided the decoder is well written) the corruption or loss of one unit corrupts only one character.

==[[CJK]] multibyte encodings==

The first use of multibyte encodings was for the encoding of Chinese, Japanese and Korean, which have large character sets well in excess of 256 characters. At first the encoding was constrained to the limit of 7 bits. The [[ISO/IEC 2022|ISO-2022-JP, ISO-2022-CN and ISO-2022-KR encodings]] used the range 21-7E21–7E (hexadecimal) for both lead units and trail units, and marked them off from the singletons by using ISO 2022 escape sequences to switch between single-byte and multibyte mode. A total of 8,836 (94×94) characters could be encoded at first, and further sets of 94×94 characters with switching. The ISO 2022 encoding schemes for CJK are still in use on the Internet. The stateful nature of these encodings and the large overlap make them very awkward to process.

On [[Unix]] platforms, the ISO 2022 7-bit encodings were replaced by a set of 8-bit encoding schemes, the Extended Unix Code: EUC-JP, EUC-CN and EUC-KR. Instead of distinguishing between the multiunit sequences and the singletons with escape sequences, which made the encodings stateful, multiunit sequences were marked by having the most significant bit set, that is, being in the range 80-FF80–FF (hexadeximalhexadecimal), while the singletons were in the range 00-7F00–7F alone. The lead units and trail units were in the range A1 to FE (hexadeximalhexadecimal), that is, the same as their range in the ISO 2022 encodings, but with the high bit set to 1. These encodings were reasonabllyreasonably easy to work with provided all your delimiters were [[ASCII]] characters and you avoided truncating strings to fixed lengths, but a break in the middle of a multibyte character could still cause major corruption.

On the PC ([[MS-DOS]] and [[Microsoft Windows]] platforms), two encodings became established for Japanese and Traditional Chinese in which all of singletons, lead units and trail units overlapped: [[Shift-JIS]] and [[Big5]] respectively. In Shift-JIS, lead units had the range 81-9F81–9F and E0-FCE0–FC, trail units had the range 40-7E40–7E and 80-FC80–FC, and singletons had the range 21-7E21–7E and A1-DFA1–DF. In Big5, lead units had the range A1-FEA1–FE, trail units had the range 40-7E40–7E and A1-FEA1–FE, and singletons had the range 21-7E21–7E (all values in hexadecimal). This overlap, again, made processing tricky, though at least most of the symbols had unique byte values (though strangely the backslash does not).<!-- FIXME: GBK and code page 949 should probabblyprobably also be mentioned here. -->

==Unicode variable-width encodings==

The [[Unicode]] standard has two variable-width encodings: [[UTF-8]] and [[UTF-16]] (it also has a fixed-width encoding, [[UTF-32]]). Originally, both the Unicode and [[ISO 10646|ISO&nbsp;10646]] standards were meant to be fixed-width, with Unicode being 16 -bit and ISO&nbsp;10646 being 32 -bit.{{Citation needed|date=April 2013}} ISO 10646 provided a variable-width encoding called [[UTF-1]], in which singletons had the range 00-9F00–9F, lead units the range A0-FFA0–FF and trail units the rangeranges A0-FFA0–FF and 21-7E21–7E. Because of this bad design, parallelsimilar to [[Shift- JIS]] and [[Big5]] in its overlap of values, the inventors of the [[Plan 9 from Bell Labs|Plan 9]] operating system, the first to implement Unicode throughout, abandoned it and replaced it with a much better designed variable-width encoding for Unicode: UTF-8, in which singletons have the range 00-7F00–7F, lead units have the range C0-DFC0–FD (now actually C2-DFC2–F4, to avoid overlong sequences and to maintain synchronism with the encoding capacity of UTF-16; see the [[UTF-8]] article), and trail units have the range E0-FD (now E0-F4, in synchronism with the encoding capacity of UTF-16)80–BF. The lead unit also tells how many trail units follow: one after C2-DFC2–DF, two after E0-EFE0–EF and three after F0F0–F4.{{efn|In the original version of UTF-F48, from its 1992 publication until its code space was restricted to that of UTF-16 in 2003, the range of lead units encoding three-unit trailing sequences was larger (F0–F7); additionally, the lead units F8–FB were followed by four trail units, and FC–FD by five. FE–FF were never valid lead or trail units in any version of UTF-8.}}

UTF-16 was devised to break free of the 65,536-character limit of the original Unicode (1.x) without breaking compatibility with the 16-bit encoding. In UTF-16, singletons have the range 0000-D7FF0000–D7FF (55,296 code points) and E000-FFFFE000–FFFF (8192 code points, 63,488 in total), lead units the range D800-DBFFD800–DBFF (1024 code points) and trail units the range DC00-DFFFDC00–DFFF (1024 code points, 2048 in total). The lead and trail units, called in Unicode terminology ''high surrogates'' and ''low surrogates'', respectively, in Unicode terminology, map 1024×1024 or 1,048,576 numberssupplementary characters, making for1,112,064 a(63,488 maximumBMP ofcode possiblepoints + 1,114048,112576 codepointscode points represented by high and low surrogate pairs) encodable code points, or ''scalar values'' in Unicode parlance (surrogates are not encodable).

==See also==

[[Category:Character encoding]]

* [[wchar_t]] wide characters

* [[de:MultibyteLotus Multi-Byte Character Set]] (LMBCS)

* [[Triple-Byte Character Set]] (TBCS)

* [[Double-byte character set|Double-Byte Character Set]] (DBCS)

* [[SBCS|Single-Byte Character Set]] (SBCS)

==Notes==

[[de:Multibyte Character Set]]

{{notelist}}

[[ja:マルチバイト文字]]

==References==

{{Reflist}}

{{Character encoding}}

{{DEFAULTSORT:Variable-Width Encoding}}

[[Category:Character encoding]]