ISSUE-168: 3.2 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE
3.2 CHARACTER_ENCODING_SUPPORT and CHARACTER_ENCODING_USE
- State:
- CLOSED
- Product:
- mobileOK Basic tests
- Raised by:
- Jo Rabin
- Opened on:
- 2006-11-09
- Description:
- For each resource linked via a link or style element, request the resource:
If the character encoding is not specified in HTTP response Content-Type header
or the response specifies an Internet media type starting with \"text/\" and the
character encoding is not \"UTF-8\", WARN
I think this needs to be clarified:
a) you can\'t link a resource via a style element as such - you need to follow
the @import rules within a style element or a stylesheet linked via a link element.
b) we need to think about which link elements we are actually interested in - in
this context - we\'re certainly interested in Stylesheet, and I think we are
almost certainly not interested in Alternate or Bookmark (as otherwise we would
WARN on links for RSS feeds, and links to Alternate versions intended for other
devices). We\'re probably interested in Start, Next, Prev etc. (does anyone
actually use these?)
c) The character encoding thing seems to be wrong too - if the content type is
a/x+x then we seem to be saying that if the UTF-8 character encoding is missing
then we WARN. As Dom has patiently explained, you don\'t have to say UTF-8 for
XML documents - it\'s the default. Even more so as Dom has hinted there may be a
new orthodoxy saying you SHOULD not include the character encoding in this
circumstance.
- Related Actions Items:
- No related actions
- Related emails:
- [minutes] Thu 20 Nov BPWG Telecon (from jo@linguafranca.org on 2006-11-30)
- ISSUE-169: 3.3 CONTENT_FORMAT_SUPPORT (from dean+cgi@w3.org on 2006-11-09)
- ISSUE-171: 3.5 EXTERNAL_RESOURCES (from dean+cgi@w3.org on 2006-11-09)
Related notes:
No additional notes.
Display change log
