From: SourceForge.net <no...@so...> - 2006-08-24 06:31:08
|
Feature Requests item #1254533, was opened at 2005-08-09 07:01 Message generated for change (Comment added) made by xmldoc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=1254533&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: XSL Group: output: all formats Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: qandaentry/blockinfo/title should be used in TOC Initial Comment: when the qandaentry/question is large or complex, it does not make sense to place it into the generated TOC. I suggest using qandaentry/blockinfo/title for TOC instead of qandaentry/question when it is non-void. ---------------------------------------------------------------------- >Comment By: Michael(tm) Smith (xmldoc) Date: 2006-08-24 15:31 Message: Logged In: YES user_id=118135 DocBook 5 doesn't support putting titles in info children of qandaentry, so if you mark up your docs with qandaentry/ blockinfo/title, they will not be forwards-compatible. I don't think QandAentry is reallky intended to allow a title. I think the only reason it's allowed in DocBook 4 is that there was no db.titleforbidden.info in DocBook 4, as there is in DocBook 5. So there was no way to constrain blockinfo to exclude title when blockinfo occurs as a child of qandaentry. It seems to me like a better solution for you might be to make your questions less large and complex -- break them into smaller questions or move some parts of the questions, restated, into your answers. Sorry, I know that this is probably not what you wanted to hear, but I don't see a good way to add support for this in the stylesheets. It seems like something that would require a new element, or require an optional title child to be added to qandaentry. If that's what you want, then you need to file a DocBook RFE for it and see what the TC thinks. ---------------------------------------------------------------------- Comment By: Michael(tm) Smith (xmldoc) Date: 2006-08-24 15:23 Message: Logged In: YES user_id=118135 DocBook 5 doesn't support putting titles in info children of qandaentry, so if you mark up your docs with qandaentry/ blockinfo/title, they will not be forwards-compatible. I don't think QandAentry is reallky intended to allow a title. I think the only reason it's allowed in DocBook 4 is that there was no db.titleforbidden.info in DocBook 4, as there is in DocBook 5. So there was no way to constrain blockinfo to exclude title when blockinfo occurs as a child of qandaentry. It seems to me like a better solution for you might be to make your questions less large and complex -- break them into smaller questions or move some parts of the questions, restated, into your answers. Sorry, I know that this is probably not what you wanted to hear, but I don't see a good way to add support for this in the stylesheets. It seems like something that would require a new element, or require an optional title child to be added to qandaentry. If that's what you want, then you need to file a DocBook RFE for it and see what the TC thinks. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-01-18 01:08 Message: Logged In: YES user_id=5735 more specifically: the question/para may contain elements (like screen) not suitable for TOC. E.g.: <qandaentry id="faq-random"> <blockinfo><title>Is &random; broken?</title></blockinfo> <question id="faq-random-q"><para>Why does <screen>&sh-prompt; clisp &opt-x; '(&random; 1s0)'</screen> always print the same number?</para></question> <answer><para>Reproducibility is important. See <xref linkend="random-state"/>.</para></answer></qandaentry> ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2005-09-30 00:43 Message: Logged In: YES user_id=5735 see http://www.podval.org/~sds/clisp/impnotes/faq.html A.4.1. A.4.6. A.4.7. for examples ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373750&aid=1254533&group_id=21935 |