[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Charset in newgroup sample
Julien ÉLIE <julien@xxxxxxxxxxxxxxx> writes:
> In the sample of newgroup control message:
> Control: newgroup example.admin.info moderated
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="nxtprt"
> Content-Transfer-Encoding: 8bit
> This is a MIME control message.
> Content-Type: application/news-groupinfo
> For your newsgroups file:
> example.admin.info About the example.* groups (Moderated)
> Content-Type: text/plain
> A moderated newsgroup for announcements about new newsgroups in
> the example.* hierarchy.
> wouldn't it be better to put the charsets in order to highlight the
> fact they are useful (though it is said the default is US-ASCII)?
Yeah, probably a good idea. I'll make that change.
> Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
As near as I can tell from RFC 2046, charset is not a valid parameter for
multipart/* content types. It's only supposed to go on the final
constituent parts. Among other things, this avoids...
> In our case, the most important is the second one. Incidentally,
> I wonder what happens when the first one is defined to utf-8 and
> the second one is undefined. Is it utf-8 (out of transitivity)
> or us-ascii?
...that problem. :)
Russ Allbery (rra@xxxxxxxxxxxx) <http://www.eyrie.org/~eagle/>