Rune Saetre wrote:
Hi again.
This is snipped from the RFC:
The "charset" parameter is used with some media types to define the character set (section 3.4) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or its subsets MUST be labeled with an appropriate charset value. See section 3.4.1 for compatibility problems.
The sender might be either the client or the server. The document following the headers MUST be encoded using the ISO-8859-1 charset if nothing else is explicitly stated in the Content-Type header. This means that the recipient MUST interpret the document according to the ISO-8859-1 charset if the sender has not explicitly stated that another charset is used in the Content-Type header.
correct.
Wether this the charset is guessed while parsing the headers, or if one implicitly assumes ISO-8859-1 everywhere else in the code if no charset is specified in the Content-Type header, does not matter.
It is clear from section 3.4.1 that no indicated charset DOES NOT mean that the indicated preference from the recipient has been heeded, but that the document actually is encoded using the ISO-8859-1 charset.
ok, got the point. Thanks for outlining this again.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 DÃsseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
