Re: [docbook-apps] header.content customization bridgehead problem

Thanks Bob,
I am using XEP but I noticed different problem.  I am at 1.69 and it looks like I need to upgrade to get the code below.  It was in the plans but looks like I have a good reason to move it up on the list of things to do.  

In preliminary testing it looks to be working now.

Thanks again,
Joy

On Sat, Jul 23, 2011 at 4:09 PM, Bob Stayton <> wrote:

Hi Joy,

It looks like you would need to customize the 
template with match="bridgehead" in fo/sections.xsl.  It seems that a 
bridgehead is treated as a section of the equivalent level when generating the 
markers.  After computing the equivalent section level of the bridgehead, 
the template sets a variable named "marker":

 

  <xsl:variable 
name="marker">
    
<xsl:choose>
      <xsl:when test="$level 
&lt;= 
$marker.section.level">1</xsl:when>
      
<xsl:otherwise>0</xsl:otherwise>
    
</xsl:choose>
  </xsl:variable>

So when the computed level of the bridgehead is 
less than or equal to $marker.section.level, then it sets the variable to 1. 
That variable is used later to generate the marker.  So set the 
variable's value to zero and no marker should be generated.

 

I can't explain why the bridgehead's marker is used 
when it is not the last one on the page.  What XSL-FO processor are you 
using?

 

Bob Stayton
Sagehill Enterprises


 

 

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

  
From: 
  Joy 
  Andree 

  
To:  
  

  
Sent: Thursday, July 21, 2011 5:37 
  AM

  
Subject: [docbook-apps] header.content 
  customization bridgehead problem

  

For my customization layer I want the header to display the 
  first-including-carryover of the sect1 or section tag on the position left 
  header.  
I have the following parameter set:
  <xsl:param 
  name="marker.section.level">1</xsl:param>
and the fo retrieve 
  marker
           
  <xsl:when test="ancestor::book and ($double.sided != 
  0)>
              
  <fo:retrieve-marker 
  retrieve-class-name="section.head.marker"
                                  
  retrieve-position="last-starting-within-page"
                                  
  retrieve-boundary="page-sequence"/>
            
  </xsl:when>

However, it was noticed that bridgeheads also appear 
  in the header which was not so much as problem as in some cases the header 
  gets stuck on the bridgehead and displays it several pages later.

The 
  bridgehead has only one single line para after it and then a new section 
  starts on the same page so the bridgehead should not be selected in the first 
  place because the sections after it should have been picked up.  The book 
  I am noticing this on is one that uses many bridgeheads.

Is there some 
  way I can turn off it picking up bridgeheads?

Thanks,
Joy

-- 
Joy Andree
Software Developer II
ANSYS, Inc.
275 
  Technology Drive
Canonsburg, PA 15317
Tel: 724-514-2944
---------------------------------------------------------------------------------------------------

The 
  information transmitted is intended only for the person or entity to which it 
  is addressed and may contain confidential and/or privileged material. Any 
  review, retransmission, dissemination or other use of, or taking of any action 
  in reliance upon, this information by persons or entities other than the 
  intended recipient is prohibited. If you received this in error, please 
  contact the sender and delete the material from any 
computer.

-- 
Joy Andree
Software Developer II
ANSYS, Inc.
275 Technology Drive
Canonsburg, PA 15317
Tel: 724-514-2944

---------------------------------------------------------------------------------------------------

The
 information transmitted is intended only for the person or entity to 
which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other use of, or 
taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you 
received this in error, please contact the sender and delete the 
material from any computer.