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]
Date:	03 May 2007 15:52:30 +0200
From:	Arne Georg Gleditsch <argggh@...phinics.no>
To:	"John Anthony Kazos Jr." <jakj@...-k-j.com>
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

"John Anthony Kazos Jr." <jakj@...-k-j.com> writes:
> 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.

Yes, I agree that heuristics can be used to determine the coding
system used with a high degree of probability.  I'm just suggesting we
make the coding system explicit, in order to spare other applications
that do visual presentation of Linux source code having to perform
their own heuristics.

But hey, if I'm the only one wanting to see this particular bike shed
painted blue...

-- 
								Arne.

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ