Next in thread →
Next in month →
Re: DOCBOOK-APPS: PassiveTeX error with 1.52.1 XSL Stylesheets
Also, for your enjoyment... the full log
(nonstopmode) of the bad output using
pdfxmltex, the file is attached.
AM
----- Original Message -----
From:
fyl2xp1
To: fyl2xp1 ; docbook-apps
Sent: Tuesday, July 09, 2002 9:12
AM
Subject: Re: DOCBOOK-APPS: PassiveTeX
error with 1.52.1 XSL Stylesheets
oh and in typical idiot style I forgot to include
the files I said were attached...
here they are :)
----- Original Message -----
From:
fyl2xp1
To: docbook-apps
Sent: Tuesday, July 09, 2002 8:57
AM
Subject: DOCBOOK-APPS: PassiveTeX error
with 1.52.1 XSL Stylesheets
I installed the latest stylesheets 1.52.1 and
then tried to render PDF from the
formatting objects output, created with
xsltproc, with pdfxmltex. Everything worked
fine with version 1.51.1, with this new version
I get this strange error:
xmltex version: 2000/09/07 v1.8y
(Exp):
(c:/docbook/TeXLive/texmf/tex/xmltex/base/xmltex.cfg)
No File: test.cfg
(c:/docbook/TeXLive/texmf/tex/xmltex/passivetex/fotex.xmt
! Illegal parameter number in definition of
\x@temp.
(to be read again)
1.2 ...ustify" line-height="normal"
language="en">
<fo: layout-master-set><fo:...
It seemed to be complaining about the
line:
font-family=""Times
Roman",serif"
which using the old version was:
font-family="Times Roman"
so I changed this to:
"Times Roman,serif"
and tried again, generating the
error:
! Illegal parameter number in definition of
\x@temp.
<to be read again>
1.2 ...ont-family=""Times
Roman",serif">
©</fo:inline>
1998 Yo...
so I found what I thought was the offending
line:
font-family=""Times
Roman",serif">
and changed it to
"Times Roman,serif"
then tried again, generating the
error(s):
LaTeX Warning: Reference 'id360373' on page 1
undefined on input line 2.
LaTeX Warning: Reference 'id360388' on page 1
undefined on input line 2.
! Missing \endgroup inserted.
<inserted text>
\endgroup
1.6 </fo:block></fo:block></fo:flow>
</fo:page-sequence></fo:root>
Well i'm stymied, I don't know why it was
asking for inputfile.cfg?
I tried creating this file and left it
empty but that did nothing.
I also tried changing the fonts to exactly the
same as the other
(not including the serif bit), that did
nothing. So I have included
the actual formatting object outputs from
version 1.51.1 (goodfo)
and version 1.52.1 (badfo) and their logs,
(good.log) and (bad.log)
respectively. (note that bad.log was
prematurely exited with CTRL-C)
Regards
AM
Attachment:
fullbadlog.log
Description: Binary data
Next in thread →
Next in month →