Re: Make Unicode bugs release critical?
-----BEGIN PGP SIGNED MESSAGE-----
Am Fr den 11. Feb 2011 um 10:37 schrieb Lars Wirzenius:
> The first Unicode standard was published in 1991. That's twenty years
> ago. Any software that processes text at all and is incapable of dealing
> with UTF-8 should be considered with extreme suspicion. Making all such
> bugs be release critical (which includes the notion that release
> managers may ignore the bug in particular cases) sounds like a good way
> to get things under control.
I think you are mixing stuff together. First there is unicode. There are
several definitions for unicode (unicode-16, unicode-32, ...) but UTF-8
is not unicode it is just one implementation of unicode and in my eyes
the most problematic as it has undefined states and is variable length.
However, UTF-8 was created to allow using unicode in non-unicode
environments. For me that was always a pointless plan and the unreadable
UTF-8 characters all around buggy software that cannot handle encodings
correct (and there are many around) and ignorant users who are using
UTF-8 in environments that are not specified for multibyte charsets
(IRC) is the most annoying one.
As there are places where UTF-8 makes perfect sense and is the best
solution it is not the best solution for all ignorance users (me too ;-)
So specifying to be UTF-8 capable is somewhat inconsequent. Software has
to be capable to handle every encoding as long as they are specified for
Klaus Ethgen http://www.ethgen.ch/
pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
-----END PGP SIGNATURE-----