- From: Anne van Kesteren <annevk@opera.com>
- Date: Sun, 14 Feb 2010 12:28:25 +0100
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "Erik van der Poel" <erikv@google.com>, "public-iri@w3.org" <public-iri@w3.org>
On Fri, 12 Feb 2010 21:23:07 +0100, Julian Reschke <julian.reschke@gmx.de> wrote: > I just checked CSS for the syntax, and found: > > "The format of a URI value is 'url(' followed by optional white space > followed by an optional single quote (') or double quote (") character > followed by the URI itself, followed by an optional single quote (') or > double quote (") character followed by optional white space followed by > ')'. The two quote characters must be the same." -- > <http://www.w3.org/TR/CSS2/syndata.html#value-def-uri> > > So trimming the IRI certainly does not "need" to be done in the IRI > spec; it's simply your preference. I believe newlines always need to be removed. > We discussed earlier the use of white-space separated lists of IRIs in > HTML5 (I think on IRC). Could you please elaborate why you think it's > acceptable for the spec to mandate "split on whitespace", but then it's > unacceptable to say "trim whitespace"? As far as I can tell, both fall > into the same category of preprocessing input. No. One is about parsing a string for IRIs and one is about parsing an IRI. -- Anne van Kesteren http://annevankesteren.nl/
Received on Sunday, 14 February 2010 11:29:02 UTC