W3C home > Mailing lists > Public > public-html@w3.org > May 2012

[Bug 16971] New: i18n-ISSUE-106: When the character cannot be encoded into the target encoding

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 May 2012 17:44:25 +0000
To: public-html@w3.org
Message-ID: <bug-16971-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16971

           Summary: i18n-ISSUE-106: When the character cannot be encoded
                    into the target encoding
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: minor
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: addison@lab126.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


2.6.3 Resolving URLs
http://www.w3.org/TR/html5/urls.html#resolving-urls

Deals with processing URLs. The steps here result in defining the "character
encoding" of the URL, which is applied to the query portion of the URL. I put
character encoding in quotes, because it is really the character encoding of
the document or script containing the URL as a string. Step 8.2 contains an
implicit encoding conversion (to the document character encoding). A health
warning should be supplied about what to do when the character cannot be
encoded into the target encoding.

-- 
Configure bugmail: https://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 Tuesday, 8 May 2012 18:11:46 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:52 UTC