OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] <programlisting linenumbering="numbered"> does not number...

We have never been able to use Xerces due to this bug in XInclude:


Note that it has a patch since 2005 (sic!) but hasn't been integrated yet.

Docbook stylesheets rely heavily on xml:base being correct, so if one has non-flat arrangement of source XMLs, all hell breaks loose.


On 02/10/2017 11:21 PM, Dave Pawson wrote:
I can understand the hassle of setting this chain up.
Suggest you isolate each step?

Transformation to xsl-fo
fo processing to PDF.

for 2 I have

java -Xms1024m -cp
net.sf.saxon.Transform -x
org.apache.xml.resolver.tools.ResolvingXMLReader -y
-r:org.apache.xml.resolver.tools.CatalogResolver -s:$1 -xsl:$2 -o:$3

1 is the source,
2 the stylesheet
3 the output
4 any additional saxon params.

Adjust parms as necessary.

(may be out of date). My fop script is

export fophome=/apps/fop10


java -cp $cp org.apache.fop.cli.Main -r -c $fophome/fop.conf -fo $1 -pdf $2

input fo is $1
output pdf is $2


On 10 February 2017 at 20:26,  <stimits@comcast.net> wrote:

I was going by this reference as to requirements, and have not read the
whole book (thus I did not yet see the Java requirement):

Admittedly I'm trying to do something quicker than I should and not reading
everything (I've been through a lot of material, but it's just a drop in the
bucket for everything needed when I really just need to sit down and write
content). I've had some frustrations getting the Java-based processors
working and have tried to stick to the xmllint/jing/xsltproc family for that
single reason. The Java-based processing answer likely also answers my
earlier syntax highlighting question about whether to abandon my current
approach with xmllint.

To use Saxon or Xalan I would have to change the current build scheme, which
I've never succeeded at:
xmllint --output "${OBJ}/${TITLE}_monolithic.xml" --nonet --noent -xinclude
xsltproc --output ${OBJ}/${TITLE}_monolithic.fo ${XSLT}/docbook.xsl
fop -c ${PREFIX}/fop.xconf -fo ${OBJ}/${TITLE}_monolithic.fo -pdf

I realize I'm probably asking a lot, but is there any advice I can get on
editing that chain of commands to instead work with Saxon or Xalan? Getting
past the tools on the command line (for a hand written Makefile) is just
getting frustrating and is why the current chain of commands have never
evolved to anything Java-based.

I do plan on reading more (I'm not resisting reading), but there are other
requirements which tend to require at least a draft to be available sooner
rather than later.


----- Original Message -----
From: Bob Stayton <bobs@sagehill.net>
To: stimits@comcast.net, Docbook <docbook-apps@lists.oasis-open.org>
Sent: Fri, 10 Feb 2017 19:09:00 -0000 (UTC)
Subject: Re: [docbook-apps] <programlisting linenumbering="numbered"> does
not number...
Did you read this section in my online book about line numbering? It
only works with Java-based processors.
Bob Stayton
Sagehill Enterprises
On 2/10/2017 11:01 AM, stimits@comcast.net wrote:

Under DocBook 5.1 I've been able to list programs, but line numbering
has no effect (and there is no error under xmllint or jing). Is there
some ENTITY or other precondition required for line numbering under 5.1?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]