- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 03 Jun 2009 18:47:05 +0200
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: "public-iri@w3.org" <public-iri@w3.org>
* Anne van Kesteren wrote: >I think that would be a bug in the definition of the relevant character >encoding. For each encoding it should be unambiguous how it maps to >Unicode and how Unicode maps to the encoding, IMO. Many character encodings are not injective, i.e., they permit multiple binary representations of the same character sequence, UTF-7 is a well known example; the original definition of UTF-8 is another (and it was made injective in later versions). I note that Internet Explorer won't use many problematic character encodings when constructing the query string for 'http' and 'https' resource identifiers (for other schemes this encoding sensitive treatment of the query string is fictional). -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Wednesday, 3 June 2009 16:47:44 UTC