> I'll post a RFE?/Bug report? to the FOP mailing list. (If you could do > the same thing, it would be nice: two votes are better than one.)
I am no longer sure whom to blame. I would even go so far to say that the fop behaviour is somewhat correct: The docbook stylesheets try to generate a (hyperlinked) list of tables at the beginning of a document. If the doc has two table elements with the same ID one on page X and the other on page Y, where should the corresponding links point to -- the first or second instance of the ID? I tried a sample document (transformed with the docbook stylesheets 1.70.1) with XEP 4.4 (the free edition). As you have already said, XEP does not complain about the duplicate ID but the result is not correct (at least not in my opinion): The list of tables correctly shows the table two times but with identically page numbers. To me it seems it more and more to be a conceptual problem in the usage of xi:include along with IDs rather than a formatter issue. puzzled Patrick -------- Original-Nachricht -------- Datum: Wed, 23 Aug 2006 11:00:24 +0200 Von: Hussein Shafie <hussein at xmlmind.com> An: Patrick Riffel <versorger at gmx.li> Betreff: Re: [XXE] (no subject) > Patrick Riffel wrote: > > > >>Sure, we do that all the time here at XMLmind. The main difference > >>between you and us is that we do not feel the need to double-check our > >>documents using xmllint. > > > > Well, it's less a reason of double-checking than one of automation > issues. I use XXE as an editor in a "classical" docbook toolchain: Part of > that > is two resolve xincludes via xmllint, do the xsl transformation with saxon > and create the PDF with apache's fop. And while I could very well live with > a duplicate ID, fop throws an error and stops transformation. > > I understand. This is really a problem. > > * Saxon (or is it the XSLT style sheet?) just issues this warning: > Warning: multiple "IDs" for constraint linkend: limitation_list. > > * Both FOP 0.20.5 and FOP 0.92beta throw a ValidationException and stop > working. > > * RenderX XEP happily converts the XSL-FO to PDF. > > * Same with XMLmind FO Converter. > > > > > Any idea how to deal with this? BTW, the 3.3 feature to ignore such > errors sounds promising, at least for the editing part ... > > Well, with FOP 0.92beta, using configuration parameter > strict-validation=false or using command-line option -r should have > forced FOP to ignore such benign validation error. But unfortunately I > cannot get that to work. > > I'll post a RFE?/Bug report? to the FOP mailing list. (If you could do > the same thing, it would be nice: two votes are better than one.) -- "Feel free" ? 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
