- From: Anne van Kesteren <annevk@opera.com>
- Date: Mon, 25 May 2009 12:54:13 +0200
- To: "Julian Reschke" <julian.reschke@gmx.de>, Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Cc: "Dan Connolly" <connolly@w3.org>, "www-tag@w3.org" <www-tag@w3.org>, public-iri@w3.org
On Mon, 25 May 2009 12:22:22 +0200, Julian Reschke <julian.reschke@gmx.de> wrote: > Yes, but that's a requirement that is *specific* to URLs in *non-valid* > (*) HTML documents. > > I wouldn't want that encoding dependency to be present for *any* > language that uses IRIs. > > (*) as defined in HTML5 Yeah, in my testing I've found that in most contexts URLs are used they do use the processing rules as defined in HTML5 (e.g. in CSS and XMLHttpRequest), but have the "URL character encoding" flag always set to UTF-8. -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 25 May 2009 10:55:10 UTC