On Oct 10, 2006, at 22:25, J.Pietschmann wrote:
Andreas L Delmelle wrote:
I was thinking to use an approach analogous to the current
refinement white-space handling: one BidiProcessor stored in the
FOEventHandler.
This may have inindented consequences: some output formats expect the
ultimate user client to do BIDI formatting, which means the renderer
has to undo some of the mirroring done while constructing the FO tree.
Just to make everything clear:
I would not yet perform any character substitutions or such at FOTree
stage, but simply the insertion of bidi-overrides and splitting of
inlines based on the directionality of the characters, so that the
layoutengine at least never needs to bother with determining the
directionality of *each* character in the text-flow. The
LayoutManagers can depend on the writing-mode-related properties set
on their own FObj. Directionality changes, from the POV of the
layoutengine, would always coincide with a FO boundary.
So I'm guessing these unintended consequences do not really apply.
The name I used for the class was a bit of an unfortunate choice,
though...
Cheers,
Andreas
