How is it included now? It isn't in docbook.xsl directly.
I don't really want l10n living in my top-level customization layer,
there must be a way somehow.
On 11/2/07, Mauritz Jeanson [EMAIL PROTECTED] wrote:
-Original Message-
From: [EMAIL PROTECTED]
I'd like to keep the same
-Original Message-
From: [EMAIL PROTECTED]
How is it included now? It isn't in docbook.xsl directly.
I don't really want l10n living in my top-level customization layer,
there must be a way somehow.
1. The standard en.xml is found via the l10n.xml parameter in
common/l10n.xsl:
Hi Jacques,
On Freitag, 2. November 2007, Jacques Foucry wrote:
On 2 nov. 07, at 23:35, Thomas Schraitle wrote:
1. Did you validate your files? How?
My files are validate with saxon with a oXygenXML scenario.
2. Do you use XIncludes or external entities?
I use XInclude, enabled in
On 3 nov. 07, at 13:23, Thomas Schraitle wrote:
A solution could be to insert the parent para with an os=leopard
like
this:
para os=leopardPlease refer to xref linkend=anID/./para
Did you tried this?
I just tried and it works.
I found the exact problem. with profile.os=tiger defined
This usage of profiling attributes on XIncludes like this:
xi:include href=TimeMachine.xml os=leopard/
can be made to work if you are willing to add steps to the processing
chain. With single-pass profiling with XIncludes, then the xinclude is
resolved before the profiling step, so the os
I have just noticed that when I pass in a text string as a parameter on the
command line, any character references are escaped. For example:
#x2021;
becomes
amp;#x2021;
In my output, I get the literal string #x2021; instead of my special
character.
This seems to be the case with both
Bob == Bob Stayton [EMAIL PROTECTED] writes:
Bob I have just noticed that when I pass in a text string as a
Bob parameter on the command line, any character references are
Bob escaped. For example:
Bob #x2021;
Bob becomes
Bob amp;#x2021;
Bob In my output, I
Hi everyone,
I'm using the latest version of docbook-xsl. Why do I get the following
warning?
citebiblioid encountered in para, but no template matches.
The result (with the fo stylesheet) is a document where the unprocessed
citebibliod elements appear as they were in XML, in red.
Thanks
