Thanks Bob, that worked perfectly. I just had to remove all of the "d:" 
prefixes to the legalnotice references, but after that it worked just fine.

Eric

-----Original Message-----
From: Bob Stayton [mailto:[email protected]] 
Sent: Friday, April 26, 2013 12:44 PM
To: Eric Nordlund; [email protected]
Subject: Re: [docbook-apps] Combining legalnotice tags

I think so.  You can try this (untested):

1.  Copy the template with match="d:legalnotice" mode="titlepage.mode" from 
html/titlepage.xsl to your customization layer.

2.  Change the match attribute to
match="d:legalnotice[not(preceding-sibling::d:legalnotice)]"

so that only the first legalnotice is handled with this template, which 
generates the output file and the link.

3.  In that template, after the line where it does <xsl:apply-templates 
mode="titlepage.mode"/> to process the content of the first legalnotice, add 
this line to process the content of the others:

<xsl:apply-templates select="following-sibling::d:legalnotice/node()" 
mode="titlepage.mode"/>

4.  To prevent the other legalnotices from being processed normally, add this 
empty template:

  <xsl:template match="d:legalnotice[preceding-sibling::d:legalnotice]" 
mode="titlepage.mode"/>

Let me know if this works or not.

Bob Stayton
Sagehill Enterprises
[email protected]


From: Eric Nordlund
Sent: Friday, April 26, 2013 12:14 PM
To: [email protected]
Subject: [docbook-apps] Combining legalnotice tags


Hello. The source files for my company's books all have 4 legalnotice tags on 
them. This is fine in the PDF output, but in the HTML output I get 4 legal 
notice links on the front page.

Is there a way to funnel all of the legalnotice content into one legalnotice 
page and corresponding link in the final HTML output without changing all of my 
source files?

Thanks!

Eric Nordlund
Customer Documentation and Training
Cray Inc.
901 5th Ave
Seattle, WA 98164
(206)701-2232
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to