It is my understanding that iTunes ignores character encoding
information given in the charset parameter of the HTTP Content-Type
header. Example:
http://feedparser.org/tests/wellformed/itunes/http_charset_overrides_doc.xml
You can capture HTTP headers from the command line with curl:
$ curl -Dheaders
http://feedparser.org/tests/wellformed/itunes/http_charset_overrides_doc.xml
$ cat headers
HTTP/1.1 200 OK
Date: Wed, 27 Jul 2005 13:34:54 GMT
Server: Apache/1.3.33 (Debian GNU/Linux)
Vary: *
Last-Modified: Tue, 05 Jul 2005 00:37:01 GMT
ETag: "ec0c8-8b8-42c9d62d"
Accept-Ranges: bytes
Content-Length: 2232
Content-Type: application/xml; charset=windows-1252
It is this last parameter in this last header that interests me. If
present, it overrides the encoding given in the encoding attribute in
first line of the body of the feed. Reference: section 3.2 of RFC
3023 http://www.ietf.org/rfc/rfc3023.txt
Does Apple plan to fully support the HTTP Content-Type header
(including the optional charset parameter) in a future version of
iTunes?
--
Cheers,
-Mark
_______________________________________________
Do not post admin requests to the list. They will be ignored.
syndication-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/syndication-dev/email@hidden
This email sent to email@hidden
