https://issues.apache.org/bugzilla/show_bug.cgi?id=45237





--- Comment #1 from Andreas L. Delmelle <[EMAIL PROTECTED]>  2008-06-19 
06:46:54 PST ---

Just had an idea. To be considered together with the already mentioned swapping
startOfNode() and addChildNode():

The problem is that FOText.endOfNode() (and subsequentially
FOEventHandler.characters()) is called before handleWhiteSpace().

If we remove the endOfNode() call from flushText(), and instead call
endOfNode() for the text-nodes upon addChildNode() for the following node
(after handleWhiteSpace()), the issue should be partly alleviated. The
FOEventHandler will then receive characters() for text-nodes that have been
treated and the ignorable white-space is no longer reported in those events...

For fo:characters, we could move the call to FOEventHandler.character() to
endOfNode(). We would then only need to make sure that this particular
endOfNode() call is skipped in FOTreeBuilder (?)

For inline-level FOs, there would still need to be some sort of deferral (since
the XMLWhiteSpaceHandler also has to wait until either the next node or
Block.endOfNode() to finish them).


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to