~ chicken-core (master) /tests/UTF-8-test.txt
Trap1UTF-8 decoder capability and stress test2----------------------------------------34Markus Kuhn <http://www.cl.cam.ac.uk/~mgk25/> - 2015-08-28 - CC BY 4.056This test file can help you examine, how your UTF-8 decoder handles7various types of correct, malformed, or otherwise interesting UTF-88sequences. This file is not meant to be a conformance test. It does9not prescribe any particular outcome. Therefore, there is no way to10"pass" or "fail" this test file, even though the text does suggest a11preferable decoder behaviour at some places. Its aim is, instead, to12help you think about, and test, the behaviour of your UTF-8 decoder on a13systematic collection of unusual inputs. Experience so far suggests14that most first-time authors of UTF-8 decoders find at least one15serious problem in their decoder using this file.1617The test lines below cover boundary conditions, malformed UTF-818sequences, as well as correctly encoded UTF-8 sequences of Unicode code19points that should never occur in a correct UTF-8 file.2021According to ISO 10646-1:2000, sections D.7 and 2.3c, a device22receiving UTF-8 shall interpret a "malformed sequence in the same way23that it interprets a character that is outside the adopted subset" and24"characters that are not within the adopted subset shall be indicated25to the user" by a receiving device. One commonly used approach in26UTF-8 decoders is to replace any malformed UTF-8 sequence by a27replacement character (U+FFFD), which looks a bit like an inverted28question mark, or a similar symbol. It might be a good idea to29visually distinguish a malformed UTF-8 sequence from a correctly30encoded Unicode character that is just not available in the current31font but otherwise fully legal, even though ISO 10646-1 doesn't32mandate this. In any case, just ignoring malformed sequences or33unavailable characters does not conform to ISO 10646, will make34debugging more difficult, and can lead to user confusion.3536Please check, whether a malformed UTF-8 sequence is (1) represented at37all, (2) represented by exactly one single replacement character (or38equivalent signal), and (3) the following quotation mark after an39illegal UTF-8 sequence is correctly displayed, i.e. proper40resynchronization takes place immediately after any malformed41sequence. This file says "THE END" in the last line, so if you don't42see that, your decoder crashed somehow before, which should always be43cause for concern.4445All lines in this file are exactly 79 characters long (plus the line46feed). In addition, all lines end with "|", except for the two test47lines 2.1.1 and 2.2.1, which contain non-printable ASCII controls48U+0000 and U+007F. If you display this file with a fixed-width font,49these "|" characters should all line up in column 79 (right margin).50This allows you to test quickly, whether your UTF-8 decoder finds the51correct number of characters in every line, that is whether each52malformed sequences is replaced by a single replacement character.5354Note that, as an alternative to the notion of malformed sequence used55here, it is also a perfectly acceptable (and in some situations even56preferable) solution to represent each individual byte of a malformed57sequence with a replacement character. If you follow this strategy in58your decoder, then please ignore the "|" column.596061Here come the tests: |62 |631 Some correct UTF-8 text |64 |65You should see the Greek word 'kosme': "κόσμε" |66 |672 Boundary condition test cases |68 |692.1 First possible sequence of a certain length |70 |712.1.1 1 byte (U-00000000): " "722.1.2 2 bytes (U-00000080): "" |732.1.3 3 bytes (U-00000800): "ࠀ" |742.1.4 4 bytes (U-00010000): "𐀀" |752.1.5 5 bytes (U-00200000): "" |762.1.6 6 bytes (U-04000000): "" |77 |782.2 Last possible sequence of a certain length |79 |802.2.1 1 byte (U-0000007F): ""812.2.2 2 bytes (U-000007FF): "߿" |822.2.3 3 bytes (U-0000FFFF): "" |832.2.4 4 bytes (U-001FFFFF): "" |842.2.5 5 bytes (U-03FFFFFF): "" |852.2.6 6 bytes (U-7FFFFFFF): "" |86 |872.3 Other boundary conditions |88 |892.3.1 U-0000D7FF = ed 9f bf = "" |902.3.2 U-0000E000 = ee 80 80 = "" |912.3.3 U-0000FFFD = ef bf bd = "�" |922.3.4 U-0010FFFF = f4 8f bf bf = "" |932.3.5 U-00110000 = f4 90 80 80 = "" |94 |953 Malformed sequences |96 |973.1 Unexpected continuation bytes |98 |99Each unexpected continuation byte should be separately signalled as a |100malformed sequence of its own. |101 |1023.1.1 First continuation byte 0x80: "" |1033.1.2 Last continuation byte 0xbf: "" |104 |1053.1.3 2 continuation bytes: "" |1063.1.4 3 continuation bytes: "" |1073.1.5 4 continuation bytes: "" |1083.1.6 5 continuation bytes: "" |1093.1.7 6 continuation bytes: "" |1103.1.8 7 continuation bytes: "" |111 |1123.1.9 Sequence of all 64 possible continuation bytes (0x80-0xbf): |113 |114 " |115 |116 |117 " |118 |1193.2 Lonely start characters |120 |1213.2.1 All 32 first bytes of 2-byte sequences (0xc0-0xdf), |122 each followed by a space character: |123 |124 " |125 " |126 |1273.2.2 All 16 first bytes of 3-byte sequences (0xe0-0xef), |128 each followed by a space character: |129 |130 " " |131 |1323.2.3 All 8 first bytes of 4-byte sequences (0xf0-0xf7), |133 each followed by a space character: |134 |135 " " |136 |1373.2.4 All 4 first bytes of 5-byte sequences (0xf8-0xfb), |138 each followed by a space character: |139 |140 " " |141 |1423.2.5 All 2 first bytes of 6-byte sequences (0xfc-0xfd), |143 each followed by a space character: |144 |145 " " |146 |1473.3 Sequences with last continuation byte missing |148 |149All bytes of an incomplete sequence should be signalled as a single |150malformed sequence, i.e., you should see only a single replacement |151character in each of the next 10 tests. (Characters as in section 2) |152 |1533.3.1 2-byte sequence with last byte missing (U+0000): "" |1543.3.2 3-byte sequence with last byte missing (U+0000): "" |1553.3.3 4-byte sequence with last byte missing (U+0000): "" |1563.3.4 5-byte sequence with last byte missing (U+0000): "" |1573.3.5 6-byte sequence with last byte missing (U+0000): "" |1583.3.6 2-byte sequence with last byte missing (U-000007FF): "" |1593.3.7 3-byte sequence with last byte missing (U-0000FFFF): "" |1603.3.8 4-byte sequence with last byte missing (U-001FFFFF): "" |1613.3.9 5-byte sequence with last byte missing (U-03FFFFFF): "" |1623.3.10 6-byte sequence with last byte missing (U-7FFFFFFF): "" |163 |1643.4 Concatenation of incomplete sequences |165 |166All the 10 sequences of 3.3 concatenated, you should see 10 malformed |167sequences being signalled: |168 |169 "" |170 |1713.5 Impossible bytes |172 |173The following two bytes cannot appear in a correct UTF-8 string |174 |1753.5.1 fe = "" |1763.5.2 ff = "" |1773.5.3 fe fe ff ff = "" |178 |1794 Overlong sequences |180 |181The following sequences are not malformed according to the letter of |182the Unicode 2.0 standard. However, they are longer then necessary and |183a correct UTF-8 encoder is not allowed to produce them. A "safe UTF-8 |184decoder" should reject them just like malformed sequences for two |185reasons: (1) It helps to debug applications if overlong sequences are |186not treated as valid representations of characters, because this helps |187to spot problems more quickly. (2) Overlong sequences provide |188alternative representations of characters, that could maliciously be |189used to bypass filters that check only for ASCII characters. For |190instance, a 2-byte encoded line feed (LF) would not be caught by a |191line counter that counts only 0x0a bytes, but it would still be |192processed as a line feed by an unsafe UTF-8 decoder later in the |193pipeline. From a security point of view, ASCII compatibility of UTF-8 |194sequences means also, that ASCII characters are *only* allowed to be |195represented by ASCII bytes in the range 0x00-0x7f. To ensure this |196aspect of ASCII compatibility, use only "safe UTF-8 decoders" that |197reject overlong UTF-8 sequences for which a shorter encoding exists. |198 |1994.1 Examples of an overlong ASCII character |200 |201With a safe UTF-8 decoder, all of the following five overlong |202representations of the ASCII character slash ("/") should be rejected |203like a malformed UTF-8 sequence, for instance by substituting it with |204a replacement character. If you see a slash below, you do not have a |205safe UTF-8 decoder! |206 |2074.1.1 U+002F = c0 af = "" |2084.1.2 U+002F = e0 80 af = "" |2094.1.3 U+002F = f0 80 80 af = "" |2104.1.4 U+002F = f8 80 80 80 af = "" |2114.1.5 U+002F = fc 80 80 80 80 af = "" |212 |2134.2 Maximum overlong sequences |214 |215Below you see the highest Unicode value that is still resulting in an |216overlong sequence if represented with the given number of bytes. This |217is a boundary test for safe UTF-8 decoders. All five characters should |218be rejected like malformed UTF-8 sequences. |219 |2204.2.1 U-0000007F = c1 bf = "" |2214.2.2 U-000007FF = e0 9f bf = "" |2224.2.3 U-0000FFFF = f0 8f bf bf = "" |2234.2.4 U-001FFFFF = f8 87 bf bf bf = "" |2244.2.5 U-03FFFFFF = fc 83 bf bf bf bf = "" |225 |2264.3 Overlong representation of the NUL character |227 |228The following five sequences should also be rejected like malformed |229UTF-8 sequences and should not be treated like the ASCII NUL |230character. |231 |2324.3.1 U+0000 = c0 80 = "" |2334.3.2 U+0000 = e0 80 80 = "" |2344.3.3 U+0000 = f0 80 80 80 = "" |2354.3.4 U+0000 = f8 80 80 80 80 = "" |2364.3.5 U+0000 = fc 80 80 80 80 80 = "" |237 |2385 Illegal code positions |239 |240The following UTF-8 sequences should be rejected like malformed |241sequences, because they never represent valid ISO 10646 characters and |242a UTF-8 decoder that accepts them might introduce security problems |243comparable to overlong UTF-8 sequences. |244 |2455.1 Single UTF-16 surrogates |246 |2475.1.1 U+D800 = ed a0 80 = "" |2485.1.2 U+DB7F = ed ad bf = "" |2495.1.3 U+DB80 = ed ae 80 = "" |2505.1.4 U+DBFF = ed af bf = "" |2515.1.5 U+DC00 = ed b0 80 = "" |2525.1.6 U+DF80 = ed be 80 = "" |2535.1.7 U+DFFF = ed bf bf = "" |254 |2555.2 Paired UTF-16 surrogates |256 |2575.2.1 U+D800 U+DC00 = ed a0 80 ed b0 80 = "" |2585.2.2 U+D800 U+DFFF = ed a0 80 ed bf bf = "" |2595.2.3 U+DB7F U+DC00 = ed ad bf ed b0 80 = "" |2605.2.4 U+DB7F U+DFFF = ed ad bf ed bf bf = "" |2615.2.5 U+DB80 U+DC00 = ed ae 80 ed b0 80 = "" |2625.2.6 U+DB80 U+DFFF = ed ae 80 ed bf bf = "" |2635.2.7 U+DBFF U+DC00 = ed af bf ed b0 80 = "" |2645.2.8 U+DBFF U+DFFF = ed af bf ed bf bf = "" |265 |2665.3 Noncharacter code positions |267 |268The following "noncharacters" are "reserved for internal use" by |269applications, and according to older versions of the Unicode Standard |270"should never be interchanged". Unicode Corrigendum #9 dropped the |271latter restriction. Nevertheless, their presence in incoming UTF-8 data |272can remain a potential security risk, depending on what use is made of |273these codes subsequently. Examples of such internal use: |274 |275 - Some file APIs with 16-bit characters may use the integer value -1 |276 = U+FFFF to signal an end-of-file (EOF) or error condition. |277 |278 - In some UTF-16 receivers, code point U+FFFE might trigger a |279 byte-swap operation (to convert between UTF-16LE and UTF-16BE). |280 |281With such internal use of noncharacters, it may be desirable and safer |282to block those code points in UTF-8 decoders, as they should never |283occur legitimately in incoming UTF-8 data, and could trigger unsafe |284behaviour in subsequent processing. |285 |286Particularly problematic noncharacters in 16-bit applications: |287 |2885.3.1 U+FFFE = ef bf be = "" |2895.3.2 U+FFFF = ef bf bf = "" |290 |291Other noncharacters: |292 |2935.3.3 U+FDD0 .. U+FDEF = ""|294 |2955.3.4 U+nFFFE U+nFFFF (for n = 1..10) |296 |297 " |298 " |299 |300THE END |