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

[John Anthony Kazos Jr.]

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

The changes to the keymap files and so forth aren't quite as simple 
though. Have to convert the latin1 characters within character-constant 
expressions to \0 notation, while the comments can be left as utf8.

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

Does this mean you're doing it and I'll be ignored, or that few people 
care and I'll be ignored? I figure if I just repost my patches to LKML 
once per month, they'll eventually get merged (or at least I'll get 
comments on how people actually want them). Things are tough on a 
high-volume list. I think the git method may have the best chance of 
success. We'll see.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/