Masataka Ohta comments on my comment:
which use chars: =3DC4 =3DD6 (and =3DC5) (TeX: \"A \"O \AA )
Sigh, the line becomes a lot more meaningless.
This line is meaningless to me.
Dear me, didn't these MIME headers have any effect ?
No, I'm not using MIME, because we, Japanese, don't need it for
daily communication.
MIME-Version: 1.0
Content-Type: text/plain; charset=3DISO-8859-1
Content-Transfer-Encoding: 8BIT
When Mr. Ohta (and many others behind non-ESMTP/8BITMIME mailers)
receive this, they get the headers as:
(This time mr. Ohta gets that QUOTED-PRINTABLE
encoded line with even larger bunch of equals + two hex chars,
as the equals-char gets quoted -- it being a special case..)
Sure. So, please don't rely on "charset=3DISO-8859-1", if you want to
communicate people living outside of small part of Europe.
Like Keith has commented earlier, "Just-send-8-bit without labeling
the character set is foolish"
To me, its foolish to try to have a standard to deny what is already
being used widely without any difficulty.
Within enclaves, yes. I can even read relcom newsgroups
(not that I can UNDERSTAND them, but I can get the russian characters
to my screen,) when I MANUALLY pick proper font for my xterm.
THAT is the place where I want some smart-smart news-parser + multifont
displayer to pick the information from within the message, preferrably
MIME-headers, and then do the displaying.
And how can you post or read mixed 8859/1 KOI article?
Your interpretation is very good. That is, MIME should have nothing t=
o
do with encoding issues.
There we agree. I want to use MIME as a way to LABEL what
charsets and encodings are being used so that the smar
parser can use whatever means it has to drive the display.
No, you should use MIME to label encoding.
But then, aren't we talking about the labeling in here ?
Labelling embedded in text as escape sequences.
... nevertheless, the MIME is spreading!
Not here.
Masataka Ohta