Cart
[Home] [By Thread] [By Date] [Recent Entries]
Chris Lilley wrote: > MIME actually need not have those constraints; *email* has those > constraints (although increasingly it does not, in practice). HTTP is > always 8-bit clean. I agree that the MIME RFCs have steadfastly tried to > pretend that MIME is an email-only thing. The requirement for a charset with text/* documents (whether minimized or not) has nothing to do with email, although the fact that a minimized charset parameter means "US-ASCII" surely does. A charset must be specified for interoperable text (as opposed to application-specific formats) because text means nothing if you do not know the charset, and no text-using application can fail to either decode, guess, or simply presume some charset. -- John Cowan http://www.ccil.org/~cowan cowan@c... You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5) xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
