Thank you so much, Bob. That's exactly what I was looking for. 

In going back to my original output, you were right about the index. I was just 
seeing my other appendixes being indented awkwardly. 




--- 
David Goss, M.A. 
Technical Writer, Laboratory Division 
Frontier Science & Technology Research Foundation 
4033 Maple Road 
Amherst, NY 14226 
(716) 834-0900 x7218 

----- Original Message -----

From: "Bob Stayton" <b...@sagehill.net> 
To: "David Goss" <g...@fstrf.org>, docbook-apps@lists.oasis-open.org 
Sent: Friday, June 7, 2013 11:52:29 AM 
Subject: Re: [docbook-apps] body.start.indent with mixed one and two column 
layout 


Hi David, 
You will need to customize the template named 'set.flow.properties' from 
fo/pagesetup.xsl. There is an xsl:choose statement in there that decides how to 
add that property to the fo:flow of each page-sequence. You can modify it to 
handle the elements or pageclasses you want to control. You'll notice that 
pageclass="index" is omitted, so you should not be getting indents in the index 
already. 

Bob Stayton 
Sagehill Enterprises 
b...@sagehill.net 




From: David Goss 
Sent: Friday, June 07, 2013 8:14 AM 
To: docbook-apps@lists.oasis-open.org 
Subject: [docbook-apps] body.start.indent with mixed one and two column layout 


Hi, 

I'm using the column.count.back property to change the layout for the index, 
glossary, etc for our manual to 2 columns. The problem is, this is inheriting 
the indent (body.start.indent, I assume) from the rest of the document. This 
creates a weird look where the back matter columns are intented. I know I can 
just do body.start.intent=0 to fix that, but I want to keep the indent 
elsewhere. I'm not sure what sure what template and/or parameters to customize 
so that body.start.indent=0 only if the current section is 2 columns, otherwise 
it is 4pc. 

Regards, 
David 



--- 
David Goss, M.A. 
Technical Writer, Laboratory Division 
Frontier Science & Technology Research Foundation 
4033 Maple Road 
Amherst, NY 14226 
(716) 834-0900 x7218 


Reply via email to