OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] Html: suppressing separate titlepage for book/article

Along with the stylesheets being hard-coded to always chunk
Article into a separate file, the logic for generating the nav
links is also hard-coded to assume that output for Article
instances are in separate files.

It will take some work to get them to handle it correctly. I think
you should probably open up a new feature request -


In the mean time, I think you might have to live with the current
output. I may just be rationalizing, but speaking just as a user,
I don't find particularly annoying to find a TOC with just one
link (e.g., your "Valgrind Frequently Asked Questions" link) and
then to need to click that to get to the actual content.

But if you have users who think otherwise, you might want to
consider restructuring your source such that your FAQ Article is
not part of a Book in a Set, but is instead a separate standalone

I know that would mess up the auto-generated master TOC for your
Set, but you could instead create the DocBook source for that TOC
manually, using ToC/ToPart/ToCentry markup, and turn off
autogeneration of TOC for your set. It's a flat TOC with only six
entries, so it should not be a big hassle to maintain manually.


Donna Robinson <donna@terpsichore.ws> writes:

> Hi,
> A problem has surfaced wrt navigation.
> The 'next' link now points to a non-existent file.
> Given this:
> <chapter id="cl-annotate" xreflabel="Callgrind Annotate">
>   <title>Callgrind Annotate</title>
>   <xi:include href="cl-annotate.xml" parse="xml"  
>       xmlns:xi="http://www.w3.org/2001/XInclude"; />
> </chapter>
> Then an incorrect $next is being generated from
> <article id="callgrind_annotate">
> so that the nav. link points to
> file:///home/de/BUILD/callgrind-0.10.1/docs/html/callgrind_annotate.html
> when it should in fact point to the next chapter.
> I think (?) this is happening in both 
>   <xsl:template name="header.navigation">
> and
>   <xsl:template name="footer.navigation">
> Am I right in thinking I'm going to have to modify these lines in some 
> fashion:
> <xsl:if test="count($prev)>0">
>   <a accesskey="p">
>   <xsl:attribute name="href">
>     <xsl:call-template name="href.target">
>       <xsl:with-param name="object" select="$prev"/>
>     </xsl:call-template>
>   </xsl:attribute>
>   <xsl:call-template name="navig.content">
>     <xsl:with-param name="direction" select="'prev'"/>
>   </xsl:call-template>
>  </a>
> </xsl:if>
> I'd appreciate some help on what to do here.
> Regards,
> Donna
> (PS: of course all this applies to the 'prev' link also,
> when on the next chapter page)

Michael Smith


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]