Phil, David and Markus!
Thanks a lot for your help. I have adjusted my mother file by adding the
xi:fallback lines. Now the FO/PDF and HTML output looks good and
supplies proper information.
I agree to Markus' opinion, that adjusting the scripting (which produces
the referenced files) would be
I'm not sure if anyone mentioned this, but you could customize the scripting to
handle unresolved xincludes. You create a template that matches on xi:include
to output your own message. The default message comes from this template that
matches on any unrecognized element:
xsl:template match=*
Any help??
spr wrote:
I have to create a page-master for legal notice-only. In the page sequence
it appears after the default titlepage.
But, despite spending long time reading the customization section on TDG5,
I am stuck at 2 places:
1) The pages (recto verso) are being generated,
Hi,
You need to do a couple of things to get this to work.
1. In your titlepage spec file, omit the d: namespace prefix on this
attribute value:
t:element=legalnotice
instead of d:legalnotice. I know, it is DocBook 5, but this attribute is
used to create the named template, and the
In your ant build file, what process is being used to resolve the
XIncludes? Is there a separate step that creates a temporary XML file with
XIncludes resolved before the stylesheet is applied? If so, then you can
examine the xml:base attributes in it to see if those are correct. If they
Actually, I missed the part in your message where you mentioned the
keep.relative.image.uris parameter. If keep.relative.image.uris is set to
1, then each relative path is *not* altered to account for xml:base
attributes. For FO output, that parameter should be set to zero, except
under
Why not just customize the link template itself, then?
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: Sam Steingold [EMAIL PROTECTED]
To: docbook-apps@lists.oasis-open.org
Cc: DocBook Apps docbook-apps@lists.oasis-open.org
Sent:
Rob Cavicchio ([EMAIL PROTECTED]) kindly volunteered to test my Turkish
HTML Help files on a Windows system set up as a Turkish system. It turns
out that when the HTML Help files are compiled on this Turkish system, then
the Index and Search window panes display the correct windows-1254
Do you still have a legalnotice on your book verso titlepage? Can you tell
what element is producing the duplicate ID by looking in the FO file?
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: spr [EMAIL PROTECTED]
To:
Sorry, I lost the thread a bit there. You could have your special
filename template call the link template, but add a new parameter to
express different behavior. Then you could customize the link template to
accept the new parameter, and behave somewhat differently when it is set.
Did you validate the file before processing? An XSLT process does not stop
to validate a file before processing. It just checks a DTD for any entity
references it needs to resolve.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From:
Hi Tino
This sounds a bit like the xml:base problem I had a couple of years
ago. See the mail below and the pre-processing xsl step to remove
duplicate directory names.
Ron
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=1.0
!--
Yes, it does require copying the template to change it. That is often the
case in customization layers. Did you take a look at calling the
simple.xlink template instead?
Bob Stayton
Sagehill Enterprises
DocBook Consulting
[EMAIL PROTECTED]
- Original Message -
From: Sam Steingold
13 matches
Mail list logo
