- From: Henry S. Thompson <ht@inf.ed.ac.uk>
- Date: Mon, 23 Mar 2009 17:53:39 +0000
- To: Ian Hickson <ian@hixie.ch>
- Cc: public-html@w3.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian wrote:
> Doug wrote:
> . . .
>> * Ideally, the SVG WG would like the HTML tokenizer to be
>> case-preserving for attribute and element names.
> My understanding is that doing this would introduce an unacceptable
> performance penalty for implementations.
So, I'm perplexed.
All the browsers I'm familiar with (I haven't installed Chrome yet)
support XML+XSLT via the xml-stylesheet processing instruction.
So they all have case-preserving tokenizers whose performance is
acceptable for the people who serve and read XML+XSLT.
Who then has ruled that a case-preserving tokenizer "imposes an
unacceptable performance penalty", and on the basis of what evidence?
ht
- --
Henry S. Thompson, School of Informatics, University of Edinburgh
Half-time member of W3C Team
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFJx8yjkjnJixAXWBoRAqeWAJ9gRd7hnL5v2ghOCNOq71pu9Q8OvACfWBrU
KkG5lcxPc/i0Y6YmGJSVfbE=
=5pDG
-----END PGP SIGNATURE-----
Received on Monday, 23 March 2009 17:54:20 UTC