Re: DOCBOOK: Problems creating pdf file of tdg

[Bob Stayton <bobs@caldera.com>]

On Mon, Feb 04, 2002 at 09:23:07PM +0100, Kraa de Simon wrote:
> Hello,
> 
> Can anyone help me converting the DocBook: The Definitive Guide (xml files)
> to pdf format?
> 
> Or give me some useful hints?
> 
> On Windows 2000.
> 
> Thanks,
> 
> Simon.
> 
> This is what I did...
> 
> Using:
> 
> - Windows 2000
> - DocBook: The Definitive Guide from CVS
> - Saxon 6.5
> - Docbook-xsl-1.48
> - Fop-0.20.3rc-bin
> - Xep_27_eval_msjvm
> 
> Create fo file using saxon
> ----------------------------------------
> When I create the fo file using saxon I get errors like:
> 
> ...
> term width: 5em
> term width: 5em
> alt encountered, but no template matches.
> term width: 8em
> term width: 5em
> ...
> 
> How can I prevent these errors to occur?

The 'term width' error is a useless message that should
be turned off in the lists.xsl stylesheet file.  You could
file a bug in the Docbook sourceforge project to request
that.

The '* encountered, no template matches' errors indicate
that the fo stylesheets are not complete and are missing
templates for valid elements.  Gather them up and
file another bug.

> 
> The fo file is successfully (?) created though (size approximately 13 Mb).
> 
> Convert fo file to pdf file using fop
> ----------------------------------------
> When I try to convert the fo file to a pdf file using fop the conversion
> seems to "hang" somewhere at the  start. An invalid pdf file is created
> (size approximately 3707 bytes)
> 
> ...
> [WARN]: property - "last-line-end-indent" is not implemented yet.
> [WARN]: property - "last-line-end-indent" is not implemented yet.
> [INFO]: [20]
> [INFO]: [21]
> ...
> (no response at this point)
> 
> Convert fo file to pdf file using xep
> ----------------------------------------
> when I try to convert the fo file to a pdf file using xep I get errors like:
> 
> c:\xep>run tdg.fo
> (document
> [input tdg.fo]
> [output tdg.pdf]
> (S (parse [system-id file:/D:/xep/tdg.fo]
> {!line 3207, column 58: Attribute "xlink:type" must be declared for element
> type
>  "a".}
> 
> {!line 3207, column 78: Attribute "xlink:show" must be declared for element
> type
>  "a".}
> 
> {!line 3207, column 100: Attribute "xlink:actuate" must be declared for
> element
> type "a".}
> 
> {!line 3207, column 114: Attribute "href" must be declared for element type
> "a".
> }
> 
> {!line 3207, column 141: Element type "a" must be declared.}
> 
> {!line 3208, column 12: The content of element type "fo:block" must match
> "(#PCD
> ATA|fo:initial-property-set|fo:bidi-override|fo:character|fo:external-graphi
> c|fo
> :instream-foreign-object|fo:inline|fo:inline-container|fo:leader|fo:page-num
> ber|
> fo:page-number-citation|fo:basic-link|fo:multi-toggle|fo:block|fo:block-cont
> aine
> r|fo:table-and-caption|fo:table|fo:list-block|fo:footnote|fo:float|fo:multi-
> swit
> ch|fo:multi-properties|fo:wrapper|fo:marker|fo:retrieve-marker|rx:fall-throu
> gh)*
> ".}

Indeed, the fo file is not valid.  The problem is
the little kludge to insert a separate text file
inside a programlisting.  See for example ch03.xml
line 607 in the current CVS version.

This requires the use of
the textinsert extension of each XSLT processor
(only Saxon and Xalan are supported at this point).
Without that processing, you get an <a> element (!)
with xlink attributes.  Needless to say, an <a>
element inside an fo file is not valid, and is probably
a holdover from the html stylesheets (another bug).

Try setting the stylesheet parameters 'use.extensions' and
'textinsert.extension' to '1' and see if that gets you
further along. 


Bob Stayton                                 400 Encinal Street
Publications Architect                      Santa Cruz, CA  95060
Technical Publications                      voice: (831) 427-7796
Caldera International, Inc.                 fax:   (831) 429-1887
                                            email: bobs@caldera.com