UTF-8 is a character encoding capable of encoding all possible characters, or code points, defined by Unicode and originally designed by Ken Thompson and Rob Pike.
The encoding is variable-length and uses 8-bit code units. It was designed for backward compatibility with ASCII and to avoid the complications of endianness and byte order marks in the alternative UTF-16 and UTF-32 encodings. The name is derived from Unicode (or Universal Coded Character Set) Transformation Format – 8-bit.
UTF-8 is the dominant character encoding for the World Wide Web, accounting for 87.9% of all Web pages in November 2016 (the most popular East Asian encodings, Shift JIS and GB 2312, have 1.1% and 0.8% respectively). The Internet Mail Consortium (IMC) recommends that all e-mail programs be able to display and create mail using UTF-8, and the W3C recommends UTF-8 as the default encoding in XML and HTML.
UTF-8 encodes each of the 1,112,064 valid code points in the Unicode code space (1,114,112 code points minus 2,048 surrogate code points) using one to four 8-bit bytes (a group of 8 bits is known as an octet in the Unicode Standard). Code points with lower numerical values (i.e., earlier code positions in the Unicode character set, which tend to occur more frequently) are encoded using fewer bytes. The first 128 characters of Unicode, which correspond one-to-one with ASCII, are encoded using a single octet with the same binary value as ASCII, so that valid ASCII text is valid UTF-8-encoded Unicode as well. Since ASCII bytes do not occur when encoding non-ASCII code points into UTF-8, UTF-8 is safe to use within most programming and document languages that interpret certain ASCII characters in a special way, such as end of string.
By early 1992, the search was on for a good byte stream encoding of multi-byte character sets. The draft ISO 10646 standard contained a non-required annex called UTF-1 that provided a byte stream encoding of its 32-bit code points. This encoding was not satisfactory on performance grounds, among other problems, and the biggest problem was probably that it did not have a clear separation between ASCII and non-ASCII: new UTF-1 tools would be backward compatible with ASCII-encoded text, but UTF-1-encoded text could confuse existing code expecting ASCII (or extended ASCII), because it could contain continuation bytes in the range 0x21–0x7E that meant something else in ASCII, e.g., 0x2F for '/', the Unix path directory separator, and this example is reflected in the name and introductory text of its replacement. The table below was derived from a textual description in the annex.
|Byte 1||Byte 2||Byte 3||Byte 4||Byte 5|
|3||U+4016||U+38E2D||F6–FB||21–7E, A0–FF||21–7E, A0–FF|
|5||U+38E2E||U+7FFFFFFF||FC–FF||21–7E, A0–FF||21–7E, A0–FF||21–7E, A0–FF||21–7E, A0–FF|
In July 1992, the X/Open committee XoJIG was looking for a better encoding. Dave Prosser of Unix System Laboratories submitted a proposal for one that had faster implementation characteristics and introduced the improvement that 7-bit ASCII characters would only represent themselves; all multibyte sequences would include only bytes where the high bit was set. The name File System Safe UCS Transformation Format (FSS-UTF) and most of the text of this proposal were later preserved in the final specification.
|Byte 1||Byte 2||Byte 3||Byte 4||Byte 5|
In August 1992, this proposal was circulated by an IBM X/Open representative to interested parties. A modification by Ken Thompson of the Plan 9 operating system group at Bell Labs made it somewhat less bit-efficient than the previous proposal but crucially allowed it to be self-synchronizing, letting a reader start anywhere and immediately detect byte sequence boundaries. It also abandoned the use of biases and instead added the rule that only the shortest possible encoding is allowed; the additional loss in compactness is relatively insignificant, but readers now have to look out for invalid encodings to avoid reliability and especially security issues. Thompson's design was outlined on September 2, 1992, on a placemat in a New Jersey diner with Rob Pike. In the following days, Pike and Thompson implemented it and updated Plan 9 to use it throughout, and then communicated their success back to X/Open, which accepted it as the specification for FSS-UTF.
|Byte 1||Byte 2||Byte 3||Byte 4||Byte 5||Byte 6|
UTF-8 was first officially presented at the USENIX conference in San Diego, from January 25 to 29, 1993.
In November 2003, UTF-8 was restricted by RFC 3629 to match the constraints of the UTF-16 character encoding: explicitly prohibiting code points corresponding to the high and low surrogate characters removed more than 3% of the three-byte sequences, and ending at U+10FFFF removed more than 48% of the four-byte sequences and all five- and six-byte sequences.
Google reported that in 2008, UTF-8 (labelled "Unicode") became the most common encoding for HTML files.
This table shows UTF-8 as it is since 2003 (the
x characters are replaced by the bits of the code point):
|Byte 1||Byte 2||Byte 3||Byte 4|
The salient features of this scheme are as follows:
- Backward compatibility: One-byte codes are used only for the ASCII values 0 through 127. In this case the UTF-8 code has the same value as the ASCII code. The high-order bit of these codes is always 0. This means that ASCII text is valid UTF-8, and UTF-8 can be used for parsers expecting 8-bit extended ASCII even if they are not designed for UTF-8.
- Clear distinction between multi-byte and single-byte characters: Code points larger than 127 are represented by multi-byte sequences, composed of a leading byte and one or more continuation bytes. The leading byte has two or more high-order 1s followed by a 0, while continuation bytes all have '10' in the high-order position. Thus, no bytes representing ASCII characters appear in multi-byte sequences.
- Clear indication of byte sequence length: Like in UTF-1, the first byte indicates the number of bytes in the sequence. Unlike in UTF-1, for multi-byte sequences it is simply the number of high-order 1s in the leading byte.
- Prefix property: From the sequence length indication in the first byte (for both UTF-1 and UTF-8), a reader also knows where a sequence ends, which implies that no valid sequence is a prefix of any other. This means that a reader reading from a stream can instantaneously decode each individual fully received sequence, without first having to wait for either the first byte of a next sequence or an end-of-stream indication.
- Self-synchronization: Unlike in UTF-1, the high-order bits of every byte determine the type of byte: single bytes (
0xxxxxxx), leading bytes (
11...xxx), and continuation bytes (
10xxxxxx) do not share values. The start of a character can be found by backing up at most 3 bytes (5 bytes before RFC 3629 restriction, see above). Together with the prefix property, this makes the scheme self-synchronizing.
- Code structure: The remaining bits of the encoding are used for the bits of the code point being encoded, padded with high-order 0s if necessary. The high-order bits go in the leading byte, lower-order bits in subsequent continuation bytes. The number of bytes in the encoding must be the minimum required to hold all the significant bits of the code point.
The first 128 characters (US-ASCII) need one byte. The next 1,920 characters need two bytes to encode. This covers the remainder of almost all Latin alphabets, and also Greek, Cyrillic, Coptic, Armenian, Hebrew, Arabic, Syriac, Thaana and N'Ko alphabets, as well as Combining Diacritical Marks. Three bytes are needed for characters in the rest of the Basic Multilingual Plane, which contains virtually all characters in common use including most Chinese, Japanese and Korean characters. Four bytes are needed for characters in the other planes of Unicode, which include less common CJK characters, various historic scripts, mathematical symbols, and emoji (pictographic symbols).
Consider the encoding of the Euro sign, €.
- The Unicode code point for "€" is U+20AC.
- According to the scheme table above, this will take three bytes to encode, since it is between U+0800 and U+FFFF.
0010 0000 1010 1100. The two leading zeros are added because, as the scheme table shows, a three-byte encoding needs exactly sixteen bits from the code point.
- Because the encoding will be three bytes long, its leading byte starts with three 1s, then a 0 (
- The first four bits of the code point are stored in the remaining low order four bits of this byte (
1110 0010), leaving 12 bits of the code point yet to be encoded (
...0000 1010 1100).
- All continuation bytes contain exactly six bits from the code point. So the next six bits of the code point are stored in the low order six bits of the next byte, and
10is stored in the high order two bits to mark it as a continuation byte (so
- Finally the last six bits of the code point are stored in the low order six bits of the final byte, and again
10is stored in the high order two bits (
The three bytes
1010 1100 can be more concisely written in hexadecimal, as
E2 82 AC.
Since UTF-8 uses groups of six bits, it is sometimes useful to use octal notation which uses 3-bit groups. With a calculator which can convert between hexadecimal and octal it can be easier to manually create or interpret UTF-8 compared to using binary.
- Octal 0200–3777 (hex 80-7FF) shall be coded with two bytes. xxyy will be 3xx 2yy.
- Octal 4000–177777 (hex 800-FFFF) shall be coded with three bytes. xxyyzz will be (340+xx) 2yy 2zz.
- Octal 200000-4177777 (hex 10000-10FFFF) shall be coded with four bytes. wxxyyzz will be 36w 2xx 2yy 2zz.
The following table summarises this conversion, as well as others with different lengths in UTF-8. The colors indicate how bits from the code point are distributed among the UTF-8 bytes. Additional bits added by the UTF-8 encoding process are shown in black.
|Character||Octal code point||Binary code point||Binary UTF-8||Octal UTF-8||Hexadecimal UTF-8|
The following table summarizes usage of UTF-8 code units (individual bytes or octets) in a code page format. The upper half (
7_) is for bytes only used in single-byte codes, so it looks like a normal code page; the lower half is for continuation bytes (
B_) and (possible) leading bytes (
F_), and is explained further in the legend below.
Orange cells with a large dot are continuation bytes. The hexadecimal number shown after a "+" plus sign is the value of the six bits they add.
White cells are the leading bytes for a sequence of multiple bytes, the length shown at the left edge of the row. The text shows the Unicode blocks encoded by sequences starting with this byte, and the hexadecimal code point shown in the cell is the lowest character value encoded using that leading byte.
Red cells must never appear in a valid UTF-8 sequence. The first two (C0 and C1) could only be used for an invalid "overlong encoding" of ASCII characters (i.e., trying to encode a 7-bit ASCII value between 0 and 127 using two bytes instead of one; see below). The remaining red cells indicate leading bytes of sequences that could only encode numbers larger than the 0x10FFFF limit of Unicode, or that were also never used in the original design for 31 bits (FE and FF).
Pink cells are the leading bytes for a sequence of multiple bytes, of which some, but not all, possible continuation sequences are valid. E0 and F0 could start overlong encodings, in this cast the lowest non-overlong-encoded code point is shown, marked by an asterisk "*". F4 can start code points greater than 0x10FFFF which are invalid. ED can start the encoding of a surrogate half that cannot be encoded in UTF-16 and are also invalid.
In principle, it would be possible to inflate the number of bytes in an encoding by padding the code point with leading 0s. To encode the Euro sign € from the above example in four bytes instead of three, it could be padded with leading 0s until it was 21 bits long –
000 000010 000010 101100, and encoded as
AC in hexadecimal). This is called an overlong encoding.
The standard specifies that the correct encoding of a code point use only the minimum number of bytes required to hold the significant bits of the code point. Longer encodings are called overlong and are not valid UTF-8 representations of the code point. This rule maintains a one-to-one correspondence between code points and their valid encodings, so that there is a unique valid encoding for each code point. This ensures that string comparisons and searches are well-defined.
Modified UTF-8 uses the two-byte overlong encoding of U+0000 (the NUL character),
80), instead of
00). This allows the byte
00 to be used as a string terminator.
Invalid byte sequences
Not all sequences of bytes are valid UTF-8. A UTF-8 decoder should be prepared for:
- the red invalid bytes in the above table
- an unexpected continuation byte
- a leading byte not followed by enough continuation bytes (can happen in simple string truncation, when a string is too long to fit when copying it)
- an overlong encoding as described above
- a sequence that decodes to an invalid code point as described below
Many earlier decoders would happily try to decode these. Carefully crafted invalid UTF-8 could make them either skip or create ASCII characters such as NUL, slash, or quotes. Invalid UTF-8 has been used to bypass security validations in high-profile products including Microsoft's IIS web server and Apache's Tomcat servlet container.
RFC 3629 states "Implementations of the decoding algorithm MUST protect against decoding invalid sequences." The Unicode Standard requires decoders to "...treat any ill-formed code unit sequence as an error condition. This guarantees that it will neither interpret nor emit an ill-formed code unit sequence."
Many UTF-8 decoders throw exceptions on encountering errors. This can turn what would otherwise be harmless errors (producing a message such as "no such file") into a denial of service bug. Early versions of Python 3.0 would exit immediately if the command line or environment variables contained invalid UTF-8, making it impossible to handle such errors.
More recent converters translate the first byte of an invalid sequence to a replacement character and continue parsing with the next byte. These error bytes will always have the high bit set. This avoids denial-of-service bugs, and it is very common in text rendering such as browser display, since mangled text is probably more useful than nothing for helping the user figure out what the string was supposed to contain. Popular replacements include:
- The replacement character "�" (U+FFFD) (or
- The invalid Unicode code points U+DC80–U+DCFF where the low eight bits are the byte's value. Sometimes it is called UTF-8B
- The Unicode code points U+0080–U+00FF with the same value as the byte, thus interpreting the bytes according to ISO-8859-1
- The Unicode code point for the character represented by the byte in CP1252, which is similar to using ISO-8859-1, except that some characters in the range 0x80–0x9F are mapped into different Unicode code points. For example, 0x80 becomes the Euro sign, U+20AC.
These replacement algorithms are "lossy", as more than one sequence is translated to the same code point. This means that it would not be possible to reliably convert back to the original encoding, therefore losing information. Reserving 128 code points (such as U+DC80–U+DCFF) to indicate errors, and defining the UTF-8 encoding of these points as invalid so they convert to 3 errors, would seem to make conversion lossless. But this runs into practical difficulties: the converted text cannot be modified such that errors are arranged so they convert back into valid UTF-8, which means if the conversion is UTF-16, it cannot also be used to store arbitrary invalid UTF-16, which is usually needed on the same systems that need invalid UTF-8. U+DC80–U+DCFF are reserved for UTF-16 surrogates, so that when they are used for UTF-8 in this way, and the string is converted to UTF-16 this can lead to bugs or the string being rejected.
The large number of invalid byte sequences provides the advantage of making it easy to have a program accept both UTF-8 and legacy encodings such as ISO-8859-1. Software can check for UTF-8 correctness, and if that fails assume the input to be in the legacy encoding. It is technically true that this may detect an ISO-8859-1 string as UTF-8, but this is very unlikely if it contains any 8-bit bytes as they all have to be in unusual patterns of two or more in a row, such as "Â£".
Invalid code points
Since RFC 3629 (November 2003), the high and low surrogate halves used by UTF-16 (U+D800 through U+DFFF) and code points not encodable by UTF-16 (those after U+10FFFF) are not legal Unicode values, and their UTF-8 encoding must be treated as an invalid byte sequence.
Not decoding surrogate halves makes it impossible to store invalid UTF-16, such as Windows filenames, as UTF-8. Therefore, detecting these as errors is often not implemented and there are attempts to define this behavior formally (see WTF-8 and CESU below).
Official name and variants
The official Internet Assigned Numbers Authority (IANA) code for the encoding is "UTF-8". All letters are upper-case, and the name is hyphenated. This spelling is used in all the Unicode Consortium documents relating to the encoding.
Alternatively, the name "utf-8" may be used by all standards conforming to the IANA list (which include CSS, HTML, XML, and HTTP headers), as the declaration is case insensitive.
Other descriptions that omit the hyphen or replace it with a space, such as "utf8" or "UTF 8", are not accepted as correct by the governing standards. Despite this, most agents such as browsers can understand them, and so standards intended to describe existing practice (such as HTML5) may effectively require their recognition.
Unofficially, UTF-8-BOM and UTF-8-NOBOM are sometimes used to refer to text files which respectively contain and lack a byte order mark (BOM). In Japan especially, UTF-8 encoding without BOM is sometimes called "UTF-8N".
In PCL, UTF-8 is called Symbol-ID "18N" (PCL supports 183 character encodings, called Symbol Sets, which potentially could be reduced to one, 18N, that is UTF-8).
The following implementations show slight differences from the UTF-8 specification. They are incompatible with the UTF-8 specification.
Many programs added UTF-8 conversions for UCS-2 data and did not alter this UTF-8 conversion when UCS-2 was replaced with the surrogate-pair using UTF-16. In such programs each half of a UTF-16 surrogate pair is encoded as its own three-byte UTF-8 encoding, resulting in six-byte sequences rather than four bytes for characters outside the Basic Multilingual Plane. Oracle and MySQL databases use this, as well as Java and Tcl as described below, and probably many Windows programs where the programmers were unaware of the complexities of UTF-16. Although this non-optimal encoding is generally not deliberate, a supposed benefit is that it preserves UTF-16 binary sorting order when CESU-8 is binary sorted.
In Modified UTF-8 (MUTF-8), the null character (U+0000) uses the two-byte overlong encoding
80), instead of
00). Modified UTF-8 strings never contain any actual null bytes but can contain all Unicode code points including U+0000, which allows such strings (with a null byte appended) to be processed by traditional null-terminated string functions.
All known Modified UTF-8 implementations also treat the surrogate pairs as in CESU-8.
In normal usage, the Java programming language supports standard UTF-8 when reading and writing strings through
OutputStreamWriter (if it is the platform's default character set or as requested by the program). However it uses Modified UTF-8 for object serialization among other applications of
DataOutput, for the Java Native Interface, and for embedding constant strings in class files.
The dex format defined by Dalvik also uses the same modified UTF-8 to represent string values.
Tcl also uses the same modified UTF-8 as Java for internal representation of Unicode data, but uses strict CESU-8 for external data.
WTF-8 (Wobbly Transformation Format – 8-bit) is an extension of UTF-8 where the encodings of the surrogate halves (U+D800 through U+DFFF) are allowed. This is necessary to store possibly-invalid UTF-16, such as Windows filenames. Many systems that deal with UTF-8 work this way without considering it a different encoding, as it is simpler.
WTF-8 has been used to refer to erroneously doubly-encoded UTF-8.
Byte order mark
Many Windows programs (including Windows Notepad) add the bytes 0xEF, 0xBB, 0xBF at the start of any document saved as UTF-8. This is the UTF-8 encoding of the Unicode byte order mark (BOM), and is commonly referred to as a UTF-8 BOM, even though it is not relevant to byte order. A BOM can also appear if another encoding with a BOM is translated to UTF-8 without stripping it. Software that is not aware of multibyte encodings will display the BOM as three garbage characters at the start of the document, e.g. "ï»¿" in software interpreting the document as ISO 8859-1 or Windows-1252 or "∩╗┐" if interpreted as code page 437, default for Windows console applications.
The Unicode Standard neither requires nor recommends the use of the BOM for UTF-8, but does allow the character to be at the start of a file. The presence of the UTF-8 BOM may cause problems with existing software that could otherwise handle UTF-8, for example:
- Programming language parsers not explicitly designed for UTF-8 can often handle UTF-8 in string constants and comments, but cannot parse the BOM at the start of the file.
- Programs that identify file types by leading characters may fail to identify the file if a BOM is present even if the user of the file could skip the BOM. An example is the Unix shebang syntax. Another example is Internet Explorer which will render pages in standards mode only when it starts with a document type declaration.
- Programs that insert information at the start of a file will break use of the BOM to identify UTF-8 (one example is offline browsers that add the originating URL to the start of the file).
Advantages and disadvantages
- UTF-8 is the only encoding for XML entities that does not require a BOM or an indication of the encoding.
- UTF-8 and UTF-16 are the standard encodings for Unicode text in HTML documents, with UTF-8 as the preferred and most used encoding.
- UTF-8 strings can be fairly reliably recognized as such by a simple heuristic algorithm. Valid UTF-8 cannot contain a lone byte with the high bit set, and the chance that any pair of bytes both with the high bit set is valid UTF-8 is 11.7%[nb 1] and the odds are much lower for longer sequences. This makes it extremely unlikely that text in any other encoding (such as ISO/IEC 8859-1) is valid UTF-8. This is an advantage that most other encodings do not have, and allows UTF-8 to be mixed with a legacy encoding without having to add data to identify which encoding is in use, avoiding errors (mojibake) typically encountered when trying to change a system to a new default encoding, or introducing data with a different encoding than the default one.
- Sorting a set of UTF-8 encoded strings as strings of unsigned bytes yields the same order as sorting the corresponding Unicode strings lexicographically by codepoint.
- Ascii is valid UTF8 and has the shortest possible encoding. Even in non western languages, for XML documents like HTML, docx or odt, ascii characters are almost always the most common ones due to the large amount of markup.
- UTF-8 uses the codes 0–127 only for the ASCII characters. This means that UTF-8 is an ASCII extension and can be processed by software that supports 7-bit characters and assigns no meaning to non-ASCII bytes. This means that strings in most programming languages which use single byte charcters can use the same native interface. This greatly simplifies adapting software for international use as only the part of the software that deals with user interaction and system software to present glyphs need to be upgraded. By contrast, in Shift-JIS a byte that can be a 7-bit ASCII character can also be used as part of a multi-byte character; the byte 0x5C, for example, might be part of a multibyte character, but in the context of a string some programming languages or application software would instead interpret it as a backslash ('\') and assume that it marks the beginning of an escape sequence, incorrectly influencing the interpretation of subsequent bytes. And if using UTF-16 for an upgrade of old software, all code which handle strings must be rewritten. If translating strings using UTF-16 software such as Excel, conversion to UTF-8 is well-defined and done by copy-and-paste into the editor, in opposite to using various 8-bit code pages for internationalization.
Compared to single-byte encodings
- UTF-8 can encode any Unicode character, avoiding the need to figure out and set a "code page" or otherwise indicate what character set is in use, and allowing output in multiple scripts at the same time. For many scripts there have been more than one single-byte encoding in usage, so even knowing the script was insufficient information to display it correctly.
- The bytes 0xFE and 0xFF do not appear, so a valid UTF-8 stream never matches the UTF-16 byte order mark and thus cannot be confused with it. The absence of 0xFF (0377) also eliminates the need to escape this byte in Telnet (and FTP control connection).
- UTF-8 encoded text is larger than specialized single-byte encodings except for plain ASCII characters. In the case of scripts which used 8-bit character sets with non-Latin characters encoded in the upper half (such as most Cyrillic and Greek alphabet code pages), characters in UTF-8 will be double the size. For some scripts, such as Thai and Hindi's Devanagari, characters will triple in size. There are even examples where a single byte turns into a composite character in Unicode and is thus six times larger in UTF-8. This has caused objections in India and other countries.
- It is possible in UTF-8 (or any other multi-byte encoding) to split or truncate a string in the middle of a character. This can result in an invalid string which some software refuse to accept. A good parser should ignore a truncated character at the end, which is easy in UTF-8 but tricky in some other multi-byte encodings.
- If the code points are all the same size, measurements of a fixed number of them is easy. Due to ASCII-era documentation where "character" is used as a synonym for "byte" this is often considered important. However, by measuring string positions using bytes instead of "characters" most algorithms can be easily and efficiently adapted for UTF-8. Searching for a string within a long string can for example be done byte by byte.
- Some software, such as text editors, will refuse to correctly display or interpret UTF-8 unless the text starts with a byte order mark, and will insert such a mark. This has the effect of making it impossible to use UTF-8 with any older software that can handle ASCII-like encodings but cannot handle the byte order mark. This, however, is no problem of UTF-8 itself but one of bad software implementations.
Compared to other multi-byte encodings
- UTF-8 can encode any Unicode character. Files in different scripts can be displayed correctly without having to choose the correct code page or font. For instance Chinese and Arabic can be supported (in the same text) without special codes inserted or manual settings to switch the encoding.
- UTF-8 is self-synchronizing: character boundaries are easily identified by scanning for well-defined bit patterns in either direction. If bytes are lost due to error or corruption, one can always locate the next valid character and resume processing. If there is a need to shorten a string to fit a specified field, the previous valid character can easily be found. Many multi-byte encodings are much harder to resynchronize.
- Any byte oriented string searching algorithm can be used with UTF-8 data, since the sequence of bytes for a character cannot occur anywhere else. Some older variable-length encodings (such as Shift JIS) did not have this property and thus made string-matching algorithms rather complicated. In Shift JIS the end byte of a character and the first byte of the next character could look like another legal character, something that can't happen in UTF-8.
- Efficient to encode using simple bit operations. UTF-8 does not require slower mathematical operations such as multiplication or division (unlike the obsolete UTF-1 encoding).
- UTF-8 will take more space than a multi-byte encoding designed for a specific script. East Asian legacy encodings generally used two bytes per character yet take three bytes per character in UTF-8.
Compared to UTF-16
- Byte encodings and UTF-8 are represented by byte arrays in programs, and often nothing needs to be done to a function when converting from a byte encoding to UTF-8. UTF-16 is represented by 16-bit word arrays, and converting to UTF-16 while maintaining compatibility with existing ASCII-based programs (such as was done with Windows) requires every API and data structure that takes a string to be duplicated, one version accepting byte strings and another version accepting UTF-16.
- Text encoded in UTF-8 will be smaller than the same text encoded in UTF-16 if there are more code points below U+0080 than in the range U+0800..U+FFFF. This is true for all modern European languages.
- Most of the rich text formats (including HTML) contain a large proportion of ASCII characters for the sake of formatting, thus the size usually will be reduced significantly compared to UTF-16, even when the language mostly uses 3-byte long characters in UTF-8.[nb 2]
- Most communication and storage was designed for a stream of bytes. A UTF-16 string must use a pair of bytes for each code unit:
- The order of those two bytes becomes an issue and must be specified in the UTF-16 protocol, such as with a byte order mark.
- If an odd number of bytes is missing from UTF-16, the whole rest of the string will be meaningless text. Any bytes missing from UTF-8 will still allow the text to be recovered accurately starting with the next character after the missing bytes.
- Characters U+0800 through U+FFFF use three bytes in UTF-8, but only two in UTF-16. As a result, text in (for example) Chinese, Japanese or Hindi will take more space in UTF-8 if there are more of these characters than there are ASCII characters. The impact becomes greater when data mainly consist of pure prose, but is lessened by the degree to which the context uses spaces, line terminators, digits, and punctuation that are encoded in ASCII.[nb 3]
- Alt code
- Character encodings in HTML
- Comparison of e-mail clients § Features
- Comparison of Unicode encodings
- GB 18030
- Iconv – a standardized API used to convert between different character encodings
- ISO/IEC 8859
- Specials (Unicode block)
- Unicode and e-mail
- Unicode and HTML
- Universal Character Set
- UTF-8 in URIs
- UTF-9 and UTF-18
- ↑ 1920 valid two-byte UTF-8 characters over 128 × 128 possible two-byte sequences.
- ↑ The 2010-10-27 version of UTF-8 generated 169 KB when converted with Notepad to UTF-16, and only 101 KB when converted back to UTF-8. The 2010-11-22 version of यूनिकोड (Unicode in Hindi) required 119 KB in UTF-16 and 76 KB in UTF-8.
- ↑ The 2010-11-22 version of यूनिकोड (Unicode in Hindi), when the pure text was pasted to Notepad, generated 19 KB when saved as UTF-16 and 22 KB when saved as UTF-8.
- 1 2 Email Subject: UTF-8 history, From: "Rob 'Commander' Pike", Date: Wed, 30 Apr 2003..., ...UTF-8 was designed, in front of my eyes, on a placemat in a New Jersey diner one night in September or so 1992...So that night Ken wrote packing and unpacking code and I started tearing into the C and graphics libraries. The next day all the code was done...
- ↑ "Chapter 2. General Structure". The Unicode Standard (6.0 ed.). Mountain View, California, USA: The Unicode Consortium. ISBN 978-1-936213-01-6.
- ↑ Davis, Mark (2010-01-28). "Unicode nearing 50% of the web". Official Google Blog. Google. Retrieved 2010-12-05.
- ↑ "Usage Statistics of Character Encodings for Websites, (updated daily)". W3Techs. Retrieved 2016-02-21.
- ↑ "UTF-8 Usage Statistics". BuiltWith. Retrieved 2011-03-28.
- ↑ "Using International Characters in Internet Mail". Internet Mail Consortium. 1998-08-01. Retrieved 2007-11-08.
- ↑ "Specifying the document's character encoding", HTML5, World Wide Web Consortium, 2014-06-17, retrieved 2014-07-30
- ↑ "Appendix F. FSS-UTF / File System Safe UCS Transformation format" (PDF). The Unicode Standard 1.1. Archived (PDF) from the original on 2016-06-07. Retrieved 2016-06-07.
- ↑ Whistler, Kenneth (2001-06-12). "FSS-UTF, UTF-2, UTF-8, and UTF-16". Archived from the original on 2016-06-07. Retrieved 2006-06-07.
- 1 2 Pike, Rob (2003-04-30). "UTF-8 history". Retrieved 2012-09-07.
- ↑ Pike, Rob (2012-09-06). "UTF-8 turned 20 years old yesterday". Retrieved 2012-09-07.
- ↑ Davis, Mark (2008-05-05). "Moving to Unicode 5.1". Retrieved 2013-03-01.
- ↑ Allen, Julie D.; Anderson, Deborah; Becker, Joe; Cook, Richard, eds. (2012). "The Unicode Standard, Version 6.1". Mountain View, California: Unicode Consortium.
The Basic Multilingual Plane (BMP, or Plane 0) contains the common-use characters for all the modern scripts of the world as well as many historical and rare characters. By far the majority of all Unicode characters for almost all textual data can be found in the BMP.
- ↑ Marin, Marvin (2000-10-17). "Web Server Folder Traversal MS00-078".
- ↑ "National Vulnerability Database - Summary for CVE-2008-2938".
- 1 2 Yergeau, F. (2003). "RFC 3629 - UTF-8, a transformation format of ISO 10646". Internet Engineering Task Force. Retrieved 2015-02-03.
- ↑ Java's DataInput IO Interface
- ↑ "Non-decodable Bytes in System Character Interfaces". python.org. 2009-04-22. Retrieved 2014-08-13.
- ↑ Kuhn, Markus (2000-07-23). "Substituting malformed UTF-8 sequences in a decoder". Archived from the original on 2015-03-15. Retrieved 2014-09-25.
- ↑ Sittler, B. (2006-04-02). "Binary vs. UTF-8, and why it need not matter". Retrieved 2014-09-25.
- 1 2 "Character Sets". Internet Assigned Numbers Authority. 2013-01-23. Retrieved 2013-02-08.
- ↑ Dürst, Martin. "Setting the HTTP charset parameter". W3C. Retrieved 2013-02-08.
- ↑ "BOM - suikawiki" (in Japanese). Retrieved 2013-04-26.
- ↑ Davis, Mark. "Forms of Unicode". IBM. Archived from the original on 2005-05-06. Retrieved 2013-09-18.
- ↑ PCL Symbol Sets
- ↑ "Java SE documentation for Interface java.io.DataInput, subsection on Modified UTF-8". Oracle Corporation. 2015. Retrieved 2015-10-16.
- ↑ "The Java Virtual Machine Specification, section 4.4.7: "The CONSTANT_Utf8_info Structure"". Oracle Corporation. 2015. Retrieved 2015-10-16.
Java virtual machine UTF-8 strings never have embedded nulls.
- ↑ "Java Object Serialization Specification, chapter 6: Object Serialization Stream Protocol, section 2: Stream Elements". Oracle Corporation. 2010. Retrieved 2015-10-16.
[…] encoded in modified UTF-8.
- ↑ "Java Native Interface Specification, chapter 3: JNI Types and Data Structures, section: Modified UTF-8 Strings". Oracle Corporation. 2015. Retrieved 2015-10-16.
The JNI uses modified UTF-8 strings to represent various string types.
- ↑ "The Java Virtual Machine Specification, section 4.4.7: "The CONSTANT_Utf8_info Structure"". Oracle Corporation. 2015. Retrieved 2015-10-16.
[…] differences between this format and the "standard" UTF-8 format.
- ↑ "ART and Dalvik". Android Open Source Project. Retrieved 2013-04-09.
[T]he dex format encodes its string data in a de facto standard modified UTF-8 form, hereafter referred to as MUTF-8.
- ↑ "Tcler's Wiki: UTF-8 bit by bit (Revision 6)". 2009-04-25. Retrieved 2009-05-22.
In orthodox UTF-8, a NUL byte (\x00) is represented by a NUL byte. […] But […] we […] want NUL bytes inside […] strings […]
- ↑ Sapin, Simon (2016-03-11) [2014-09-25]. "The WTF-8 encoding". Archived from the original on 2016-05-24. Retrieved 2016-05-24.
- ↑ "WTF-8.com". 2006-05-18. Retrieved 2016-06-21.
- ↑ Speer, Rob (2015-05-21). "ftfy (fixes text for you) 4.0: changing less and fixing more". Retrieved 2016-06-21.
- ↑ "WTF-8, a transformation format of code page 1252". www-uxsup.csx.cam.ac.uk. Retrieved 2016-10-12.
- ↑ "The Unicode Standard - Chapter 2" (PDF). p. 30.
- ↑ "Extensible Markup Language (XML) 1.0 (Fifth Edition)". W3C. 2008-11-26. Retrieved 2013-02-08.
- ↑ Dürst, Martin. "Multilingual Forms". W3C. Retrieved 2013-02-08.
- ↑ "#418058 - iconv: half-smart on ascii compatible code conversion (shift-jis) - Debian Bug report logs". Bugs.debian.org. 2007-04-06. Retrieved 2014-06-13.
|Look up UTF-8 in Wiktionary, the free dictionary.|
There are several current definitions of UTF-8 in various standards documents:
- RFC 3629 / STD 63 (2003), which establishes UTF-8 as a standard Internet protocol element
- The Unicode Standard, Version 6.0, §3.9 D92, §3.10 D95 (2011)
- ISO/IEC 10646:2012 §9.1
They supersede the definitions given in the following obsolete works:
- ISO/IEC 10646-1:1993 Amendment 2 / Annex R (1996)
- The Unicode Standard, Version 5.0, §3.9 D92, §3.10 D95 (2007)
- The Unicode Standard, Version 4.0, §3.9–§3.10 (2003)
- The Unicode Standard, Version 2.0, Appendix A (1996)
- RFC 2044 (1996)
- RFC 2279 (1998)
- The Unicode Standard, Version 3.0, §2.3 (2000) plus Corrigendum #1 : UTF-8 Shortest Form (2000)
- Unicode Standard Annex #27: Unicode 3.1 (2001)
They are all the same in their general mechanics, with the main differences being on issues such as allowed range of code point values and safe handling of invalid input.
- Original UTF-8 paper (or pdf) for Plan 9 from Bell Labs
- RFC 5198 defines UTF-8 NFC for Network Interchange
- UTF-8 test pages by Andreas Prilop, Jost Gippert and the World Wide Web Consortium
- Unix/Linux: UTF-8/Unicode FAQ, Linux Unicode HOWTO, UTF-8 and Gentoo
- The Unicode/UTF-8-character table displays UTF-8 in a variety of formats (with Unicode and HTML encoding information)
- Characters, Symbols and the Unicode Miracle – Computerphile on YouTube