On Mar 12, Neil Roeth ([EMAIL PROTECTED]) wrote:
> On Mar 12, Frank Lichtenheld ([EMAIL PROTECTED]) wrote:
> > On Sat, Mar 05, 2005 at 09:39:44AM +0100, Andreas Barth wrote:
> > > docbook2pdf local-fontconfig-user.sgml
> > > Using catalogs: /etc/sgml/catalog
> > > Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
> > > Working on:
> /build/buildd/fontconfig-2.3.0/doc/local-fontconfig-user.sgml
> > >
> openjade:/usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbrfntry.dsl:83:3:E:
> flow objects at the root must be all of class scroll or all of class
> page-sequence or simple-page-sequence
> > > /usr/share/docbook-utils/backends/pdf: line 9: 3698 Illegal
> instruction $SGML_JADE -t tex -o ${SGML_FILE_NAME}.tex $SGML_ARGUMENTS
> >
> > Some further investigation on this:
> >
> > fontconfig builds fine if jade is installed but not if only openjade is
> > installed. So the real error here seems to be the openjade error, not
> > the segv in docbook-utils that is caused by it.
> >
> > Since I don't know that much about the docbook SGML toolchain, I'm
> > unsure how to proceed: should fontconfig build-depend on jade? Or
> > is this a bug in openjade? Or really in docbook-utils?
> >
> > Gruesse,
> > --
> > Frank Lichtenheld <[EMAIL PROTECTED]>
> > www: http://www.djpig.de/
>
> The openjade error message is saying that there is a problem in the
> stylesheet
> dbrfntry.dsl, part of the docbook-dsssl package. I suppose since the error
> occurs for openjade and not jade that it could actually be an error in
> openjade. I maintain jade, openjade and openjade1.3. I can look into
> whether
> this is an openjade error if someone will tell me how to reproduce it - will
> the error occur if I just get the current source of fontconfig from unstable
> and attempt to build the package?
>
> I CC'ed the docbook-dsssl package on this. It's maintained by Peter
> Eisentraut. Peter, can you take a look at the stylesheets and see if
> there is a problem in dbrfntry.dsl?
I was able to reproduce this using just openjade and the docbook-dsssl
stylesheets, so the problem is not in docbook-utils or its customized versions
of the docbook stylesheets. I was also able to generate without error the
HTML version of the file, which uses the DocBook html stylesheet rather than
the DocBook print stylesheet, so the problem is specific to the print
stylesheet. I'm not a DSSSL expert, but I was able to modify the print
stylesheet so that it did not produce an error. I think this is a
docbook-dsssl problem.
--
Neil Roeth
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
