Re: Even more Hebrew / Bidi / Encoding Woes (2/2)

[Dov Feldstern]

Abdelrazak Younes wrote:
Dov Feldstern wrote:
Hi!
Another issue with the changes recently made to the encodings. This 
one is actually not a bug, perhaps, rather an "over-fix".

I think it is a bug and it'd be solved by letting Qt do his bidi at 
character levels. The language information is _not_ necessary to order 
correctly the characters.


If it really is a bug, then the bug described is in the backend, not the 
frontend, so I fail to see how Qt has anything to do with it.

On the contrary, I think this is just one more argument *against* using 
Qt for bidi: Qt would do exactly what the gui is already doing now; so 
if we decide that what the gui is doing is correct, then there's no need 
to switch --- that wouldn't change anything. We *would* have to make 
changes to the backend, so that it would match the gui's behavior, but 
that's orthogonal to the question of Qt/non-Qt --- it's in the backend; 
and if we decide that the backend's behavior is correct, then we'll have 
to change the gui --- which right now, we can do, because it's our 
algorithm, but if we were using Qt's bidi then we'd be stuck.

As I know we won't switch to Qt own bidi, we should fix the bidi 
algorithm: The re-ordering of characters should _exclusively_ be based 
on the unicode range not on the language. Fixing the bidi algorithm to 
do that should not be very difficult.


This is certainly an option, however I am far from convinced that this 
is the correct behavior. I'd be happy to hear additional opinions... 
(Georg?)

Abdel.