linux-kernel - Re: [PATCH] crypto: convert crypto.h to UTF-8

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.0.98.0705030915240.21257@sigma.j-a-k-j.com>
Date:	Thu, 3 May 2007 09:21:11 -0400 (EDT)
From:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
To:	Arne Georg Gleditsch <argggh@...phinics.no>
cc:	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

> > Did this file individually, per request. Will re-do the whole tree later 
> > as I'm still working on my handy-dandy testing and patching tools and 
> > don't have a lot of time outside of work until the summer gets underway.
> 
> While this is probably inevitable, it would be nice if there was some
> way to determine the actual coding system used for individual files.
> Especially if we're mixing latin1 and utf8 in the same tree.  Has
> something like adding "/* -*- coding: utf-8; -*- */" or similar to the
> top of converted files been considered?

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 
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...

Besides, based on the actual binary representation of UTF-8, it's 
extremely unlikely for any ISO-8859-1 string to be detected as UTF-8. VIm 
already does this: UTF-8 it handles natively, but open up one of these 
unpatched files in VIm and you'll see "[converted]" at the bottom of your 
screen. Should happen if you open the attached .patch.bin file in VIm.
-
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/