Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#366 html: refentryinfo vs bookinfo processing inconsistency

output: HTML
open
nobody
XSL (399)
5
2014-08-17
2006-10-17
Sam Steingold
No

I have the same text in bookinfo and in refentryinfo:
&clisp-authors; &clisp-doc-copyright;
bookinfo text ends up on the front page,
refentryinfo text is discarded.
i would prefer that the refentryinfo data is not
discarded but put in a section "project info" (or
similar) instead.

http://clisp.cvs.sourceforge.net/\*checkout*/clisp/clisp/doc/

see also
https://sourceforge.net/tracker/index.php?func=detail&aid=1524581&group_id=21935&atid=373747

Discussion

    • labels: 322745 --> 321159
     
    • summary: refentryinfo vs bookinfo processing inconsistency --> html: refentryinfo vs bookinfo processing inconsistency
     
  • Logged In: YES
    user_id=582041
    Originator: NO

    Is this really a bug? The refentryinfo element is a container for metadata about a refentry. It is not intended for "project info". If you want refentryinfo content to be rendered, then modify the titlepage setup.

     
  • Logged In: YES
    user_id=582041
    Originator: NO

    Set to pending status: this is arguably not a bug, and there was no response to the 2007-04-04 comment.

     
    • status: open --> pending-wont-fix
     
  • Sam Steingold
    Sam Steingold
    2007-06-05

    • status: pending-wont-fix --> open-wont-fix
     
  • Sam Steingold
    Sam Steingold
    2007-06-05

    Logged In: YES
    user_id=5735
    Originator: YES

    I think that bookinfo and refentryinfo should be processed similarly by default.
    your suggestion that I "modify the titlepage setup" is ineteresting,
    but I would prefer my modification to be as simple as setting a parameter,
    e.g., set render.refentryinfo to 1.
    please note that the xsl is sufficiently complicated for the 3 line code snippet you have in mind to be extremely hard for me to come up with, so I would appreciate an example.
    thanks.

     
  • Logged In: YES
    user_id=582041
    Originator: NO

    Again, I'm questioning if this is a bug. Feel free to turn it into a feature request, but note that refentryinfo allows many child elements. What if you, for example, wanted to render only some of them, and suppress others? Having a simple on/off parameter wouldn't help. That is why there is a special titlepage customization mechanism (explained in detail at http://www.sagehill.net/docbookxsl/HTMLTitlePage.html\). If you need more help, the docbook-apps list is the place to ask.

     
  • Sam Steingold
    Sam Steingold
    2007-06-06

    Logged In: YES
    user_id=5735
    Originator: YES

    the page you point me to (thanks!) does not mention refentryinfo.

     
  • Logged In: YES
    user_id=582041
    Originator: NO

    Please do not post any more followups here. This is a bug tracking system, not a support forum. I kindly advise you to:
    1. take some time to learn the principles of titlepage customization.
    2. direct additional questions to docbook-apps.

     
    • status: open-wont-fix --> closed-wont-fix
     
  • Logged In: YES
    user_id=118135
    Originator: NO

    As Mauritz points out, this is not a bug. So moving it to feature-request tracker (to preserve the history at least).

     
    • milestone: 447634 --> output: HTML
    • labels: 321159 --> XSL
    • status: closed-wont-fix --> open