- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 06 Jun 2009 15:18:49 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6998 --- Comment #4 from Michael Kay <mike@saxonica.com> 2009-06-06 15:18:49 --- In my implementation I gave up on the Java code for float->string a while ago and wrote my own, based on published algorithms. You seem to be correct that the rules in the spec are stricter for values in the range (1e-6, 1e6) than for values outside that range. My memory was that we had relaxed the rules at a fairly late stage of development, but it seems this was only for the values outside this range. Compare the CR spec (http://www.w3.org/TR/2005/CR-xpath-functions-20051103/#casting-to-string) with the final version. I seem to remember experimenting with a "shortest string" approach at some stage. It's not quite the same as the "nearest value" rule required for the 1e-6-to-1e6 case, or by the old CR rules. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 6 June 2009 15:18:56 UTC