http://blog.gmane.org/gmane.org.w3c.xsl-editors hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.org.w3c.xsl-editors/1122 <pre>https://www.w3.org/Bugs/Public/show_bug.cgi?id=21456 Bug ID: 21456 Summary: Flash crash ssl Classification: Unclassified Product: XSLFO Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: P2 Component: XSL-FO Requirements Assignee: xsl-editors&lt; at &gt;w3.org Reporter: Kathysoto411a&lt; at &gt;gmail.com QA Contact: xsl-editors&lt; at &gt;w3.org </pre> bugzilla< at >jessica.w3.org 2013-04-01T03:50:42 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1121 <pre>&amp;nbsp;&amp;nbsp;&amp;nbsp; Hi!&amp;nbsp;&amp;nbsp;&amp;nbsp; http://hondaclubpanama.com/wmb/qwxnhsmovnsal95ehnlz5nto0nkjc1i9nzghychg2x7ws/awudahqknot7yjrswd9597rfp7qfsd3az4whk82h8d3w5a0&amp;5do88yiokl93ip4&amp;nbsp;&amp;nbsp; srinivasarao vegunta</pre> srinivasarao vegunta 2013-02-12T12:06:08 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1116 <pre>In XSL-FO 1.1, 5.10.4, appears: "If this function is used in an expression on a formatting object, F, that is a descendant of an fo:page-sequence, then the computed value is taken from the region specification that was used to generate the nearest ancestor region reference area which has as its descendants the areas returned by F." However, this is followed by an example where "this function" (from-page-master-region) is used on fo:page-sequence, and not a descendant of fo:page-sequence! &lt;fo:page-sequence master-name="default-sequence" writing-mode="from-page-master-region()"&gt; How is this example to be reconciled with the normative language cited above about being "used in an expression ... that is a descendant of an fo:page-sequence"? Regards, Glenn </pre> Glenn Adams 2012-04-21T16:12:48 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1115 <pre>Hi, It whould be very helpful to use a text-overflow as in http://www.w3.org/TR/css3-ui/#text-overflow0 why: the overflow="hidden" is not very useful for a print media in case of text, because it may cut a letter. Doing this outside of the FO namespace is also a bad solution because it requires font size/style calculation. see also my http://stackoverflow.com/questions/9807926/add-suspensive-dots-at-end-of-a-text-in-case-of-overflow-hidden question. other ideas? Adrian </pre> Adrian Stadelmann 2012-03-22T15:31:59 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1112 <pre>Hello, I've known you website for ages! And I found interesting your publication "Transformations XSL (XSLT)" which I googled on http://xmlfr.org/w3c/TR/xslt/ ! I'd love to use it in a project I'm involved with called "Geek Science", so I'm seeking your permission for translation to Macedonian language. "Geek Science" is a freemium-model non-English language orientated startup with collection of scientific articles, personal notes etc. in several languages that is collaboratively edited by volunteers from around the world since 1999. Young and old, students and professors - even your neighbor could be a volunteer member. If you agree, we will credit you for your work in the resulting translation's references by stating that it was based on your work and is used with your permission, and by mentioning the name of my project "Geek Science" back to: http://xmlfr.org/w3c/TR/xslt/ Thank you for your time and patience. I look forward to your response next week. --- Best wishes, John Obri Tirana, Albania (GMT +1) Translation for Education FAQ - http://goo.gl/q9Oq9 </pre> John Obri 2012-03-15T14:48:11 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1109 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=13828 Summary: ICC reference may be out of date Product: XSLFO Version: 2.0 Working Draft Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: XSL-FO AssignedTo: tgraham&lt; at &gt;mentea.net ReportedBy: tgraham&lt; at &gt;mentea.net QAContact: xsl-editors&lt; at &gt;w3.org SVG Color 1.2 uses: [ICC42] International Color Consortium. Specification ICC.1:2004-10 (Profile version 4.2.0.0) Image technology colour management — Architecture, profile format, and data structure. Available at http://www.color.org/ICC1V42.pdf </pre> bugzilla< at >jessica.w3.org 2011-08-18T14:47:25 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1108 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=13827 Summary: Do cie-lab-color() and cie-lchab-color() need optional white point? Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: tgraham&lt; at &gt;mentea.net ReportedBy: tgraham&lt; at &gt;mentea.net QAContact: xsl-editors&lt; at &gt;w3.org XSL FO 2.0's cie-lab-color() and cie-lchab-color() [1] are meant to be compatible with what can be expressed in SVG Color 1.2 [2]. The cielab() and cielchab() functions in SVG Color 1.2 both have an option white point parameter. Should XSL FO 2.0 have this parameter in its functions? Regards, Tony Graham. [1] http://www.w3.org/Style/XSL/Group/2009/03/xslfo20.html#d2e7142 [2] http://dev.w3.org/SVG/modules/color/master/SVGColor.html </pre> bugzilla< at >jessica.w3.org 2011-08-18T14:33:18 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1107 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=13804 Summary: Is normative rgb-icc() prototype wrong? Product: XSLFO Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: tgraham&lt; at &gt;mentea.net ReportedBy: tgraham&lt; at &gt;mentea.net QAContact: xsl-editors&lt; at &gt;w3.org The rgb-icc() prototype [1] in the normative HTML for XSL 1.1 is: color rgb-icc(numeric, numeric, numeric, NCName, numeric, numeric) However, the non-normative XML source [2] for XSL 1.1 contains: &lt;proto name="rgb-icc" return-type="color"&gt;&lt;arg type="numeric"/&gt;&lt;arg type="numeric"/&gt; &lt;arg type="numeric"/&gt;&lt;arg type="NCName"/&gt;&lt;arg type="numeric"/&gt;&lt;arg type="numeric" occur="rep"/&gt;&lt;/proto&gt; I.e., the 'occur="rep"' on the last &lt;arg&gt; does not make it any different from an &lt;arg&gt; without it. In contrast 'occur="opt"' adds a "?" after the argument in the rendered prototype. E.g., in 'system-font()'. Was 'occur="rep"' supposed to add a "+" after the argument name in the rendered prototype? Regards, Tony Graham tgraham&lt; at &gt;mentea.net Consultant http://www.mentea.net Mentea 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- XML, XSL FO and XSLT consulting, training and programming [1] http://www.w3.org/TR/xsl11/#expr-color-functions [2] http://www.w3.org/TR/2006/REC-xsl11-20061205/xslspec.xml </pre> bugzilla< at >jessica.w3.org 2011-08-17T11:05:12 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1099 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=13406 Summary: "caption-side" should be "Extended" conformance level Product: XSLFO Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: XSL-FO AssignedTo: tgraham&lt; at &gt;mentea.net ReportedBy: tgraham&lt; at &gt;mentea.net QAContact: xsl-editors&lt; at &gt;w3.org The "caption-side" property [1] is listed in section B.3 [2], Property Table: Part II, as having "Complete" conformance level. It should be "Extended" conformance level. "caption-side" applies only to fo:table-and-caption [3], where it "specifies the position of the caption box with respect to the table box." The "caption box" is the optional fo:table-caption [4] child of fo:table-and-caption. fo:table-and-caption has "Basic" conformance level [5], and fo:table-caption has "Extended" conformance level [5], but there's little point implementing fo:table-caption without implementing "caption-side", since that is a major part of the correct implementation of fo:table-caption. Furthermore, "Extended" conformance [6] is defined as "includes everything else, except for shorthands", and "Complete" conformance is defined as "includes everything". "caption-side" is not a shorthand, so it better fits the definition of "Extended" conformance rather than "Complete". Actually, defining fo:table-and-caption as "Basic" and fo:table-caption" as "Extended" is odd in itself, since there's very little point in using a fo:table-and-caption that doesn't have a fo:table-caption. It would be better to also make fo:table-caption have "Basic" conformance and move the fallback currently defined for fo:table-caption to be the fallback for "caption-side". Regards, Tony Graham. [1] http://www.w3.org/TR/xsl11/#caption-side [2] http://www.w3.org/TR/xsl11/#prtab2 [3] http://www.w3.org/TR/xsl11/#fo_table-and-caption [4] http://www.w3.org/TR/xsl11/#fo_table-caption [5] http://www.w3.org/TR/xsl11/#d0e36675 [6] http://www.w3.org/TR/xsl11/#conform </pre> bugzilla< at >jessica.w3.org 2011-07-28T12:26:50 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1092 <pre>Hi there, see the subject line -- is there a media type for XSL-FO documents? (I did check the XSL 1.1 spec, plus the IANA registry, but couldn't find anything...) Best regards, Julian </pre> Julian Reschke 2011-05-13T12:03:09 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1090 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=12369 Summary: Reference-orientation and writing-mode on page-master and regions Product: XSLFO Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: vhennebert&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org There seems to be ambiguities in the way the reference-orientation and writing-mode properties should be handled on side regions. fo:simple-page-master is used to generate a page-viewport-area/ page-reference-area pair. The reference-orientation of the page-viewport-area is set to 0. In the description of Section 6.4.13, “fo:simple-page-master”, there is the following: • a note saying “For example, if the writing-mode of the fo:simple-page-master is ‘lr-tb’, then these regions correspond to the body of a document, the header, the footer, the left sidebar, and the right sidebar.” • this sentence: “The ‘writing-mode’ of the page is used to determine the placement of the five regions on the master.” That seems to indicate that the value of the “writing-mode” property set on the fo:simple-page-master is used to determine the placement of the regions. • but further below there is this: “The reference-orientation of the page-reference-area and writing-mode of the page-viewport-area are determined by the formatting object that generates the area (see 6.4.5 fo:page-sequence).” In Section 6.4.15, “fo:region-before”, there is this: “This region specifies a viewport/reference pair that is located on the ‘before’ side of the page-reference-area.” So, if the fo:simple-page-master has a “reference-orientation” of 0 and the fo:page-sequence a “reference-orientation” of 90, what prevails? The existence of the from-page-master-region() function leaves to think that the third point above should prevail. If that function is used, then the reference-orientation and writing-mode properties set on fo:simple-page-master would be used, otherwise this is the value of those properties as specified on the fo:page-sequence element that would count. However, in Section 5.10.4 no mention is being made of the fo:simple-page-master element. Only the regions are mentioned. If we assume that the from-page-master-region() function actually also applies to fo:simple-page-master, and given the following XSL-FO document: &lt;?xml version="1.0" standalone="no"?&gt; &lt;fo:root xmlns:fo="http://www.w3.org/1999/xsl/format"&gt; &lt;fo:layout-master-set&gt; &lt;fo:simple-page-master master-name="page" page-width="21cm" page-height="29.7cm" reference-orientation="90"&gt; &lt;fo:region-body margin-top="15pt" reference-orientation="90"/&gt; &lt;fo:region-before extent="10pt"/&gt; &lt;/fo:simple-page-master&gt; &lt;/fo:layout-master-set&gt; &lt;fo:page-sequence master-reference="page" reference-orientation="from-page-master-region()"&gt; &lt;fo:static-content flow-name="xsl-region-before" font-size="8pt"&gt; &lt;fo:block&gt;xsl-region-before&lt;/fo:block&gt; &lt;/fo:static-content&gt; &lt;fo:flow flow-name="xsl-region-body"&gt; &lt;fo:block&gt;lorem ipsum dolor sit amet, consectetur adipiscing elit. vestibulum arcu felis, gravida vitae laoreet in, molestie nec libero. mauris non enim diam. pellentesque nisl diam, aliquet nec euismod vitae, convallis nec massa. mauris gravida arcu ac erat euismod molestie. maecenas eget neque in sem aliquam viverra. vivamus dictum lobortis scelerisque.&lt;/fo:block&gt; &lt;/fo:flow&gt; &lt;/fo:page-sequence&gt; &lt;/fo:root&gt; Because the from-page-master-region() function is used, the “reference-orientation” property specified on the fo:simple-page-master and the regions would be used to determine their orientations. So the content-rectangle of the page-reference-area would be like this: ___________________________ | end | | | | | | | | | | | |before |after | | | | | | | | | | | | |_________________________| start While the content-rectangle of the region-viewport-area for the region-before is supposed to be like this: after ____ | | | | | | | | | | end| |start | | | | | | | | | | |__| before which seems to be inconsistent with the description of fo:region-before: “The before-edge of the content-rectangle of this region-viewport-area is positioned coincident with the before-edge of the content-rectangle of the page-reference-area generated using the parent fo:simple-page-master. The block-progression-dimension of the region-viewport-area is determined by the extent trait on the fo:region-before formatting object.” The inconsistency could be resolved by replacing content-rectangle with border-rectangle in the excerpt above. Because, as explained in Section 4.2.3, “Geometric Definitions”, the definition of the before/after/start/end-edges of the content-rectangle of an area uses the inline/block-progression-direction of that area; Whereas the border/padding/allocation-rectangles use the directions of the parent area. Thanks, Vincent </pre> bugzilla< at >jessica.w3.org 2011-03-23T12:32:44 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1089 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11823 Summary: syntax error? 7.31.1 Product: XSLFO Version: 1.1 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org 7.31.1 "background" CSS2 Definition: Value: [&lt;background-color&gt; || &lt;background-image&gt; || &lt;background-repeat&gt; || &lt;background-attachment&gt; || &lt;background-position&gt; ]] | inherit I'm assuming a syntax error. Mismatched [] pairs. </pre> bugzilla< at >jessica.w3.org 2011-01-20T12:57:53 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1086 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11672 Summary: Block-progression-dimension of fo:inline and fo:basic-link does not take children into account Product: XSLFO Version: 1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: vhennebert&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org The children of an fo:inline or fo:basic-link element do not seem to be taken into account when computing the block-progression-dimension of the element's content rectangle and this may lead to counter-intuitive results for the user. Given the following FO snippet: &lt;fo:block font-family="Helvetica" font-size="12pt"&gt;Lorem ipsum dolor &lt;fo:inline id="outer" border="1pt solid red"&gt;&lt;fo:inline id="inner" font-size="30pt"&gt;sit&lt;/fo:inline&gt;&lt;/fo:inline&gt; amet&lt;/fo:block&gt; Assuming that we are in the default lr-tb writing mode, we are interested in computing the height of the red border rectangle. Section 4.6, “Inline-areas”, states that “An inline-area with inline-area children has a content-rectangle which extends from its dominant baseline by its text-depth in the block-progression-direction, and in the opposite direction by its text-altitude”. In the case of the outer inline-area, text-altitude and text-depth are taken from the font metrics. Assuming we are using the standard Helvetica font available as one of the 14 PDF core fonts, this amounts to 11.1pt. So the border-rectangle is 11.1pt high. The inner inline-area has a font-size of 30pt, which makes its content-rectangle 27.75pt high, which largely overflows the border-rectangle of the outer inline-area. Now, if we replace the outer inline element with an fo:basic-link element, the active (‘clickable’) area generated by the FO processor will also be 11.1pt high, so will not cover the whole inner inline-area, and to my knowledge there is no way to achieve this. The practical use case is an image surrounded by a basic-link to make it clickable. Only the bottom of the image will actually be active. Should that really be the expected behaviour, or is that an oversight? </pre> bugzilla< at >jessica.w3.org 2011-01-05T17:18:40 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1085 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11664 Summary: 5.6.1 "word-spacing-critical-length" Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "This property specifies a length (x) for the word spacing to allow before invoking letterspacing. More precisely, it specifies a limitation on the effect of a "letterspacing" value; letterspacing may be used in the line-breaking algorithm within a given line-area when otherwise the word-spacing value would be greater than x." Critical is used, not max or min? No indication of which side of the value causes a transition from word to letter spacing? A length is used, yet the description talks of a limitation (on what?). The requirement says "Allow users to specify the priority between word and letter spacing." I'm guessing that when word spacing exceeds this value, letter-spacing is used? 1. Does it meet the requirement (no mention of which of the two has priority). 2. I don't find the property name at all intuitive wrt purpose. 3. The description is unclear IMHO. </pre> bugzilla< at >jessica.w3.org 2011-01-04T10:47:08 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1084 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11662 Summary: 5.5.1 "tab-stops" Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "Value: list of pairs of { left | right | center | decimal } and &lt;length&gt;" No mention of how pairs are separated? Or how each item in the pair is separated? </pre> bugzilla< at >jessica.w3.org 2011-01-04T09:51:13 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1083 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11661 Summary: 5.4 "hanging-punctuation" Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "This property describes which characters are allowed to hang outside the margins." I question the validity of this statement. perhaps 'outside the body of text' or 'into the margin? See http://is.gd/k4wsT </pre> bugzilla< at >jessica.w3.org 2011-01-04T09:48:07 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1082 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11660 Summary: 5.2.1 "last-line-minimum-deficit" Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "The last-line-minimum-deficit property specifies a length (x) for the minimum line length deficit for the last line-area of a block-area. More precisely, it specifies a constraint on the last line-area child of the last block-area L generated and returned by the formatting object, such that the inline L is either equal to the available width (w) in the inline-dimension (as the term is used in the "justify" value of "text-align"), or is less than or equal to w minus x." Above contains 'block-area L' and 'inline L' which is confusing. I find the use of the word 'deficit' unclear in this context, after the description in 5.2. Seems to lack clarity in what is deficient wrt what? within a certain range. " which I find clear, perhaps justify-when-greater-than might be clearer, since the description intimates that justification will only take place when the actual length is greater than some value? </pre> bugzilla< at >jessica.w3.org 2011-01-04T09:29:41 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1081 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11659 Summary: 2.11 Examples Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org It appears that no use is made of fo:number in the example? Isn't that the purpose of the example? If it is used, no mention is made of how? Confusing to the reader? </pre> bugzilla< at >jessica.w3.org 2011-01-04T09:19:43 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1079 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11653 Summary: 2.8.28 Arbitrary Object Numbering Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: trivial Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "The definition of attribute "number-pref-id" is as following:" yet the examples refer to 'number-ref-id'. I believe the latter to be correct. </pre> bugzilla< at >jessica.w3.org 2011-01-03T10:21:59 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1077 <pre>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&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;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. </pre> bugzilla< at >jessica.w3.org 2011-01-03T10:13:57 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1076 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11651 Summary: 2.8.1 fo:number Product: XSLFO Version: 2.0 Working Draft Platform: PC OS/Version: Linux Status: NEW Severity: trivial Priority: P2 Component: XSL-FO AssignedTo: Tony.Graham&lt; at &gt;MenteithConsulting.com ReportedBy: dave.pawson&lt; at &gt;gmail.com QAContact: xsl-editors&lt; at &gt;w3.org "fo:number creates a number sequence to be processed by the XSL-FO processor and generate a list of sequences in varies of area in the XSL-FO area tree." Suggest simplifying, possibly "fo:number requires the XSL-FO processor to generate a number for use in the output" Otherwise I find the statement unclear. </pre> bugzilla< at >jessica.w3.org 2011-01-03T10:07:00 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.org.w3c.xsl-editors