On May 3 2007 11:35, John Anthony Kazos Jr. wrote: > >> >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? Nah. I did a walkthrough once, and my discoveries were that iso-8859-{2 .. 14} was a real minority if not nonexistant, leaving you with almost obvious choices to guess what a file's encoding is. If a name looks good, it must be UTF8 already. Else try ISO-8859-1. If it still looks odd -- perhaps because it's a weirdo character like "1/2" or it "does not sound right", try cp437. etc. > 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. > Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
