- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Fri, 10 Jun 2005 07:44:07 +0100 (BST)
- To: www-svg@w3.org
> The SVG WG coordinated with the DOM WG long ago about attribute value > normalization which might result in getAttributeNS() returning a different > string than was set via setAttributeNS(). It was decided that SVG To me normalisation would mean changes to thy syntactic sugar, or mathematical manipulations that don't change the meaning of the formula in the specification in which it is defined. Display is defined by CSS, so normalisation of Display ought to be reversible to a string that would have the same effect in any CSS application. d is defined by SVG, so SVG knows what transformations are safe in that case. If one wants to save space and be fast, one should probably store your one bit of the SVG specific semantics and a Huffman code for the full value. One might treat the SVG function bit as part of the code, and therefore only need two bits if people use your preferred values.
Received on Friday, 10 June 2005 07:14:54 UTC