[Fwd: Re: [docbook-apps] using chunk.xsl to create index and chaptersfor use in frameset]

[Paul Taylor <paul_t100@fastmail.fm>]

-------- Original Message --------
Subject: 	Re: [docbook-apps] using chunk.xsl to create index and 
chapters for use in frameset
Date: 	Mon, 20 Sep 2004 09:59:06 +0100
From: 	Paul Taylor <paul_t100@fastmail.fm>
Reply-To: 	paul_t100@fastmail.fm
To: 	Bob Stayton <bobs@sagehill.net>
CC: 	docbook-apps@lists.oasis-open.org
References: 	<414B0CCF.5040103@fastmail.fm> 
<050801c49cdd$a1af6b30$6401a8c0@toshiro>



Thanks managed to get it working ok.

But still unable to get chunker.output.indent to work, my files are all 
on one line. Im probably using the paramter in the wrong place but cant 
really see where I am meant to put it or understand how it is different 
to the other paramters that I have managed to get working.
I call the follow .xsl with Saxon to generate my output.

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
               version='1.0'>
<xsl:import href="./chunk.xsl"/>
<xsl:param name="section.autolabel" select="1"></xsl:param>
<xsl:param name="spacing.paras" select="'1'"></xsl:param>
<xsl:param name="html.stylesheet" select="'style.css'"></xsl:param>
<xsl:param name="target.window" select="'main'"/>
<xsl:template name="user.head.content">
     <base  target="{$target.window}"/>
</xsl:template>
<xsl:param name="chunker.output.indent" select="'yes'"/>
</xsl:stylesheet>

Bob Stayton wrote:

>This reference shows you how to add the target for a frameset:
>
>http://www.sagehill.net/docbookxsl/HtmlFrames.html
>
>It is a bit of a kludge, as the stylesheets really don't have an option to
>generate files that have the proper behavior in all cases in a frameset.
>
>To get rid of the header and footer navigation in the TOC, you could
>customize a copy of the 'chunk-element-content' template from
>html/chunk-common.xsl.  You could wrap an xsl:if around the call to
>header.navigation and footer.navigation.  If it is only for the TOC file,
>then the $prev parameter will be empty, so you could test for that.
>
>Customizing the behavior of the chunking stylesheets is a little harder than
>the regular stylesheet because of the way different templates are imported.
>See this reference to see how to set up a chunking stylesheet customization:
>
>http://www.sagehill.net/docbookxsl/ChunkingCustomization.html
>
>The chunker.output.indent parameter does work, but it works differently in
>xsltproc.  xsltproc has 'yes' by default.  It breaks the lines, but doesn't
>indent.  Setting it to 'no' will cause long lines.  Is that what you are
>getting?
>
>Bob Stayton
>Sagehill Enterprises
>DocBook Consulting
>bobs@sagehill.net
>
>
>----- Original Message ----- 
>From: "Paul Taylor" <paul_t100@fastmail.fm>
>To: <docbook-apps@lists.oasis-open.org>
>Sent: Friday, September 17, 2004 9:11 AM
>Subject: [docbook-apps] using chunk.xsl to create index and chapters for use
>in frameset
>
>
>  
>
>>Anyone pleae help, ive managed to created simple html documents with
>>Docbook but Im struggling using chunks
>>
>>Using docbook 1.65 xsl I have processed a docbook and it creates an
>>index.html and various chxx.html files the trouble is if I put it into a
>>frameset with the index on the lhs and the chapter on the rhs I want
>>clicking on a link in the lhs to update the rhs but it doesnt because
>>there is no target attribute in the index.html. I know it I can fix this
>>using search and replace but I would like it all to be automated.
>>
>>The index page also contain prev and next buttons in the header which I
>>do not want.
>>
>>Also I call the following  xsl file:
>>
>><xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
>>                version='1.0'>
>> <xsl:import href="./chunk.xsl"/>
>> <xsl:param name="chunker.output.indent" select="'yes'"/>
>></xsl:stylesheet>
>>
>>but the parameter chunker.output.indent which is meant to make the
>>output easier to read doesnt seem to have any effect. I tried replacing
>>chunk.xsl
>>with chunker.xsl but didnt seem to make any difference, Im not sure
>>which one I should use.
>>
>>
>>
>>    
>>
>
>
>
>  
>