gjikkl wrote:
I stand correct on the percentage-encoding not being Unicode.
Well IMO this shouldn't even be a problem, is kinda of common this
percentage-encoding and all browsers should recognize it and make the
proper translation.
Did you bother reading the RFC 3986 at
<ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt> which David Ross
provided (particularly sections 2.2 and 2.4) and his explanation. If
you had you would have seen that your opinion doesn't really matter
because the RFC explicitly states that "URIs that differ in the
replacement of a reserved character with its corresponding
percent-encoded octet are not equivalent." and therefore; no standards
compliant browser should translate the uri you provided as you suggest.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
