W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

[Bug 19961] Write security considerations

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Nov 2014 14:27:41 +0000
To: www-international@w3.org
Message-ID: <bug-19961-4285-JYU6Pq5tmK@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19961

--- Comment #4 from Anne <annevk@annevk.nl> ---
Here is the last bit starting at the <hr> above as it was cut off due to using
a non-BMP code point (replaced with U+... reference):

===
Encoders used by URLs found in HTML and HTML's form feature can also result in
slight information loss when an encoding is used that cannot represent all
scalar values. E.g. when a resource uses the <span>windows-1252</span> encoding
a server will not be able to distinguish between an end user entering U+1F4A9
and “&amp;#128169;” into a form.

<hr>

The problems outlined here go away when exclusively using utf-8, which is one
of the many reasons that is now the mandatory encoding for all things.
===

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 November 2014 14:27:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC