| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1168182838.14763.24.camel@shinybook.infradead.org> Date: Sun, 07 Jan 2007 23:13:57 +0800 From: David Woodhouse <dwmw2@...radead.org> To: Tilman Schmidt <tilman@...p.cc> Cc: Russell King <rmk+lkml@....linux.org.uk>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: OT: character encodings (was: Linux 2.6.20-rc4) On Sun, 2007-01-07 at 14:06 +0100, Tilman Schmidt wrote: > Russell King schrieb: > > Welcome to the mess which the UTF-8 charset creates. Utter bollocks. > The problem of different character encodings coexisting on the same > platform, and the resulting occasional messing-up, far predates Unicode. > I distinctly remember one case of being bitten by this myself in 1977 > when Unicode wasn't even on the horizon yet, and I don't think that was > the first time. Indeed. If you take arbitrary content and send it out to the world labelled as ISO8859-1, of _course_ you're likely to be corrupting it. Far from being the cause of the problem, UTF-8 actually offers the chance of a _solution_. Because once the Luddites catch up, it'll largely eliminate the need for using the multitude of legacy character sets and converting between them -- and the problem of mislabelling will fairly much go away. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists