Stephen Warren <[EMAIL PROTECTED]> writes: > At present, my patch ensures that it only parses None/UTF-8 > encoded data, because I don't know if/how it would work on other > types... Are there other types that are likely?
Goodness, yes. Actually, very few mail clients grok UTF-8 at this point. Instead, they use what many call RFC 2047 "gobbledygook" to support a whole slew of encodings. > I'm in need of a good overview of I18N/UTF-8/unicode/etc.! The current situation is more complex that you'd ever imagine. Unicode is the eventual answer, but that's still a ways away. Here are some links that helped me when I was learning about I18N in e-mail: * Introduction to i18n - http://www.debian.org/doc/manuals/intro-i18n/ * The ``International templates'' section I wrote for the template HOWTO - http://tmda.net/howto-template.html * Internationalized headers - http://mimelib.sourceforge.net/docs/module-email.Header.html * ISO 8859 Alphabet Soup - http://czyborra.com/charsets/iso8859.html _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
