Patrick Riffel wrote: >>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?
* Does it make sense for an *XSL-FO* *renderer* to completely stop working when it finds duplicate IDs? Common sense says no. * Does it make sense for FOP to completely stop working when it find duplicate IDs, even when you have specified "strict-validation=false"? Common sense says no. > 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. There is nothing wrong about that. RenderX XEP did its best efforts to render two tables having the same ID. > 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. You'll have the same problems with plain old external entity references. Simply add: --- &my_table; &my_table; --- in the same document and you'll see. IMHO, it is a conceptual problem in the usage of *IDs*. --- PS: DITA modular documents have no such problems. See "Cross References" in "DITA for DocBook" http://norman.walsh.name/2005/10/21/dita
