- From: <bugzilla@jessica.w3.org>
- Date: Mon, 03 Jan 2011 10:13:57 +0000
- To: xsl-editors@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: Tony.Graham@MenteithConsulting.com
ReportedBy: dave.pawson@gmail.com
QAContact: xsl-editors@w3.org
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.
Received on Monday, 3 January 2011 10:13:59 UTC