W3C home > Mailing lists > Public > www-style@w3.org > March 2005

Re: [css2.1] IRIs

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 21 Mar 2005 16:13:55 +0100
To: Anne van Kesteren <fora@annevankesteren.nl>
Cc: W3C CSS List <www-style@w3.org>
Message-ID: <426ee221.1087502109@smtp.bjoern.hoehrmann.de>

* Anne van Kesteren wrote:
>Bjoern Hoehrmann wrote:
>>   @charset "iso-8859-1";
>>   element { background-image: url(Bjo\000308rn) }
>> 
>> would yield in a request for Bj%C3%B6rn rather than Bjo%CC%88rn. Many
>> implementations do the former so adopting a requirement for IRI support
>> might hinder us to exit CR.
>
>Actually, most implementations, including Firefox and at least recent 
>versions of Opera, have options to set URI handling to UTF-8, which 
>would result in the correct URI being loaded.

Again, RFC 3987 would require that

  @charset "iso-8859-1";
  element { background-image: url(Bjo\000308rn) }

yields in a request for Bj%C3%B6rn and that

  @charset "utf-8";
  element { background-image: url(Bjo\000308rn) }

yields in a request for Bjo%CC%88rn.

Both are "UTF-8" but differ in their Unicode Normalization. Some CSS
implementations do the latter but few if any implementations do the
former which is not surprising as that would be inconsistent with a
number of specifications.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 21 March 2005 15:14:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:36 GMT