[Bug 6858] New: More details needed for "ASCII-compatible encoding"


           Summary: More details needed for "ASCII-compatible encoding"
           Product: HTML WG
           Version: unspecified
          Platform: All
               URL: http://www.w3.org/TR/html5/infrastructure.html#character
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML 5: The Markup Language
        AssignedTo: mike@w3.org
        ReportedBy: duerst@it.aoyama.ac.jp
         QAContact: public-html-bugzilla@w3.org
                CC: public-html@w3.org

The draft currently says:
"An ASCII-compatible character encoding is one that is a superset of US-ASCII
(specifically, ANSI_X3.4-1968) for bytes in the set 0x09, 0x0A, 0x0C, 0x0D,
0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F, 0x41 - 0x5A, and 0x61 - 0x7A."
What exactly is meant? Is Shift_JIS Ascii-compatible (it encodes the US-ASCII
characters at the same bytes as US-ASCII, but also uses these bytes as the
second bytes in a multibyte character encoding).
refers to ASCII-compatible, and in that context, I would want to have Shift_JIS
be ASCII-compatible, but from the above definition, I'd lean to the conclusion
that Shift_JIS may not be ASCII-compatible.
Please clarify whether ASCII-compatible means that the above bytes are only
used for US-ASCII character, or whether it means that for US-ASCII characters,
only the above bytes are used.
If you use ASCII-compatible in several places in your spec, you might have to
check and maybe split the definition into two, to take into account different

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Friday, 1 May 2009 08:48:33 UTC