Hello,
I don't know about SHOULD but I think that it is reasonable to expect the XML processor to respect the character encoding that is reported in the XML instance (in this case, due to UTF-16, both BOM and the encoding declaration in the prolog).
Having said that with XML over HTTP I found that in many cases the accepted encoding, the encoding reported in an HTTP header and the actual encoding of the XML payload have any connection/correlation among them (though, you'd expect them to agree...). I see servers work in iso_8859-1 when they expect to get UTF-8 Hebrew text and serve clients that report in their request header iso_8859-8 and with no prolog on the XML payload (which yields UTF-8)... I can only guess how many patches on patches (bugs over bugs) have been applied to this configuration in order to work. Now imagine a situation where you need to introduce a new component (e.g., a new XML processor) into the system...
Shlomo.
-----Original Message-----
From: bryan rasmussen [mailto:rasmussen.bryan@gmail.com]
Sent: Wed 2/27/2008 1:17 PM
To: xml-dev
Subject: [xml-dev] Accept-Charset and XML declaration?
Hi,
I was just wondering, what SHOULD happen if I have an XML file server
side that has encoding UTF-16 with a declaration of that, and my
accept-charset header sent by my client is iso-8859-1?
Cheers,
Bryan Rasmussen
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php