16972 2012-05-07 17:45:48 +0000 i18n-ISSUE-107: replacement characters 2014-03-03 16:44:22 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified PC Windows NT CLOSED INVALID P2 normal --- 1 addison dave.null ian ishida mike public-html-admin public-html-wg-issue-tracking public-i18n-core robin public-html-bugzilla oldest_to_newest 67407 0 addison 2012-05-07 17:45:48 +0000 2.6.3 Resolving URLs http://www.w3.org/TR/html5/urls.html#resolving-urls Step 8.1 replaces characters that cannot be encoded into the target encoding with the question mark character (0x3F). Should this be, instead, the replacement character for the target encoding? For example, UTF-8 would use U+FFFD. Some encodings use _. 67575 1 ian 2012-05-10 17:58:18 +0000 Please provide test cases demonstrating the proposed behaviour is compatible with legacy implementations. 70193 2 contributor 2012-07-18 07:07:56 +0000 This bug was cloned to create bug 17861 as part of operation convergence. 73332 3 robin 2012-09-06 16:39:40 +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: Additional Information Needed Rationale: Addison, can you please provide further information as per Ian's comment #1? 101658 4 addison 2014-02-28 21:44:10 +0000 The text in this section has changed and I can't find the "offending bits" any longer. Actually, I believe this has been taken over by the Encodings document and the issue is being discussed in a bug there. Since there isn't anything in HTML to change, closing the bug. Regarding Ian's comment, the replacement character for UTF-8 is well known to be U+FFFD and all of the browsers use that code point when presented with malformed UTF-8 data. Other encodings do work as described in my original comment. However, I will stipulate that URL conversion may be handled specially. Since this is no longer a bug, I haven't produced a test case to test it with. 101757 5 ishida 2014-03-03 16:40:25 +0000 You can find this in the Encoding spec at http://encoding.spec.whatwg.org/#encodings. hth 101758 6 addison 2014-03-03 16:44:22 +0000 Yes, I know it's there :-). Although that's not really the spec for URL processing.