[Bug 11652] New: 2.8 Numbering

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 11652] New: 2.8 Numbering

Bugzilla from bugzilla@jessica.w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11652

           Summary: 2.8 Numbering
           Product: XSLFO
           Version: 2.0 Working Draft
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P2
         Component: XSL-FO
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]
         QAContact: [hidden email]


2.8.2 states "There’s no imperative state for an fo:number, i.e. it’s not a
counter or an variable. "
Yet 2.8.4 states "The "reset-level" determines the level that the fo:number’s
internal state in FO processor needs to be reset to its reset-value."

There appears to be some conflict here?
suggest either define 'imperative state' or remove the statement from 2.8.2
since clearly an initial value and 'state' is required.

--
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.
Reply | Threaded
Open this post in threaded view
|

[Bug 11652] 2.8 Numbering

Bugzilla from bugzilla@jessica.w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11652

--- Comment #1 from Dave Pawson <[hidden email]> 2011-01-03 10:16:23 UTC ---
I can find no requirement that an fo:number be an integer, yet it appears
implicit.

--
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.