bugzilla | 4 Dec 15:19 2008
Picon

[Bug 6267] New: [XSLFO] Tables, space-start and border-separation


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6267

           Summary: [XSLFO] Tables, space-start and border-separation
           Product: XSLFO
           Version: 1.1
          Platform: PC
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2008JanMar/0003
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

The XSL-FO 1.1 Recommendation gives some details about how the 
border-separation property for tables should be handled, but it is not 
clear in my opinion where the half of it associated to the table should 
lie.

As a picture is still the simplest way to illustrate the problem, please 
have a look at the following example and the attached picture (see below 
for the formulas):
    <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
      <fo:layout-master-set>
        <fo:simple-page-master master-name="page"
          page-height="10cm" page-width="15cm" margin="1cm">
(Continue reading)

bugzilla | 4 Dec 15:20 2008
Picon

[Bug 6267] [XSLFO] Tables, space-start and border-separation


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6267

--- Comment #1 from Tony Graham <Tony.Graham <at> MenteithConsulting.com>  2008-12-04 14:20:13 ---
Created an attachment (id=608)
 --> (http://www.w3.org/Bugs/Public/attachment.cgi?id=608)
Background separation alternatives.

--

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

bugzilla | 4 Dec 15:20 2008
Picon

[Bug 6267] [XSLFO] Tables, space-start and border-separation


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6267

--- Comment #2 from Tony Graham <Tony.Graham <at> MenteithConsulting.com>  2008-12-04 14:20:49 ---
Created an attachment (id=609)
 --> (http://www.w3.org/Bugs/Public/attachment.cgi?id=609)
Table grid boundary line.

--

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

bugzilla | 4 Dec 15:40 2008
Picon

[Bug 6268] New: [XSLFO] fo:folio-prefix (and other) content


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6268

           Summary: [XSLFO] fo:folio-prefix (and other) content
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2007JulSep/0007
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

This question applies at least to fo:folio-prefix, fo:folio-suffix, but also
seems to apply to fo:index-page-number-prefix, fo:index-page-number-suffix,
fo:index-page-citation-list-separator, and
fo:index-page-citation-range-separator.

Each of these objects has the following content model:
    (#PCDATA | %inline;)*.

The question: From whom do the child objects inherit properties? The use of
the term "static" for some of these seems to imply that they inherit
normally, that is, by reference to their ancestors in the tree. However,
that seems unlikely. It is easy, for example, to imagine an
(Continue reading)

bugzilla | 4 Dec 15:48 2008
Picon

[Bug 6269] New: [XSLFO] ipd/bpd percentage base


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6269

           Summary: [XSLFO] ipd/bpd percentage base
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2007AprJun/0004
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

I am seeking clarification of the XSL-FO 1.1 Recommendation at Sections
7.15.3 (block-progression-dimension) and 7.15.7
(inline-progression-dimension), for the <percentage> calculation. In both
cases, the percentage base is described as "the corresponding dimension of
the closest area ancestor that was generated by a block-level formatting
object."[1] This definition does not address formatting objects that may be
direct descendants of the fo:flow, such as fo:block-container and fo:table,
that can specify ipd and bpd.

My intuition wants to restate the definition as follows: "the corresponding
dimension of the closest area ancestor that is either a reference area or an
area that was generated by a block-level formatting object." Can you either
(Continue reading)

bugzilla | 4 Dec 15:50 2008
Picon

[Bug 6270] New: [XSLFO] fo:page-sequence properties


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6270

           Summary: [XSLFO] fo:page-sequence properties
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2007JulSep/0008
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

There is a minor editorial glitch in the documentation for fo:page-sequence.
The object definition references the properties "country" and "language".
However, Appendix B-4 (in the PDF version at least) does not list
"fo:page-sequence" as applying to these properties. I believe that the
object definition is correct, as these properties are part of the
"conversion properties" listed at 6.6.10, which must be available from the
"reference-page-sequence" addressed there.

--

-- 
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.
(Continue reading)

bugzilla | 4 Dec 15:53 2008
Picon

[Bug 6271] New: [XSLFO] lengths and percentages


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6271

           Summary: [XSLFO] lengths and percentages
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2007AprJun/0006
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

I see that the definition of <length-range> has changed from 1.0 to 1.1 to
explicitly differentiate between the <length> datatype and the <percentage>
datatype. This makes intuitive sense, and the clarification is welcome.
However, there is still at least one place in the 1.1 Recommendation that
confuses or even contradicts this distinction, at Section 5.11, at the first
"Note" item (designated by a hand with a pointing finger in the PDF
version), which says: "Since a <percentage> value, that is not interpreted
as "auto", is a valid <length> value it may be used in a short form."

It is difficult to tell whether this is intended to be a general statement
for all cases, or one that applies only to the "space-before" example in the
context. However, neither seems to be appropriate. The "space-before"
(Continue reading)

bugzilla | 4 Dec 15:59 2008
Picon

[Bug 6274] New: [XSLFO] Reference to "Alphabetic" in 7.17.2 letter-spacing


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6274

           Summary: [XSLFO] Reference to "Alphabetic" in 7.17.2 letter-
                    spacing
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2006JanMar/0028.html
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

I've just stumbled over something in the spec. 7.17.2 letter-spacing (in
XSL 1.1 CR, similar in XSL 1.0) mentions that letter-spacing is applied
in halves before and after every character that is classified as
"Alphabetic" in the Unicode database. This does not include characters
like "-" (002D) or "/" (002F). Assume an fo:block which allows for
letter-spacing that contains the text "XSL-FO". Between "S" and "L", you
get two half letter-spaces (together 1 letter-space). Between "L" and "-",
you get only one half letter-space if you strictly follow the spec. This
is not quite what I would expect and not what various layouters
currently do (Apache FOP, two commercial FO implementations I checked,
OpenOffice 2.0 and Word 2003).
(Continue reading)

bugzilla | 4 Dec 16:53 2008
Picon

[Bug 6276] New: Breaks and Borders, Successive Break Contexts


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6276

           Summary: Breaks and Borders, Successive Break Contexts
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2008AprJun/0003
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

>From xsl-editors:

The following situations are not explicitly described by the XSL-FO 1.1
Recommendation and no consistent behaviour could be found among the
various implementations:

Given the following FO snippet:
    <fo:block border-before-color="black"
      border-before-style="double"
      border-before-width="1pt">
      <fo:block break-before="page">
         Some text.
(Continue reading)

bugzilla | 4 Dec 17:45 2008
Picon

[Bug 6280] New: Explicit breaks on table-header and -footer


http://www.w3.org/Bugs/Public/show_bug.cgi?id=6280

           Summary: Explicit breaks on table-header and -footer
           Product: XSLFO
           Version: 1.1
          Platform: All
               URL: http://lists.w3.org/Archives/Public/xsl-
                    editors/2007AprJun/0000
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSL-FO
        AssignedTo: alb.w3c <at> gmail.com
        ReportedBy: Tony.Graham <at> MenteithConsulting.com
         QAContact: xsl-editors <at> w3.org

>From xsl-editors <at> w3.org:

I don't think it makes much sense to set the break-before and
break-after properties on fo:table-row and children of fo:table-cell
which are themselves children of fo:table-header and fo:table-footer
elements. It might be helpful to explicitely state that in the
descriptions of break-before and break-after.

--

-- 
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.
(Continue reading)


Gmane