16971 2012-05-07 17:44:21 +0000 i18n-ISSUE-106: When the character cannot be encoded into the target encoding 2014-02-28 21:35:56 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT CLOSED NEEDSINFO P2 minor --- 1 addison ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-i18n-core public-html-bugzilla oldest_to_newest 67406 0 addison 2012-05-07 17:44:21 +0000 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. 67490 1 annevk 2012-05-08 18:43:48 +0000 That is already defined. 67564 2 ian 2012-05-10 17:49:24 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: I don't understand. Could you elaborate? 101657 3 addison 2014-02-28 21:35:56 +0000 In reviewing this text here: http://www.w3.org/html/wg/drafts/html/CR/infrastructure.html#resolving-urls ... I find that the original comment is no longer relevant.