Yep, that's what I'm doing right now. Basically, I make the FOTreeBuilder a dispatching ContentHandler which forwards/delegates SAX events to the effective ContentHandlers (either the FO tree building ContentHandler or any other sub-tree building ContentHandler). That's a lot like what I did it in AreaTreeParser although I'm trying to make the whole thing more elegant and efficient. I think I'm well on my way now.
On 15.02.2006 20:51:09 Simon Pepping wrote: > On Wed, Feb 15, 2006 at 03:01:52PM +0100, Jeremias Maerki wrote: > > Among other things, I'm currently implementing support for XMP metadata > > as part of my PDF/A-1 work [1]. XMP can consist of elements from a > > number of namespaces which are not necessarily known beforehand, > > especially since you can add arbitrary private extensions to XMP > > metadata. With our current method you get warning messages such as the > > following for unregistered namespaces: > > > > WARNING: Unknown formatting object http://ns.adobe.com/xap/1.0/^CreateDate > > With XMP you may be required to accept any namespace, but you get them > in a well defined subtree. Does that help? Maybe some element may > declare a desired behaviour for its whole subtree? Jeremias Maerki
