This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11652 - 2.8 Numbering
Summary: 2.8 Numbering
Status: NEW
Alias: None
Product: XSLFO
Classification: Unclassified
Component: XSL-FO (show other bugs)
Version: 2.0 Working Draft
Hardware: PC Linux
: P2 minor
Target Milestone: ---
Assignee: Tony Graham
QA Contact: Mailing list for comments on XSL (XSl-FO)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-03 10:13 UTC by Dave Pawson
Modified: 2011-01-03 10:16 UTC (History)
0 users

See Also:

Attachments

Description Dave Pawson 2011-01-03 10:13:57 UTC 
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.
Comment 1 Dave Pawson 2011-01-03 10:16:23 UTC 
I can find no requirement that an fo:number be an integer, yet it appears implicit.