Re: iso-2022-jp

Hitoshi --

Your mail came through with a content-type header of:

Content-type: text/plain; charset=iso-2022-jp

Yet in fact it contained only ASCII.  I don't know what software you're using, but if it isn't yours please point out to the author that RFC 1341 specifies that in such cases (when your text can legitimately be called either ASCII or a superset) it should be labelled as ASCII to promote interoperability.

To give you an idea of why this is important:  I read your mail with a mail reader that displays ASCII and a few other character sets in its main window.  When it gets iso-2022-jp, it starts a kterm window in which to display it.  This is only mildly annoying when I get to see real Japanese characters (it makes the wait worthwhile!) but in the case of your message, all that popped up was ASCII, which was kind of annoying.

I'm glad to see you using the features, I just thought whoever wrote the software should know about this minor error.  -- Nathaniel

PS -- This is unrelated to the use of iso-2022-jp in your From field, to give your correct name.  That, by the way, looked fine for me in a kterm window -- I reproduce them here as an image for the benefit of list readers who have MIME support for image/gif but not for Kanji data in the headers: