> If you only have UTF-8 files you don't need to do anything. If you > communicate with other planets (and this message indicates you do :-)
your message was sent: "Content-Type: text/plain; charset=US-ASCII" which could be considered a utf-8 sub-set. Admittedly, sendmail's hangups with the eighth bit make sending clear utf-8 documents somewhat unreliable. Email is one embarrasing case where it may take awhile for the infrastructure to catch up. (putting all text email in a base-64 mime attachment can be said to suck) Does anyone know offhand what other barriers remain to sending email as raw utf-8? Its probably less of a mess than DNS... > you will have to be able to edit ISO-8859-1 files as well. The ultimate goal is that older encodings can start to fade away, and having every app that deals with text have to deal with a plethora of encodings and codeset conversion issues will be a thing of the past. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
