||*()*|| Hi, Philip. >> > There is simplesect used which messes the ToC. >> > According to Norman Walsh comment on simplesect it aren't supposed >> > to be in ToC. Was it the main idea when writing en/install/pecl.xml? >> > Should I alter XML or processing templates? >> >> It is probably better to be conformant to DocBook guidelines, so fix the >> XML please. If it breaks translations (ie. you need to modify the >> container, but not only the XML file itself), then it is more work (it >> would be nice to fix it across translations). If it does not break the >> build, then there is no immediate need to fix the translated files.
PO> How does it mess with the ToC? It looks fine to me. I like PO> simplesect in how it puts all sections on one page with a PO> ToC on said page. I hate how the PHP manual always breaks PO> the sections on separate pages, sometimes one paragraph per PO> page. Maybe you have a solution to remedy this as I simply PO> chose simplesect because it was already parsed exactly how I PO> wanted. security.magicquotes uses simplesect for this same PO> reason. If you are speaking about DSSSL templates when it can be right, but in XSL you can try to build xCHM to see how magic quotes section is displayed in ToC on the main page. I can offer nested <sect1> <sect2> element, where <sect2> isn't breaked into chunks and it's titles will appear in ToC. Do you want that titles to be hidden from ToC to be available only inside of <sect1> content? t --
