W3C home > Mailing lists > Public > www-math@w3.org > August 2016

Re: [MathML4] Whitespace and attributes canonicalization in MathML VS HTML5/CSS

From: Hammond, William F <whammond@albany.edu>
Date: Tue, 2 Aug 2016 14:03:14 +0000
To: Frédéric Wang <fwang@igalia.com>
CC: "www-math@w3.org" <www-math@w3.org>
Message-ID: <96F18CCF-CBEC-4466-A75D-8186C36AF77A@albany.edu>
My intention was to defend the Gecko behavior and to say that 'E' notation should not be used with human-scale lengths

Sent from my iPhone

> On Aug 2, 2016, at 9:30 AM, Frédéric Wang <fwang@igalia.com> wrote:
> 
>> Le 01/08/2016 à 23:33, William F Hammond a écrit :
>> 
>> 1E1 is ridiculous.  For one thing, to my eye, it's 10.0
>> (floating point) -- implied by the E notation -- rather than
>> simply 10
>> 
>>                                    -- Bill
> Not sure I understand your point either. As David said, lengths use
> floating point numbers. Gecko's MathML code implement its own parsing to
> verify that the number matches the MathML syntax before converting to
> float while WebKit's parsing code is simpler and just calls an internal
> toFloat method immediately (letting it decide what's the valid syntax).
> If MathML aligns on HTML5 and the typical syntax for floats then Gecko's
> code could be simplified a bit. Maybe that will also help converters
> that generate lengths from via some calculations, I don't know.
> 
> 
Received on Wednesday, 3 August 2016 09:27:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 3 August 2016 09:27:35 UTC