[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: multiple encoding specs (Re: IE5.0 does not conform to RFC2376)
Chris Lilley scripsit: > > There is no way to fail to specify a charset in > > text/* documents, and rightly so, because text without a charset > > is uninterpretable. > > This is disingeneous; both clauses are true, but the second one implies > that there is no other method of conveying the information, which, > clearly, there is. If you know the text is XML, then you can determine the charset by Appendix F methods; but if "text/xml" is just "text/*" to you, then you must be able to rely on the (possibly minimized) charset parameter in the media type, because if there is no charset, the text/* is, as I said, uninterpretable. > So > a) There is no way to fail to specify a charset in text/* documents > > But it does not have to be explicit. It can be implied. good way of > formalising that implication would be to refer to the rules in the XML > 1.0 Recommendation. I meant that if you are processing a MIME document, as long as you know its major type is "text", you can always determine the charset. There is either an explicit charset parameter, or the implicit charset of either "US-ASCII" or "ISO-8859-1" depending on the underlying transport protocol. -- John Cowan cowan@c... e'osai ko sarji la lojban. 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...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|