W3C home > Mailing lists > Public > xsl-editors@w3.org > October to December 2008

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

From: <bugzilla@wiggum.w3.org>
Date: Thu, 04 Dec 2008 14:40:25 +0000
To: xsl-editors@w3.org
Message-ID: <bug-6268-2197@http.www.w3.org/Bugs/Public/>


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

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
fo:page-number-citation with a 12-point "Glossary-" prefix surrounded by
10-point text in a footnote. Am I correct to assume that instead this
content should be "grafted" in a manner similar to the way that fo:marker
content inherits from the fo:retrieve-marker that it replaces? Or would the
fo:page-number-citation need to explicitly set the font-size to the correct

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 Thursday, 4 December 2008 14:40:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:25 UTC