No, I was testing a fairly small document - much smaller and with way fewer heading than the example you have given. Perhaps it is too small? ;-)
On Fri, Feb 14, 2014 at 1:57 PM, Peter Desjardins < [email protected]> wrote: > The JavaScript that creates the expanding/contracting table of > contents in the navigation pane might be taking a little longer to > render if you have a very large number of headings. > > Are you publishing source documents that have a long list of headings? > For example, this document has a lot of headings but its navigation > pane remains visible after page loads for me (in Chrome): > > > http://docs.oracle.com/cd/E41069_01/Platform.11-0/ATGPlatformProgGuide/html/index.html > > Do you have more headings than that one? > > Peter > > On Thu, Feb 13, 2014 at 7:00 PM, natk <[email protected]> wrote: > > Although we have noticed one slightly odd behaviour, which is that if you > > click on a hyperlink in the right hand side panel, the navigation panel > > disappears momentarily. Has anyone else noticed this? (This is on the > Chrome > > browser). > > > > > > On Fri, Feb 14, 2014 at 9:38 AM, natk <[email protected]> wrote: > >> > >> I generated webhelp output format and that does exactly what I want. > Thank > >> you! > >> > >> > >> On Thu, Feb 13, 2014 at 9:37 AM, natk <[email protected]> wrote: > >>> > >>> Thanks for that. I'll have a look at it, and yes I do have a > >>> customisation layer. I'll also look into the web help format. > >>> > >>> > >>> > >>> > >>> On Thu, Feb 13, 2014 at 3:02 AM, Peter Desjardins > >>> <[email protected]> wrote: > >>>> > >>>> [switching to docbook-apps list] > >>>> > >>>> That use case sounds reasonable, although in my opinion making > >>>> headings links to themselves sounds a little confusing to users. I > >>>> typically use the webhelp output format instead of direct HTML so my > >>>> output displays the TOC on every page. It's easy for me to copy the > >>>> URL for any page from that TOC. > >>>> > >>>> To do what you are describing, I would start by taking a look at the > >>>> section.heading template in the html/sections.xsl file. Here's a > >>>> snippet from that template: > >>>> > >>>> <xsl:element name="h{$hlevel}"> > >>>> <xsl:attribute name="class"><xsl:value-of > >>>> select="$class"/></xsl:attribute> > >>>> <xsl:if test="$css.decoration != '0'"> > >>>> <xsl:if test="$hlevel<3"> > >>>> <xsl:attribute name="style">clear: both</xsl:attribute> > >>>> </xsl:if> > >>>> </xsl:if> > >>>> <xsl:if test="$allow-anchors != 0"> > >>>> <xsl:call-template name="anchor"> > >>>> <xsl:with-param name="node" select="$section"/> > >>>> <xsl:with-param name="conditional" select="0"/> > >>>> </xsl:call-template> > >>>> </xsl:if> > >>>> <xsl:copy-of select="$title"/> > >>>> </xsl:element> > >>>> > >>>> The line <xsl:copy-of select="$title"/> enters the text of the > >>>> heading. You could experiment with adding an <xsl:element > >>>> name="a"><xsl:attribute name="href"> enclosure around that xsl:copy > >>>> element. > >>>> > >>>> You'd have to get the ID of the parent section in order to complete > >>>> the href attribute. That should be available from the $section > >>>> parameter of the template. But the way you get the ID depends on how > >>>> your source DocBook is formed. > >>>> > >>>> Also, this would not affect chapter titles. You'd need to hunt down > >>>> the template that writes chapter headings and do something similar. > >>>> > >>>> You'll need to get a little intimate with the XSLT in order to do this > >>>> my way. I am assuming you already have a customization layer > >>>> > >>>> ( > http://www.sagehill.net/docbookxsl/CustomMethods.html#CustomizationLayer). > >>>> Maybe someone has a simpler solution. > >>>> > >>>> Hope this helps. > >>>> > >>>> Peter > >>>> > >>>> On Tue, Feb 11, 2014 at 11:53 PM, natk <[email protected]> wrote: > >>>> > Hi, > >>>> > > >>>> > Thanks. > >>>> > > >>>> > The use-case for this is you're reading the document, and you want > to > >>>> > communicate a particular spot in the document to someone else. You > >>>> > click on > >>>> > the document, and that gives you the URL (document#anchor) to send. > >>>> > > >>>> > Nat > >>>> > > >>>> > > >>>> > > >>>> > On Wed, Feb 12, 2014 at 3:48 PM, Peter Desjardins > >>>> > <[email protected]> wrote: > >>>> >> > >>>> >> Hi. > >>>> >> > >>>> >> Typically, this sort of question should go to > >>>> >> [email protected] because it is about publishing > >>>> >> tools > >>>> >> rather than the XML source. > >>>> >> > >>>> >> I can image writing customization code that would do this. It > doesn't > >>>> >> look too difficult once you find the template that writes the > >>>> >> headings. > >>>> >> > >>>> >> But I'm curious about the intent. Do you want to make each heading > a > >>>> >> link to itself? I don't understand how that would be useful. > >>>> >> > >>>> >> Maybe I am not understanding what you are trying to accomplish? > >>>> >> > >>>> >> Peter > >>>> >> > >>>> >> On Tue, Feb 11, 2014 at 10:36 PM, natk <[email protected]> wrote: > >>>> >> > Hi, > >>>> >> > > >>>> >> > I wondered if there is any way of creating clickable titles in > the > >>>> >> > HTML > >>>> >> > output of docbook. > >>>> >> > > >>>> >> > The output would look something like: > >>>> >> > > >>>> >> > <h1 id="title"><a href="#title">Title</a></h1> > >>>> >> > > >>>> >> > The reason for doing this would be to be able to identify and > >>>> >> > communicate > >>>> >> > particular sections of a document. > >>>> >> > > >>>> >> > Nat > >>>> > > >>>> > > >>> > >>> > >> > > >
