From: Leonid Yegoshin (egoshin@genesyslab.com)
Date: Thu Nov 20 1997 - 13:51:37 CST
Hi,
>From: chl@clw.cs.man.ac.uk (Charles Lindsey)
>
>Not so, because MIME-encoded Newsgroup: headers (RFC2047-style) are not
>permitted by the proposal, so UTF-8 is all you have got. If your
>
!??? Where is this proposal ? I read http://www.landfield.com/usefor/
and found 2 drafts and read boths. I don't see this in it.
I don't look this in this mailing list from IETF announce date.
That we discuss as IETF WG ?
>For other headings (which may have been gatewayed from email) the MIME
>form (RFC2047) is permitted, but deprecated. UTF-8 is the default
>otherwise. Even then, news software MUST NOT translate it (until it
>arrives at the newsreader for display, that is).
>
I don't agree with it. With this requerement news process software
MUST have UTF-8 understanding, and additional headache. SMTP/MIME allow _any_
coding in any headers. And news-processing software should convert
MIME-encoding Newsgroup: to UTF-8 ... Why ?
But I don't see any arguments for UTF-8-only encoding, yet...
>If there is no Content-Type header at all, then the body SHOULD be in
>US-ASCII. But actually, the proposed default is UTF-8, since it does no
>harm to be that way.
You are in error here. Long before MIME there was and there is software
which can send/recieve 8-bit mails/news without MIME-headers,
for exam in Russia. Defaulting 8-bit body as UTF-8 is error, look at RFC1428.
The reason for creating this RFC is not occasional.
The defaulting to UTF-8 should break "8-bit clean" (see RFC2130,
Appendix A-1, "NetNews Messages").
- Leonid Yegoshin, LY22