Glen Mazza wrote:
1.) Discontinue the dynamic discovery and run-time
adding capability of ElementMappings.
-1
(a) It doesn't appear to work without source code
changes anyway -- I was suspecting, and Peter had
confirmed
(http://marc.theaimsgroup.com/?l=fop-dev&m=105467992322684&w=2),
that dynamically adding mappings won't help unless the
code understands the semantics of the new mappings,
i.e., what the Area Tree needs to do with them.
Which, in the case of existing, working, extensions, it does.
That the semantics of the extensions have to be realized somewhere is tautological, even if those semantics are "filter out."
The answer is: it depends. If the areas the extension element creates can be handled by the renderer, and the extension is put into places where the FO content model isn't yet enforced by the code, there is no problem to add it without further code changes.
The MathML and Plan samples actually depend on this.
Hmmm.
Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
