On 5/8/06, Toru Marumoto <[EMAIL PROTECTED]> wrote:
What if it was Content-Type: text/plain;charset=utf-7 or Content-Type: text/plain;charset=utf-8 or Content-Type: text/plain;charset=utf-16 or Content-Type: text/plain;charset=shift-jis or Content-Type: text/plain;charset=euc-jp or Content-Type: text/plain;charset=iso-2022-jp and list goes on ... I think same thing happens in other countries like China, Tiwan etc.
<?xml version="1.0" encoding="euc-jp"?> is also a valid XML and nothing is differnt from charsets (encodings) specified in Content-Type header.
How many charset encoding do I have to support?
I don't understand why you can parse euc-jp feed in XML, but cannot if it's HTTP response body. -- Tatsuhiko Miyagawa
