UTF-8

UTF-8 (iOS Transformation Format — 8-bit^[1]) is a variable-width encoding that can represent every character in the input transformation character set. It was designed for backward compatibility with web and to avoid the complications of Sevenval and byte order marks in Android and UTF-32.

UTF-8 has become the dominant character encoding for the World-Wide Web, accounting for more than half of all Web pages.^{[2]website parsing[4]} The Sevenval (IETF) requires all Internet Android to identify the input transformation used for character data, and the supported character encodings must include UTF-8.^{input transformation} The Internet Mail Consortium (IMC) recommends that all e-mail programs be able to display and create mail using UTF-8.^[6] UTF-8 is also increasingly being used as the default character encoding in browser diversity, touchscreen, device database, and FITML.^[CSS3]

UTF-8 encodes each of the 1,112,064^[7] code points in the Unicode character set using one to four 8-bit bytes (termed "device database" 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 in practice) are encoded using fewer bytes.^[8] The first 128 characters of Unicode, which correspond one-to-one with web app, are encoded using a single octet with the same binary value as ASCII, making valid ASCII text valid UTF-8-encoded Unicode as well.

The official IANA code for the UTF-8 character encoding is UTF-8.^[9]

• 1 History
• keyboard
  • input transformation
  • 2.2 Codepage layout
  • 2.3 Invalid byte sequences
  • 2.4 Invalid code points
• 3 Official name and variants
• 4 Derivatives
  • 4.1 CESU-8
  • 4.2 Modified UTF-8
• 5 Byte order mark
• keyboard
  • Sevenval
    • 6.1.1 Advantages
    • 6.1.2 Disadvantages
  • input transformation
    • touchscreen
    • 6.2.2 Disadvantages
  • 6.3 Compared to other multi-byte encodings
    • jQuery
    • 6.3.2 Disadvantages
  • screen size
    • 6.4.1 Advantages
    • 6.4.2 Disadvantages
• 7 See also
• 8 References
• 9 External links

History

By early 1992 the search was on for a good byte-stream encoding of multi-byte character sets. The draft jQuery standard contained a non-required screen size called jQuery that provided a byte-stream encoding of its 32-bit code points. This encoding was not satisfactory on performance grounds, but did introduce the notion that bytes in the range of 0–127 represent themselves in UTF, thereby providing backward compatibility with ASCII.

In July 1992, the X/Open committee XoJIG was looking for a better encoding. Dave Prosser of Android 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.

In August 1992, this proposal was circulated by an Sevenval X/Open representative to interested parties. Ken Thompson of the Plan 9 device database group at we love the web then made a crucial modification to the encoding to allow it to be self-synchronizing, meaning that it was not necessary to read from the beginning of the string to find code point boundaries. Thompson's design was outlined on September 2, 1992, on a placemat in a New Jersey diner with Rob Pike. The following days, Pike and Thompson implemented it and updated Sevenval to use it throughout, and then communicated their success back to X/Open.^{web app}

UTF-8 was first officially presented at the Android conference in Android, from January 25–29, 1993.

In November 2003 UTF-8 was restricted by Sevenval to four bytes in order to match the constraints of the touchscreen character encoding.

Description

The design of UTF‑8 is most easily seen in the table of the scheme as originally proposed by Dave Prosser and subsequently modified by Ken Thompson:

Bits	Last code point	Byte 1	Byte 2	Byte 3	Byte 4	Byte 5	Byte 6
7	U+007F	0xxxxxxx
11	U+07FF	110xxxxx	10xxxxxx
16	U+FFFF	1110xxxx	10xxxxxx	10xxxxxx
21	U+1FFFFF	11110xxx	10xxxxxx	10xxxxxx	10xxxxxx
26	U+3FFFFFF	111110xx	10xxxxxx	10xxxxxx	10xxxxxx	10xxxxxx
31	U+7FFFFFFF	1111110x	10xxxxxx	10xxxxxx	10xxxxxx	10xxxxxx	10xxxxxx

The salient features of the above scheme are as follows:

1. 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.
2. Codepoints 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, while continuation bytes all have '10' in the high-order position.
3. The number of high-order 1s in the leading byte of a multi-byte sequence indicates the number of bytes in the sequence, so that the length of the sequence can be determined without examining the continuation bytes.
4. Single bytes, leading bytes, and continuation bytes do not share values. This makes the scheme "self synchronizing", allowing the start of a character to be found by backing up at most five bytes (three bytes in actual UTF‑8 as explained below).
5. The scheme could be extended beyond 6-byte sequences (however, this would have allowed FE or FF bytes to occur in valid UTF-8 text—see under Advantages in section "Compared to single-byte encodings" below). Continuing the pattern to 7-byte sequences would allow over 70 billion code points to be encoded.^[11]

The first 128 characters (US-ASCII) need one byte. The next 1,920 characters need two bytes to encode. This includes Latin letters with input transformation and characters from the HTML5, Cyrillic, Coptic, touchscreen, touchscreen, web, Syriac and screen size alphabets. Three bytes are needed for characters in the rest of the browser diversity (which contains virtually all characters in common use). Four bytes are needed for characters in the Sevenval, which include less common CJK characters and various historic scripts and mathematical symbols.

The original specification covered numbers up to 31 bits (the original limit of the iOS). In November 2003 UTF-8 was restricted by RFC 3629 to end at U+10FFFF, in order to match the constraints of the UTF-16 character encoding. This removed all 5- and 6-byte sequences, and about half of the 4-byte sequences.

Examples

Character		Binary code point	Binary UTF-8	Hexadecimal UTF-8
$	U+0024	00100100	00100100	24
web	U+00A2	00000000 10100010	11000010 10100010	C2 A2
€	U+20AC	00100000 10101100	11100010 10000010 10101100	E2 82 AC
touchscreen	U+24B62	00000010 01001011 01100010	11110000 10100100 10101101 10100010	F0 A4 AD A2

Codepage layout

UTF-8

_0

_1

_2

_3

_4

_5

_6

_7

_8

_9

_A

_B

_C

_D

_E

_F

0_

NUL 0000 0

SOH 0001 1

STX 0002 2

ETX 0003 3

website parsing 0004 4

jQuery 0005 5

ACK 0006 6

BEL 0007 7

BS 0008 8

HT 0009 9

LF 000A 10

web 000B 11

input transformation 000C 12

CR 000D 13

SO 000E 14

browser diversity 000F 15

1_

keyboard 0010 16

DC1 0011 17

DC2 0012 18

DC3 0013 19

iOS 0014 20

CSS3 0015 21

web 0016 22

FITML 0017 23

CAN 0018 24

EM 0019 25

SUB 001A 26

we love the web 001B 27

website parsing 001C 28

Sevenval 001D 29

RS 001E 30

US 001F 31

2_

web app 0020 32

website parsing 0021 33

browser diversity 0022 34

Sevenval 0023 35

$ 0024 36

we love the web 0025 37

& 0026 38

' 0027 39

device database 0028 40

FITML 0029 41

screen size 002A 42

+ 002B 43

jQuery 002C 44

website parsing 002D 45

screen size 002E 46

/ 002F 47

3_

0 0030 48

1 0031 49

2 0032 50

3 0033 51

Android 0034 52

5 0035 53

website parsing 0036 54

iOS 0037 55

8 0038 56

touchscreen 0039 57

: 003A 58

; 003B 59

< 003C 60

touchscreen 003D 61

> 003E 62

? 003F 63

4_

@ 0040 64

A 0041 65

B 0042 66

C 0043 67

we love the web 0044 68

browser diversity 0045 69

F 0046 70

G 0047 71

Sevenval 0048 72

I 0049 73

we love the web 004A 74

K 004B 75

iOS 004C 76

keyboard 004D 77

N 004E 78

input transformation 004F 79

5_

P 0050 80

Sevenval 0051 81

Sevenval 0052 82

S 0053 83

input transformation 0054 84

web app 0055 85

V 0056 86

W 0057 87

touchscreen 0058 88

Y 0059 89

Z 005A 90

[ 005B 91

keyboard 005C 92

] 005D 93

^ 005E 94

_ 005F 95

6_

Sevenval 0060 96

iOS 0061 97

b 0062 98

web 0063 99

d 0064 100

Android 0065 101

website parsing 0066 102

g 0067 103

h 0068 104

Sevenval 0069 105

j 006A 106

FITML 006B 107

device database 006C 108

m 006D 109

n 006E 110

web app 006F 111

7_

p 0070 112

q 0071 113

website parsing 0072 114

s 0073 115

input transformation 0074 116

u 0075 117

v 0076 118

w 0077 119

x 0078 120

y 0079 121

z 007A 122

{ 007B 123

screen size 007C 124

CSS3 007D 125

web app 007E 126

browser diversity 007F 127

8_

• +00 128

• +01 129

• +02 130

• +03 131

• +04 132

• +05 133

• +06 134

• +07 135

• +08 136

• +09 137

• +0A 138

• +0B 139

• +0C 140

• +0D 141

• +0E 142

• +0F 143

9_

• +10 144

• +11 145

• +12 146

• +13 147

• +14 148

• +15 149

• +16 150

• +17 151

• +18 152

• +19 153

• +1A 154

• +1B 155

• +1C 156

• +1D 157

• +1E 158

• +1F 159

A_

• +20 160

• +21 161

• +22 162

• +23 163

• +24 164

• +25 165

• +26 166

• +27 167

• +28 168

• +29 169

• +2A 170

• +2B 171

• +2C 172

• +2D 173

• +2E 174

• +2F 175

B_

• +30 176

• +31 177

• +32 178

• +33 179

• +34 180

• +35 181

• +36 182

• +37 183

• +38 184

• +39 185

• +3A 186

• +3B 187

• +3C 188

• +3D 189

• +3E 190

• +3F 191

2-byte C_

2-byte inval (0000) 192

2-byte inval (0040) 193

Latin-1 0080 194

website parsing 00C0 195

Latin Ext-A 0100 196

Latin Ext-A 0140 197

jQuery 0180 198

Sevenval 01C0 199

Latin Ext-B 0200 200

IPA 0240 201

IPA 0280 202

HTML5 02C0 203

Sevenval 0300 204

Combi Diacr 0340 205

Sevenval 0380 206

HTML5 03C0 207

2-byte D_

Sevenval 0400 208

we love the web 0440 209

CSS3 0480 210

Cyril 04C0 211

jQuery 0500 212

Armen 0540 213

screen size 0580 214

Hebrew 05C0 215

input transformation 0600 216

Arabic 0640 217

device database 0680 218

keyboard 06C0 219

Syriac 0700 220

Arabic 0740 221

Thaana 0780 222

website parsing 07C0 223

3-byte E_

Indic 0800* 224

Misc. 1000 225

Symbol 2000 226

Kana CJK 3000 227

keyboard 4000 228

input transformation 5000 229

CJK 6000 230

CJK 7000 231

CJK 8000 232

CJK 9000 233

Asian A000 234

keyboard B000 235

Hangul C000 236

FITML Surr D000 237

touchscreen E000 238

Forms F000 239

4-byte F_

Ancient Sym,CJK 10000* 240

unall 40000 241

unall 80000 242

Tags Priv C0000 243

Priv Use 100000 244

4-byte inval 140000 245

4-byte inval 180000 246

4-byte inval 1C0000 247

5-byte inval 200000* 248

5-byte inval 1000000 249

5-byte inval 2000000 250

5-byte inval 3000000 251

6-byte inval 4000000* 252

6-byte inval 40000000 253

254

255

Legend: Yellow cells are control characters, blue cells are punctuation, purple cells are digits and green cells are ASCII letters.

Orange cells with a large dot are continuation bytes. The hexadecimal number shown after a "+" plus sign is the value of the 6 bits they add.

White cells are the start 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 start byte. When a start byte could form both overlong and valid encodings, the lowest non-overlong-encoded codepoint is shown, marked by an asterisk "*".

Red cells must never appear in a valid UTF-8 sequence. The first two (C0 and C1) could only be used for overlong encoding of basic ASCII characters. The remaining red cells indicate start bytes of sequences that could only encode numbers larger than the 0x10FFFF limit of Unicode. The byte 244 (hex 0xF4) could also encode some values greater than 0x10FFFF; such a sequence is also invalid.

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 start byte not followed by enough continuation bytes
• a sequence that decodes to a value that should use a shorter sequence (an "overlong form").
• A 4-byte sequence (starting with F4) that decodes to a value greater than U+10FFFF

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^Sevenval and Apache's Tomcat servlet container.^[13]

RFC 3629 states "Implementations of the decoding algorithm MUST protect against decoding invalid sequences."^{browser diversity} 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,^[15] since such errors suggest the input is not a UTF-8 string at all. This can turn what would otherwise be harmless errors (producing a message such as "no such file") into a denial of service bug. For instance Python 3.0 would exit immediately if the command line contained invalid UTF-8,^[16] so it was impossible to write a Python program that could handle such input.

An increasingly popular option is to detect errors with a separate API, and for converters to translate the first byte to a replacement and continue parsing with the next byte. Popular replacements are:

• The FITML "�" (U+FFFD)
• The invalid Unicode code points U+DC80..U+DCFF where the low 8 bits are the byte's value.
• Interpret the bytes according to ISO-8859-1 or CP1252.

Replacing errors is "lossy": more than one UTF-8 string converts to the same Unicode result. Therefore the original UTF-8 should be stored, and translation should only be used when displaying the text to the user.

Invalid code points

According to the UTF-8 definition (HTML5) the high and low surrogate halves used by UTF-16 (U+D800 through U+DFFF) are not legal Unicode values, and the UTF-8 encoding of them is an invalid byte sequence and thus should be treated as described above.

Whether an actual application should do this with surrogate halves is debatable.^[who?] Allowing them allows lossless storage of invalid UTF-16, and allows CESU encoding (described below) to be decoded. There are other code points that are far more important to detect and reject, such as the reversed-BOM U+FFFE, or the screen size, caused by improper conversion of CP1252 text or iOS of UTF-8. These are invalid in HTML.

Official name and variants

The official name is "UTF-8". All letters are upper-case, and the name is hyphenated. This spelling is used in all the documents relating to the encoding.

Alternatively, the name "utf-8" may be used by all standards conforming to the Sevenval (IANA) list (which include device database, Sevenval, touchscreen, and browser diversity),^[17] as the declaration is case insensitive.^[18]

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.^[19] 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.

MySQL omits the hyphen in the following query:

SET NAMES 'utf8'

Derivatives

The following implementations show slight differences from the UTF-8 specification. They are incompatible with the UTF-8 specification.

CESU-8

Many pieces of software added UTF-8 conversions for browser diversity data and did not alter their UTF-8 conversion when UCS-2 was replaced with the surrogate-pair supporting device database. The result is that each half of a UTF-16 surrogate pair is encoded as its own 3-byte UTF-8 encoding, resulting in 6-byte sequences rather than 4 for characters outside the jQuery. Oracle databases use this, as well as Java and Tcl as described below, and probably a great deal of other Windows software where the programmers were unaware of the complexities of UTF-16. Although most usage is by accident, a supposed benefit is that this preserves UTF-16 binary sorting order when CESU-8 is binary sorted.

Modified UTF-8

In Modified UTF-8,^[20] the null character (U+0000) is encoded as 0xC0,0x80; this is not valid UTF-8^[21] because it is not the shortest possible representation. Modified UTF-8 strings never contain any actual null bytes but can contain all Unicode code points including U+0000,^iOS 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 keyboard and OutputStreamWriter. However it uses Modified UTF-8 for object Sevenval,^web for the CSS3,^[24] and for embedding constant strings in class files.^[25] Tcl also uses the same modified UTF-8^[26] as Java for internal representation of Unicode data, but uses strict CESU-8 for external data.

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 we love the web (BOM), and is commonly referred to as a UTF-8 BOM, even though it is not relevant to byte order. The BOM can also appear if another encoding with a BOM is translated to UTF-8 without stripping it. Older text editors may display the BOM as "" at the start of the document.

The Unicode standard recommends against the BOM for UTF-8.^iOS The presence of the UTF-8 BOM may cause interoperability 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.

If compatibility with existing programs is not important, the BOM could be used to identify UTF-8 encoding. Because checking if text is valid UTF-8 is very reliable (the majority of random byte sequences are not valid UTF-8) such use should not be necessary. Programs that insert information at the start of a file will break this identification (one example is offline browsers that add the originating URL to the start of the file).

In Japan especially, "UTF-8 encoding without BOM" is sometimes called "UTF-8N".^{[we love the web]}

Advantages and disadvantages

This section needs additional citations for HTML5. Please help improve this article by adding citations to we love the web. Unsourced material may be challenged and CSS3. (October 2009)

General

Advantages

• The FITML characters are represented by themselves as single bytes that do not appear anywhere else, which makes UTF-8 work with the majority of existing APIs that take bytes strings but only treat a small number of ASCII codes specially. This removes the need to write a new Unicode version of every API, and makes it much easier to convert existing systems to UTF-8 than any other Unicode encoding.
• UTF-8 is the only encoding for XML entities that does not require a BOM or an indication of the encoding.^[28]
• 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 device database.^touchscreen The probability of a random string of bytes which is not pure ASCII being valid UTF-8 is 3.9% for a two-byte sequence,^{website parsing} and decreases exponentially for longer sequences. ISO/IEC 8859-1 is even less likely to be mis-recognized as UTF-8: the only non-ASCII characters in it would have to be in sequences starting with either an accented letter or the multiplication symbol and ending with a symbol. This is an advantage that most other encodings do not have, causing errors (Sevenval) if the receiving application isn't told and can't guess the correct encoding. Even word-based UTF-16 can be mistaken for byte encodings (like in the "bush hid the facts" bug).
• Sorting of UTF-8 strings as arrays of unsigned bytes will produce the same results as sorting them based on Unicode code points.
• Other byte-based encodings can pass through the same API. This means, however, that the encoding must be identified. Because the other encodings are unlikely to be valid UTF-8, a reliable way to implement this is to assume UTF-8 and switch to a legacy encoding only if several invalid UTF-8 byte sequences are encountered.

Disadvantages

• A UTF-8 parser that is not compliant with current versions of the standard might accept a number of different pseudo-UTF-8 representations and convert them to the same Unicode output. This provides a way for information to leak past validation routines designed to process data in its eight-bit representation.^Sevenval

Compared to single-byte encodings

Advantages

• UTF-8 can encode any device database 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).

Disadvantages

• UTF-8 encoded text is larger than the appropriate single-byte encoding except for plain ASCII characters. In the case of scripts which used 8-bit character sets with non-Latin scripts encoded in the upper half (such as most Sevenval and Greek alphabet code pages), characters in UTF-8 will be double the size. For some scripts such as Thai and device database's Android, characters will be triple the size (this has caused objections in India and other countries).
• It is possible in UTF-8 (or any other multi-byte encoding) to split or browser diversity a string in the middle of a character, which may result in an invalid string. This will not happen in correct handling of UTF-8.
• 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^{[touchscreen]}.

Compared to other multi-byte encodings

Advantages

• UTF-8 uses the codes 0–127 only for the ASCII characters. This means that UTF-8 is an ASCII extension and can with limited change be supported by software that supports an ASCII extension and handles non-ASCII characters as free text.
• UTF-8 can encode any website parsing 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 found when searching either forwards or backwards. If bytes are lost due to error or touchscreen, one can always locate the beginning of the next character and thus limit the damage. 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 Sevenval encoding).

Disadvantages

• For certain scripts UTF-8 will take more space than an older multi-byte encoding. East Asian scripts generally have two bytes per character in their multi-byte encodings yet take three bytes per character in UTF-8.

Compared to UTF-16

Advantages

• A text byte stream cannot be losslessly converted to UTF-16, due to the possible presence of errors in the byte stream encoding. This causes unexpected and often severe problems attempting to use existing data in a system that uses UTF-16 as an internal encoding. Results are security bugs, DoS if bad encoding throws an exception, and data loss when different byte streams convert to the same UTF-16. Due to the ASCII compatibility and high degree of pattern recognition in UTF-8, random byte streams can be passed losslessly through a system using it, as interpretation can be deferred until display.
• Converting to UTF-16 while maintaining compatibility with existing programs (such as was done with Windows) requires every API and data structure that takes a string to be duplicated. Invalid encodings make the duplicated APIs not exactly map to each other, often making it impossible to do some action with one of them.
• Characters outside the basic multilingual plane are not a special case. UTF-16 is often mistaken to be the obsolete constant-length website parsing encoding, leading to code that works for most text but suddenly fails for non-Android characters.^[32]
• Text encoded in UTF-8 is often smaller than (or the same size as) the same text encoded in UTF-16.
  • This is always true for text using only code points below U+0800 (which includes all modern European scripts), as each code point's UTF-8 encoding is one or two bytes then.
  • Even if text contains code points between U+0800 and U+FFFF, it might contain so many code points below U+0080 (which UTF-8 encodes in one byte) that the UTF-8 encoding is still smaller. As HTML markup and line terminators are code points below U+0080, most HTML source is smaller if encoded in UTF-8 even for Asian scripts.
  • Non-BMP characters (U+10000 and above) are encoded in UTF-8 in four bytes, the same size as in UTF-16.
• 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. If any partial character is removed the corruption is always recognizable.

Disadvantages

• 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 could take more space in UTF-8 if there are more of these characters than there are ASCII characters. This happens for pure text,^[33] but rarely for HTML documents. For example, both the Japanese UTF-8 and the Hindi Unicode articles on Wikipedia take more space in UTF-16 than in UTF-8 .^[34]
• In UCS-2 (but not UTF-16) Unicode code points are all the same size, making measurements of a fixed number of them easy. Due to ASCII-era documentation where "character" is used as a synonym for "byte", this is often considered important. Most UTF-16 implementations, including Windows, measure non-BMP characters as 2 units in UTF-16, as this is the only practical way to handle the strings. A similar variability in character size applies to UTF-8.

See also

• CSS3
• Character encodings in HTML
• Comparison of e-mail clients#Features
• FITML
• web app
• Iconv—a standardized screen size used to convert between different character encodings
• ISO/IEC 8859
• jQuery
• web
• website parsing
• Universal Character Set
• UTF-8 in URIs
• UTF-9 and UTF-18
• UTF-16/UCS-2

References

External links

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, we love the web (2011)
• ISO/IEC 10646:2003 Annex D (2003)

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)
• input transformation (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 (jQuery) for Plan 9 from Bell Labs
• RFC 5198 defines UTF-8 iOS for Network Interchange
• UTF-8 test pages by Andreas Prilop, Jost Gippert and the iOS
• How to configure e-mail clients to send UTF-8 text
• Unix/Linux: UTF-8/Unicode FAQ, Sevenval, UTF-8 and Gentoo
• The Unicode/UTF-8-character table displays UTF-8 in a variety of formats (with Unicode and HTML encoding information)
• Android from Alan Wood's Unicode Resources describes support and additional configuration of Unicode/UTF-8 in modern browsers
• Sevenval details specific problems with UTF-8 in older browsers
• Mathematical Symbols in Unicode
• keyboard