From: Jan Engelhardt Subject: Re: [PATCH] crypto: convert crypto.h to UTF-8 Date: Thu, 3 May 2007 17:22:25 +0200 (MEST) Message-ID: References: <20070502044345.GA29384@gondor.apana.org.au> <87r6pyqg2b.fsf@pelargir.dolphinics.no> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Arne Georg Gleditsch , Herbert Xu , linux-kernel@vger.kernel.org, trivial@kernel.org, davem@davemloft.net, linux-crypto@vger.kernel.org To: "John Anthony Kazos Jr." Return-path: Received: from mailer.gwdg.de ([134.76.10.26]:45553 "EHLO mailer.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754272AbXECP2B (ORCPT ); Thu, 3 May 2007 11:28:01 -0400 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org 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 --