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/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 </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-f</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 </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, t</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 th</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 </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 </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 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1075 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11650 Summary: 2.7.3 Widow and Orphan Management. typo 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 "it can be kept with a block or moved to the start of the next synchronized spam," s/spam/span/ </pre> bugzilla< at >jessica.w3.org 2011-01-03T10:00:27 http://comments.gmane.org/gmane.org.w3c.xsl-editors/1074 <pre>http://www.w3.org/Bugs/Public/show_bug.cgi?id=11649 Summary: 2.7.2 Common Dependencies Properties for Formatting Objects 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 "Example 4: dependency-content-start and -end properties" Contrast with the example which uses 'dependency-content-begin' Which is correct? </pre> bugzilla< at >jessica.w3.org 2011-01-03T09:34:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.org.w3c.xsl-editors