I don't know about the 0.20.5 code base, but the upcoming 1.0 code base raises the duplicate-id error message only while parsing the input stream (before any breaking up the formatting object into blocks occurs) so this error should not occur in future releases. In 1.0, ID's can (and are) subsequently attached to multiple layout blocks--that is not an XSL error. ID's just cannot be duplicated on multiple FO's in the input.
Glen --- Riz Virk <[EMAIL PROTECTED]> wrote: > I've actually noticed that problem (id xxx already > exists) even when we have been able to manually > verify that an id hasn't been used twice in the > document. > > fop seems to have a bug that if a block spans > pages,and that block has an id associated with it, > then fop tries to create two destinations with the > same id, which triggers the error above. > > The only way were able to resolve it was to hack the > fop source code to fix it ... > > Thanks > Riz > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]