Lines Matching +full:0 +full:xaf

33 .\" If the F register is >0, we'll generate index entries on stderr for
41 .nr rF 0
49 .            nr % 0
103 characters in the 0x80\-0x9F range).
105 OpenSSL versions older than 1.1.0 do variant 2 only, and that is the reason why
111 0xC3 0xAF (which is the two characters "LATIN CAPITAL LETTER A WITH BREVE"
117 outcome in OpenSSL 1.1.0 and newer than in OpenSSL older than 1.1.0.
120 \& 0x00 0xC3 0x00 0xAF                    # OpenSSL older than 1.1.0
121 \& 0x00 0xEF                              # OpenSSL 1.1.0 and newer
125 than 1.1.0 was misinterpreted as ISO\-8859\-1 sequences.
141 encoding was ISO\-8859\-1 (i.e. "naïve" resulting in the byte sequence 0x6E 0x61
142 0xEF 0x76 0x65), and you're now in an environment where your default encoding
143 is UTF\-8 (i.e. "naïve" resulting in the byte sequence 0x6E 0x61 0xC3 0xAF 0x76
190 OpenSSL older than 1.1.0.
191 (for example, \f(CW\*(C`ï\*(C'\fR, which is 0xC3 0xAF when encoded in UTF\-8, would become 0xC3
192 0x83 0xC2 0xAF when re-encoded in the naïve manner.
193 The conversion to BMPString would then yield 0x00 0xC3 0x00 0xA4 0x00 0x00, the
194 erroneous/non\-compliant encoding used by OpenSSL older than 1.1.0)