Re: DocBook XSL help? (kafkascampi)

[Robert Lauriston <robert -at- lauriston -dot- com>]

There's no specific TOC level where I want topic breaks. I want them
to match the source (Confluence).

On Fri, Jan 10, 2014 at 9:48 AM, kafkascampi <kafkascampi -at- gmail -dot- com> wrote:
> Generally there is a chunking depth control in the TOC like my fellow Chris
> mentioned. Set it at 1 to chunk every section in a topic, etc.
>
> In the answer on Stackoverflow, he mentions the chunking XSL file xhtml
> chunk.xsl. It's my guess your customization layer imports that file. You can
> copy the TOC depth spec from chunking XSL file and add it to your customized
> XSL.
>
> HTH
>
> Chris
>
>
>
>
> On Thu, Jan 9, 2014 at 2:28 PM, Robert Lauriston <robert -at- lauriston -dot- com>
> wrote:
>>
>> My understanding is that the xml:id tags control both chunking and the
>> TOC. Currently every heading that's in the TOC starts a new chunk.
>>
>> My gut feeling is it would be easier to mofify the chunking the
>> "right" way by modifying the DocBook+WebHelp project than to kludge it
>> with post-processing. I got some feedback from the developer:
>> http://stackoverflow.com/questions/20980281/docbook-xsl-chunking/20987759
>>
>> Another option is to modify the Velocity template that controls the
>> DocBook export from Confluence and generate a custom plug-in. That's
>> kind of a pain but it's a devil I already know. And that way any
>> future changes to DocBook+WebHelp would probably not break my build
>> process.
>>
>> On Thu, Jan 9, 2014 at 12:37 PM, Chris Despopoulos
>> <despopoulos_chriss -at- yahoo -dot- com> wrote:
>> > Well, rename the things that would normally chunk to something that
>> > won't?
>> > I think the chunking is determined in the TOC spec.  (I don't have the
>> > stuff
>> > in front of me right now, so I'm flying by instruments...)  Anyway, I
>> > bet if
>> > you removed most of the entries in that parameter (or comment them out),
>> > then you would not get chunking on those boundaries.  So after you wrap
>> > the
>> > PIs in something that will chunk, then remove the chunking you don't
>> > want????  Hey, I'm just guessing but this is how I'd try it if it was my
>> > problem.
>> >
>> > cud
>> >
>> > ________________________________
>> > From: Robert Lauriston <robert -at- lauriston -dot- com>
>> > To: Chris Despopoulos <despopoulos_chriss -at- yahoo -dot- com>;
>> > "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
>> > Sent: Thursday, January 9, 2014 12:48 PM
>> > Subject: Re: DocBook XSL help? (kafkascampi)
>> >
>> > But how would I get rid of all the unwanted chunks? I don't think I
>> > could just strip out the xml:id tags since I believe those are used
>> > for other purposes as well.
>> >
>> > On Thu, Jan 9, 2014 at 1:13 AM, Chris Despopoulos
>> > <despopoulos_chriss -at- yahoo -dot- com> wrote:
>> >>
>> >> My guess would be that you'll not find anything in the provided XSL
>> >> that
>> >> transforms a processing instruction into chunk.  So what I would do is
>> >> first
>> >> run a transform that uses the processing instruction to wrap the
>> >> content in
>> >> a sect.  Then (again, I'm only guessing) you could run that result
>> >> straight
>> >> through the provided transform and get what you want.  You might need
>> >> to add
>> >> IDs to your sects that you create, or do some other tweaks.  But I
>> >> think
>> >> that is the tree I would bark up.
>> >>
>> >> cud
>> >>
>> >>
>> >> On Tue, Jan 7, 2014 at 11:38 AM, Robert Lauriston
>> >> <robert -at- lauriston -dot- com>wrote:
>> >>
>> >>> Can anyone point me to the part of this file that controls chunking?
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> http://docbook4j.googlecode.com/svn-history/r4/trunk/docbook4j/src/main/resources/xsl/docbook/webhelp/xsl/webhelp-common.xsl
>> >>>
>> >>> I can't relate what I find in this doc to the code I see in that file:
>> >>>
>> >>> http://www.sagehill.net/docbookxsl/Chunking.html
>> >>>
>> >>> I want to modify the XSL so that it chunks at <?confluence type="page"
>> >>> ?> instead of <section xml:id= ...>.
>> >
>> >
>>
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
>> authoring.
>>
>> Learn more: http://bit.ly/ZeOZeQ
>>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> You are currently subscribed to TECHWR-L as kafkascampi -at- gmail -dot- com -dot- 
>>
>> To unsubscribe send a blank email to
>> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>>
>>
>> Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
>> http://www.techwhirl.com/email-discussion-groups/ for more resources and
>> info.
>>
>> Looking for articles on Technical Communications?  Head over to our online
>> magazine at http://techwhirl.com
>>
>> Looking for the archived Techwr-l email discussions?  Search our public
>> email archives @ http://techwr-l.com/archives
>
>


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives