> OK, some overall (hard) questions:
>
> o What does it mean to split the carret? I haven't tried the code,
> but will tomorrow. Would be good with an explanation in words
> though.
The problem with the BiDi text is that sometimes one position in
the text of the document coresponds to two distinct positions on
the screen. When the insertion point is at such a document
position the place where an inserted character appears on the
screen depends on its direction, i.e., if you just display an 'normal'
insertion point, the inserted character can in fact appear
somewhere coletely different than where the insertion point
indicates. To get arround that, you display two insertion points at
both screen locations, with little flags indicating which direction
either of these is for. There is a test document included in the
patch under /test/wp/ called BiDitest.abw (I think); if you try to
navigate it, you will see how this works.
> o Finally, what is the code size and performance overhead of just
> making BiDi The Way AbiWord works? Get rid of all the conditional
> code that makes maintainment and understanding harder.
I would be for, but I cannot judge the performance loss, my
machine is too fast, and the BiDi processing does adds quite a bit
of overhead.
Tomas
