Hi all!
I'm trying to use the custom.xsl here:
https://svn.berlios.de/svnroot/repos/web-cpan/doc-Hebrew-HTML-Tutorial/trunk/hebrew-html-tutorial/
(You can use the svn checkout to checkout it.)
What it's trying to do is to propagate xml:lang into various elements
that I'm using and require it.
I can't see any evidence – in the appearance of my PDFs or in the
intermediate FO files – that my dbfo PIs are being processed.
For example, my understanding of the following (adapted from Stayton, *DocBook
XSL*, 3rd edn 2005, p274)
paraNow is the time for all good men/para
para?dbfo
-Original Message-
From: Stephen Taylor
I can't see any evidence - in the appearance of my PDFs or in
the intermediate FO files - that my dbfo PIs are being processed.
For example, my understanding of the following (adapted from
Stayton, DocBook XSL, 3rd edn 2005, p274)
Thanks for the quick reply. I see I had taken dbfo PIs to be more general
than they are.
Here is a better example of my problem, taken directly from Stayton.
sidebar
titleSidebar example/title
?dbfo sidebar-width=2.5in ?
paraA sidebar can be used to emphasise…/para
/sidebar
With or
Hi Stephen,
Your example works for me when I test it with xsltproc, 1.74.0 stylesheets, and
XEP. What processor setup are you using?
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
- Original Message -
From: Stephen Taylor
To: Mauritz Jeanson
Cc:
The double.sided parameter seems to require a string value, which appears
counter-intuitive since its documented default is a zero.
xsl:param name=double.sided select=0/xsl:param
is default and disables double-sided layout. So
xsl:param name=double.sided select=1/xsl:param
looks like it should
I'm not able to duplicate this problem. Using a number value works for me, and
I'm not able to find any combination of processors where it does not. I'm not
sure what's going on that would cause it to not work for you.
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
- Original
Hi Shlomi,
The template named language.attribute generates an xsl:attribute element,
and it must appear just after an output element's start tag. The problem is
that in your custom template, you are calling that template and generating
an attribute but you have not started an output element
Mauritz Jeanson mj at johanneberg.com writes:
-Original Message-
From: mercuron at gmx.ch
I'm using Xalan-2.7.0 with Xerces-2.7.1 and docbook-xsl-1.73.2.
[...]
Is there any way to force the docbook stylesheets not to use
named entities for the target db?
Are there
Yes, please file a feature request on DocBook SourceForge with any details
you can provide. Thanks.
Bob Stayton
Sagehill Enterprises
[EMAIL PROTECTED]
- Original Message -
From: Marco [EMAIL PROTECTED]
To: docbook-apps@lists.oasis-open.org
Sent: Friday, August 22, 2008 1:10 PM
10 matches
Mail list logo