- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Mon, 21 Mar 2005 15:33:41 +0100
- To: Anne van Kesteren <fora@annevankesteren.nl>
- Cc: W3C CSS List <www-style@w3.org>
* Anne van Kesteren wrote:
>Will the next CSS 2.1 draft be using IRIs instead of URIs? Or redefining
><uri> so that IRIs are allowed? Also, the URI RFC has been updated: RFC
>3986. IRIs are defined in RFC 3987.
The section on resource identifiers should probably be rewritten, it's
quite outdated at the moment. Using IRIs might be out of scope of CSS
2.1 though. Conventional wisdom was to deal with non-ascii characters
in resource identifiers by representing the identifier in UTF-8 and
apply %xx encoding to disallowed octets (which then yields in a broken
resource identifier e.g. if the non-ascii characters are in the host
part of the identifier); RFC 3987 is incompatible with this convention
and requires that in certain cases the identifier is normalized (NFC),
so that
@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.
--
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 14:33:57 UTC