docbook-apps

  • 1.  Re: [docbook-apps] itemized list, and import precedence

    Posted 08-07-2011 16:51
    Hi Dave,
    This isn't a case of import precedence, but of different attributes. In general, the
    qualified attributes (like space-before.optimum) take precedence over the
    non-qualified attributes (like space-before). I wish the DocBook XSL stylesheets had
    not been written using the qualified attributes in some of the attribute-sets, because
    if you want to override the space before, you need to override all three of the
    qualified attributes for it to have any effectc.

    BTW, was that a typo in your example? Your attribute-set says space-before="5mm" but
    the resulting xsl-fo has space-before="0pt", but I don't see where the 0pt might have
    come from.

    Bob Stayton
    Sagehill Enterprises
    bobs@sagehill.net





  • 2.  Re: [docbook-apps] itemized list, and import precedence

    Posted 08-07-2011 18:03
    On 08/07/2011 05:50 PM, Bob Stayton wrote:
    > Hi Dave,
    > This isn't a case of import precedence, but of different attributes.
    > In general, the qualified attributes (like space-before.optimum) take
    > precedence over the non-qualified attributes (like space-before). I
    > wish the DocBook XSL stylesheets had not been written using the
    > qualified attributes in some of the attribute-sets, because if you
    > want to override the space before, you need to override all three of
    > the qualified attributes for it to have any effectc.
    >
    > BTW, was that a typo in your example? Your attribute-set says
    > space-before="5mm" but the resulting xsl-fo has space-before="0pt",
    > but I don't see where the 0pt might have come from.
    >
    > Bob Stayton
    > Sagehill Enterprises
    > bobs@sagehill.net

    Understood. I was drowning in attributes and couldn't see the wood for
    the trees.
    The 0pt value came from a direct customization. I have stripped them all out
    now. I simply wanted to reduce the space-before/after in a sequence of
    epigraphs.

    +1 on the qualified attributes. Unnecessary complication?

    Thanks Bob.


    >
    >
    >


  • 3.  Re: [docbook-apps] itemized list, and import precedence

    Posted 08-09-2011 10:33
    On 7.8.2011 18:50, Bob Stayton wrote:

    > This isn't a case of import precedence, but of different attributes.
    > In general, the qualified attributes (like space-before.optimum) take
    > precedence over the non-qualified attributes (like space-before). I
    > wish the DocBook XSL stylesheets had not been written using the
    > qualified attributes in some of the attribute-sets, because if you want
    > to override the space before, you need to override all three of the
    > qualified attributes for it to have any effectc.

    Is some FO processor supporting these non-qualified attributes for
    space-before/after? I don't think so. (Probably with the exception of
    xmltex which can map these directly to glues in TeX, but xmltex is not
    widely used today.) So I think we can safely remove those and just use
    value of .optimum trait as unqalified property.

    Jirka

    --
    ------------------------------------------------------------------
    Jirka Kosek e-mail: jirka@kosek.cz http://www.kosek.cz
    ------------------------------------------------------------------
    Profesionální školení a poradenství v oblasti technologií XML.
    Podrobný prehled školení http://xmlguru.cz/skoleni/
    ------------------------------------------------------------------
    http://docbook.cz Stránky o dokumentacním formátu DocBook
    http://xmlguru.cz Blog mostly about XML for English readers
    ------------------------------------------------------------------




  • 4.  Re: [docbook-apps] itemized list, and import precedence

    Posted 08-09-2011 11:23
    On 08/09/2011 11:33 AM, Jirka Kosek wrote:
    > On 7.8.2011 18:50, Bob Stayton wrote:
    >
    >> This isn't a case of import precedence, but of different attributes.
    >> In general, the qualified attributes (like space-before.optimum) take
    >> precedence over the non-qualified attributes (like space-before). I
    >> wish the DocBook XSL stylesheets had not been written using the
    >> qualified attributes in some of the attribute-sets, because if you want
    >> to override the space before, you need to override all three of the
    >> qualified attributes for it to have any effectc.
    > Is some FO processor supporting these non-qualified attributes for
    > space-before/after? I don't think so. (Probably with the exception of
    > xmltex which can map these directly to glues in TeX, but xmltex is not
    > widely used today.) So I think we can safely remove those and just use
    > value of .optimum trait as unqalified property.
    >
    > Jirka
    >

    +1





    regards

    --
    Dave Pawson
    XSLT XSL-FO FAQ.
    http://www.dpawson.co.uk




  • 5.  Re: [docbook-apps] itemized list, and import precedence

    Posted 08-09-2011 14:09
    On 09/08/11 11:33, Jirka Kosek wrote:
    > On 7.8.2011 18:50, Bob Stayton wrote:
    >
    >> This isn't a case of import precedence, but of different attributes.
    >> In general, the qualified attributes (like space-before.optimum) take
    >> precedence over the non-qualified attributes (like space-before). I
    >> wish the DocBook XSL stylesheets had not been written using the
    >> qualified attributes in some of the attribute-sets, because if you want
    >> to override the space before, you need to override all three of the
    >> qualified attributes for it to have any effectc.
    >
    > Is some FO processor supporting these non-qualified attributes for
    > space-before/after?

    Apache FOP does. That allows to have ‘justified’ pages (the bottoms of
    pages aligned, in the same way as the right edge of justified text makes
    one line). This is recommended by typography experts as something that
    makes reading easier (just like justified text).

    Removing this would be a step backwards IMHO.


    > I don't think so. (Probably with the exception of
    > xmltex which can map these directly to glues in TeX, but xmltex is not
    > widely used today.) So I think we can safely remove those and just use
    > value of .optimum trait as unqalified property.
    >
    > Jirka


    Vincent