- From: Chris Lilley <chris@w3.org>
- Date: Thu, 3 Nov 2005 10:24:38 +0100
- To: T Rowley <tor@cs.brown.edu>
- Cc: www-svg@w3.org
On Thursday, May 19, 2005, 12:53:53 AM, T wrote: TR> 4.1 TR> "... range for a <integer> -32,767 to 32,767" TR> s/a/an/ TR> Curious selection for the range, given that a signed 16-bit value TR> usually ranges from -32768 to 32767. We agree that this should be *an* <integer> and that the range is -32768 to 32767; we have fixed the spec. TR> Both <integer> and <number> (and dependent types) have a restricted TR> range. Does this mean that an implementation must be able to correctly TR> render all input with values within that range, even though intermediate TR> internal calculation could exceed the given ranges? No. Note that this is a restriction on content, not on implementations. Content that uses values outside this range is not conformant and will not necessarily have the values preserved accurately by all implementations. Implementations necessarily need to use higher precision internally to avoid cumulative round off error. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Thursday, 3 November 2005 09:24:40 UTC