> >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 o
> > 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
> > 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
From: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
Convert the encoding of from ISO-8859-1 to UTF-8.
Signed-off-by: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
---
Did this file individually, per request. Will re-do the whole tree later
as I'm still working on my handy-
> > Convert the subdirectory "crypto" to UTF-8. The files changed are
> > and .
> >
> > Signed-off-by: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
>
> Thanks. Could you fix up include/linux/crypto.h as well?
Sure, will do. Since I've gotten
From: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
Convert the subdirectory "crypto" to UTF-8. The files changed are
and .
Signed-off-by: John Anthony Kazos Jr. <[EMAIL PROTECTED]>
---
I can't get my mail client to send in ISO-8859-1 instead of UTF-8, so the
actual
