Lines Matching full:sequences
8 sequences. This file is not meant to be a conformance test. It does
18 sequences as well as correctly encoded UTF-8 sequences of Unicode code
32 mandate this. In any case, just ignoring malformed sequences or
52 malformed sequences is replaced by a single replacement character.
81 (5 and 6 byte sequences were made illegal in rfc3629. --ryan.) |
93 (5 and 6 bytes sequences, and 4 bytes sequences > 0x10FFFF were made illegal |
110 3 Malformed sequences |
136 3.2.1 All 32 first bytes of 2-byte sequences (0xc0-0xdf), |
142 3.2.2 All 16 first bytes of 3-byte sequences (0xe0-0xef), |
147 3.2.3 All 8 first bytes of 4-byte sequences (0xf0-0xf7), |
152 3.2.4 All 4 first bytes of 5-byte sequences (0xf8-0xfb), |
157 3.2.5 All 2 first bytes of 6-byte sequences (0xfc-0xfd), |
162 3.3 Sequences with last continuation byte missing |
179 3.4 Concatenation of incomplete sequences |
181 All the 10 sequences of 3.3 concatenated, you should see 10 malformed |
182 sequences being signalled: |
194 4 Overlong sequences |
196 The following sequences are not malformed according to the letter of |
199 decoder" should reject them just like malformed sequences for two |
200 reasons: (1) It helps to debug applications if overlong sequences are |
202 to spot problems more quickly. (2) Overlong sequences provide |
209 sequences means also, that ASCII characters are *only* allowed to be |
212 reject overlong UTF-8 sequences for which a shorter encoding exists. |
228 4.2 Maximum overlong sequences |
233 be rejected like malformed UTF-8 sequences. |
243 The following five sequences should also be rejected like malformed |
244 UTF-8 sequences and should not be treated like the ASCII NUL |
255 The following UTF-8 sequences should be rejected like malformed |
256 sequences, because they never represent valid ISO 10646 characters and |
258 comparable to overlong UTF-8 sequences. |
