thanks a lot Keiron,

I generated the fo-file and it contains NO duplicate id's. Nevertheless
fop crashes with:
org.apache.fop.apps.FOPException: The id "..." already exists in this
document

So it is nearly sure, that this is a fop bug.

Because I can't find a workaround, it would be nice if somebody cares about
this
problem (maybe a redesign of the "rather buggy way of handling id's", maybe
a workaround).

If you need more detailled informations or if there are others things
I can help with, let me know.


-----Ursprüngliche Nachricht-----
Von: Keiron Liddle [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 30. Juli 2002 11:24
An: FOP
Betreff: Re: any limitation to "generate-id()"


On Tue, 2002-07-30 at 11:14, Kutz Clemens (PEA-FE2/BA-T) wrote:
> Good idea. How can I do this? AFAIK fop doesn't have this output option.
> (I think it's a silly newbie question for the one's, who are familiar with
> xalan, xerces, ... but I think I only need a sample commandline)

do this:
java org.apache.xalan.xslt.Process -IN test.xml -XSL test.xsl
with xerces and xalan in the classpath.
The result will go to stdout.

> Maybe it could help if fop-dev's tell us, how the generate-id() function
and
> the detection of duplicate id's works internally (because the spec says
> nothing about it, except this task can be solved by the
> dev's as they like and as they think it's useful).

The generate-id() function has nothing to do with fop. Fop only handles
the fo->pdf conversion.
The detection of duplicate id's however is done in fop. When an area is
added to the area tree it adds the id of the area. This should only
happen once but can also be removed and readded etc. It is checked when
the id is added. It is a rather buggy way of handling it.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to