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
| ||
|
Date: Thu, 3 May 2007 17:22:25 +0200 (MEST) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: "John Anthony Kazos Jr." <jakj@...-k-j.com> cc: Arne Georg Gleditsch <argggh@...phinics.no>, Herbert Xu <herbert@...dor.apana.org.au>, linux-kernel@...r.kernel.org, trivial@...nel.org, davem@...emloft.net, linux-crypto@...r.kernel.org Subject: Re: [PATCH] crypto: convert crypto.h to UTF-8 On May 3 2007 09:21, John Anthony Kazos Jr. wrote: > >There's no reason for any non-UTF-8 to be in the tree at all, so >eventually it won't be a problem. I'm (slowly but surely) working on >converting everything in the tree. GCC handles UTF-8 just fine, and all In fact, GCC gives a crap about comments :) and otherwise sees things as octets, not characters. I think GCJ is the only one that really pays attention to encoding. >non-stupid/non-broken distributions of GNU/Linux and other major Un*ces >should be based on (or at least compatible with) UTF-8 in basic >operations. Files like the keymaps will be more work to convert, but they >can be as well. > >I'm operating on the assumption that anything in the tree that isn't UTF-8 >is ISO-8859-1. Of course, I'm also checking it by hand to make sure a >small-O-with-umlaut doesn't become the Klingon logo... This is probably all you'll ever see: http://lkml.org/lkml/2007/1/8/222 Jan -- - 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