[docbook-apps] Release of DocBook 5.1 + XSL?
Hi there, I know this is a cheeky request. Anyway, my organisation is using the DocBook 5.1 betas in production, and we are keen to know if there is any information regarding when the final release of the spec, and in particular the XSL distribution which fully supports it, are likely to be available. Is there a known release timeframe? We're using the assembly workflow to build documents so are hopeful that at some point oXygen will be enhanced with an assembly manager so that they're set up than at present. Assemblies work really well, but at present we're building them manually. Thanks, Graeme - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Release of DocBook 5.1 + XSL?
On 13.8.2014 15:04, gra...@heliocentrik.net wrote: I know this is a cheeky request. Anyway, my organisation is using the DocBook 5.1 betas in production, and we are keen to know if there is any information regarding when the final release of the spec, and in particular the XSL distribution which fully supports it, are likely to be available. Is there a known release timeframe? If there are no issues found in 5.1RC3 then plan is to make it OASIS Committee Specification and then OASIS Standard soon. There are some review periods required by OASIS process, but if everything goes well 5.1 could be Committee Specification during autumn. OASIS Standard is just rubber-stamping process, so no changes will be made into specification and this procedural delay shouldn't have impact on delaying implementations. XSL stylesheets are separate story. If you find some bug or missing feature in assembly support please fill it into tracker so implementation can be fixed. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Minimum TOC depth?
Has anyone figured out a way to have a *minimum* TOC depth? With HTML output, I'll sometimes see a page that has a single TOC that simply points to the first section -- in that case, it would be really nice to just skip the TOC. (On a related note, with chunk.first.sections turned off, even when there are multiple items in the TOC, the first item will often be a link to something that's already visible on the page, which is sometimes not all that useful). Thanks, Ken
Re: [docbook-apps] Minimum TOC depth?
Hi Ken, To clarify the terminology, you are describing here a minimum *length* of TOC. The depth refers to the degree of nesting of sections. There is no param that controls whether a TOC is omitted if its length is below some minumum, but I can see how it would be a good idea. For HTML output, you could customize the template named 'make.toc' in html/autotoc.xsl. Where it says: xsl:if test=$nodes you could use something like: xsl:if test=count($nodes) gt; 1 But $nodes contains only the first level entries for that TOC, not any children of those nodes (which are handled by the 'subtoc' template). So if you have a single section but it contains many subsections and your TOC depth is two or more, then this test would skip the TOC when there was more than one entry in the TOC. To be more precise, the template would have to count the entries in all levels of the TOC, which is a bit trickier. Bob Stayton Sagehill Enterprises b...@sagehill.net On 8/13/2014 9:12 AM, Ken Morse wrote: Has anyone figured out a way to have a /minimum/ TOC depth? With HTML output, I'll sometimes see a page that has a single TOC that simply points to the first section -- in that case, it would be really nice to just skip the TOC. (On a related note, with chunk.first.sections turned off, even when there are multiple items in the TOC, the first item will often be a link to something that's already visible on the page, which is sometimes not all that useful). Thanks, Ken - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
