#98 fo/admon.xsl: replacing named template 'admon.graphic.width'

closed-fixed
XSL (122)
5
2004-10-30
2003-08-18
No

as mentioned on the list
(http://lists.oasis-open.org/archives/docbook-apps/200308/msg00107.html)

the patch is not complete as it does not include the
definition of the param $amon.graphics.width. it only
replaces the usage of the template with the parameter.

Discussion

  • Joerg Heinicke

    Joerg Heinicke - 2003-08-18

    admon.xsl patch

     
  • Robert Stayton

    Robert Stayton - 2004-08-16

    Logged In: YES
    user_id=193218

    I don't agree with this change. It is quite possible that the
    width of the graphic for each admonition type could be
    different, in which case a single parameter is not sufficient.
    The context must be taken into account.

     
  • Joerg Heinicke

    Joerg Heinicke - 2004-08-17

    Logged In: YES
    user_id=847294

    So it's a width calculation template based on the context
    node. Makes sense. Any reason why <xsl:apply-templates
    select="." mode="admon.graphic.width"/> isn't used then?

     
  • Robert Stayton

    Robert Stayton - 2004-10-30

    Logged In: YES
    user_id=193218

    I changed the admon.graphic.width from a named template to
    a mode so different admonitions could have different graphic
    widths.

     
  • Robert Stayton

    Robert Stayton - 2004-10-30
    • assigned_to: nobody --> bobstayton
    • status: open --> closed-fixed
     
  • Robert Stayton

    Robert Stayton - 2004-10-30

    Logged In: YES
    user_id=193218

    I changed the admon.graphic.width from a named template to
    a mode so different admonitions could have different graphic
    widths.

     
  • Robert Stayton

    Robert Stayton - 2004-10-30

    Logged In: YES
    user_id=193218

    I changed the admon.graphic.width from a named template to
    a mode so different admonitions could have different graphic
    widths.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks