W3C home > Mailing lists > Public > www-svg@w3.org > February 2014

[Bug 24769] New: SVG Path BNF is ambigious

From: <bugzilla@jessica.w3.org>
Date: Fri, 21 Feb 2014 19:40:00 +0000
To: www-svg@w3.org
Message-ID: <bug-24769-2017@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24769

            Bug ID: 24769
           Summary: SVG Path BNF is ambigious
           Product: SVG
           Version: SVG 2.0
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Paths
          Assignee: schepers@w3.org
          Reporter: jcgregorio@google.com
        QA Contact: www-svg@w3.org

http://www.w3.org/TR/SVG2/single-page.html#paths-PathDataBNF

There is no description in the text on how this BNF is to be used. For example,
are the rules for the BNF alternatives to be parsed as 'first match wins'?

If so, then the following rules won't produce good results, as the may match
part of a floating point number as an integer before matching the
floating-point-constant rule:

nonnegative-number:
    integer-constant
    | floating-point-constant
number:
    sign? integer-constant
    | sign? floating-point-constant

If the BNF is intended to be 'first match wins' then these rules should be
written as:

nonnegative-number:
    floating-point-constant
    | integer-constant
number:
    sign? floating-point-constant
    | sign? integer-constant

This is also true of SVG 1.1 and 1.2 Tiny.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 21 February 2014 19:40:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:35 UTC