0xff can never appear in a valid UTF-8 bytestream. U+FFFF is not a valid Unicode character. (So says my copy of The Unicode Standard 5.0.)
-Kyle H On May 10, 2007, at 10:49 AM, Nelson Bolyard wrote: > j.fabre wrote: > >> The common name´s length si 51, and there are the hexadecimal >> print of >> the commonName : > > [snip] >> <20 --> > >> <41 -->A> >> <47 -->G> >> <ff ff ff dc -->Ü> ---------------------> Here is the problem, but >> this >> character could be coded in UTF-8, since I know that UTF-8 chars >> can be >> coded using until 4 bytes. >> <45 -->E> >> <52 -->R> >> <4f -->O> >> <20 --> > > > The character ff ff ff dc is NOT the character for umlauted U. > It is the Unicode code value for a character that is not valid UTF8. > when converting from another character set/encoding to UTF8, and > characters that cannot be converted get replaced with that. > But If I recall correctly, that is not the UTF8 value for that > character. > That is the UCS4 or UCS2 Unicode value. > So I suspect there's some character set conversion problem going on. > > > _______________________________________________ > dev-tech-crypto mailing list > dev-tech-crypto@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-crypto _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
