ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble

3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble

State:

CLOSED

Product:

mobileOK Basic tests

Raised by:

Sean Owen

Opened on:

2007-01-18

Description:

3.3 CHARACTER_ENCODING_SUPPORT
(http://www.w3.org/TR/mobileOK-basic10-tests/#test_character_encoding_support)
has an outstanding issue whose resolution is stuck at the moment pending
feedback from the XHTML WG. This issue restates the problem and proposes an
alternative solution. The issue goes like this:

We require that mobileOK resources specify and use UTF-8 encoding. The
Content-Type header can specify encoding via the \"...;charset=UTF-8\" syntax.
However as Jo said, we recognize that in practice it\'s sometimes hard to control
the server\'s behavior in this respect. This is problematic because content
served as \"text/html\", according to some sources, implies
\"text/html;charset=ISO-8859-1\". Other sources say there is really no meaningful
default, and, this is among the questions we have for the XHTML WG.

Separately, we say that *if* and XML preamble is present, and it specifies an
encoding, it must be UTF-8. An XML preamble is, apparently, not strictly
required and may not be present.

Here is an alternative resolution:
1. Assume that \"text/html\" does not meaningfully imply any encoding, as more
recent W3C docs indicate
2. Require an XML preamble specifying UTF-8 encoding to help aid agents in
correctly understanding the encoding

Related Actions Items:

No related actions

Related emails:

1. [minutes] Cambridge 2007 F2F meeting (from dom@w3.org on 2007-01-24)
2. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from andrea@trasatti.it on 2007-01-22)
3. RE: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from k.scheppe@t-online.net on 2007-01-22)
4. RE: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from luca.passani@openwave.com on 2007-01-20)
5. RE: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from luca.passani@openwave.com on 2007-01-19)
6. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from srowen@google.com on 2007-01-19)
7. RE: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from luca.passani@openwave.com on 2007-01-19)
8. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from srowen@google.com on 2007-01-19)
9. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from ron.mandel@openwave.com on 2007-01-19)
10. RE: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from luca.passani@openwave.com on 2007-01-19)
11. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from srowen@google.com on 2007-01-19)
12. Re: ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from srowen@google.com on 2007-01-19)
13. ISSUE-180: 3.3 CHARACTER_ENCODING_SUPPORT, again: Character encoding, text/html, XML preamble (from dean+cgi@w3.org on 2007-01-18)

Related notes:

No additional notes.

Display change log