Re:Is the use of “utf8=✓” preferable to “utf8=true”?
by kbolino on Friday October 19, 2012 @08:37AM
(#4673220)
Not to detract from your points, all good, but:
0xC2A2 will be rendered as ¢ only if it's encoded in UTF-16/UCS-2 big endian and misinterpreted as ISO-8859-1/Windows-1252.
If it's encoded in little endian (much more common on Intel x86 computers), then it would be rendered as ¢Â when misinterpreted.
Re:Is the use of “utf8=✓” preferable to “utf8=true”?
by kelnos on Saturday October 20, 2012 @08:27AM
(#4676901)
That doesn't really make sense. If someone's intending to encode ¢ in utf-8, endianness does not come into play, as it's a stream of octets, not of anything larger that you can chunk such that you could swap bytes.
At any rate, if you were to encode ¢ in UTF-16BE, it would be 0x00a2, not 0xc2a2. If a piece of software then misinterpreted it as latin1, likely you'd get nothing at all due to the embedded NUL.
$ echo -n ¢ | iconv -f UTF-8 -t UTF-16BE | hexdump -C
00000000 00 a2 |..|
Re:Is the use of “utf8=✓” preferable to “utf8=true”?
by kbolino on Thursday October 25, 2012 @08:04AM
(#4697264)
"That doesn't really make sense."
Indeed. I either completely misread the parent post, or else it said something different when I responded to it (knowing myself, I'm going with the former).
It gets far worse in 3-byte UTF8 characters, but I don't believe any of them exist natively in Latin1 (see: euro symbol)
Assuming I'm reading these various character tables right, at least ;)
So a more accurate version of what you quoted would be "UTF-8 and Latin-1 only overlap for 7-bit ASCII"