[whatwg] Editorial for application/x-www-form-urlencoded encoding algorithm
Kristof Zelechovski
giecrilj at stegny.2a.pl
Tue Feb 17 14:47:42 PST 2009
Regarding 4.10
<http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html>
Forms - HTML 5:
Is:
1. For each character in the entry's name and value that cannot be
expressed using the selected character encoding, replace the character by a
string consisting of a U+0026 AMPERSAND character (&), one of more
characters in the range U+0030 DIGIT ZERO (0) to U+0039 DIGIT NINE (9)
representing the Unicode codepoint of the character in base ten, and finally
a U+003B SEMICOLON character (;).
Should be:
1. For each character in the entry's name and value that cannot be
expressed using the selected character encoding, replace the character by a
string consisting of a U+0026 AMPERSAND character (&), U+0023 NUMBER SIGN
character (#), one of more characters in the range U+0030 DIGIT ZERO (0) to
U+0039 DIGIT NINE (9) representing the Unicode codepoint of the character in
base ten, and finally a U+003B SEMICOLON character (;).
Reasons:
1. Internet Explorer sends &#XXXX;
2. The present encoding offers no instant roundtrip.
Besides, it would be easier to say that unsupported characters are converted
to NCRs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090217/89efec47/attachment-0001.htm>
More information about the whatwg
mailing list