Guy Rutenberg wrote:
Hi,
Further more when typing hebrew when LC_CTYPE is configured to a valid
value, and not setting the text as "language hebrew" in LyX (that causes
lyx
to treat the Hebrew as English or the default language) the hebrew text is
displayed right,
Totally correct? Or just the order of the letters within the words is
correct? But are the words ordered correctly, and are the paragraphs
aligned correctly?
The solution in my point of view is to leave the correct display for
Qt and
remove the reversing of letters from Lyx.
If someone will point me where the reversing of hebrew letters is done in
the Lyx code I will try do it my self.
I believe that your analysis of the situation is correct; however, I
still have reservations about the suggested solution:
*) Apparently Qt still isn't working perfectly, either --- why is it so
dependent on the locale settings? It seems to me that the locale setting
should not affect whether or not bidi is applied.
*) I still maintain that LyX is doing a good job with the bidi --- in
all previous versions it was okay, and the problems only arose now that
Qt is also trying to apply it's own bidi algorithm. And even now we see
that LyX is doing it correctly, it's just that Qt is messing it up
(sometimes).
*) I think that if it's at all possible to tell Qt not to apply the bidi
algorithm under any circumstances, that's a much simpler solution. It's
just that starting to undo all of LyX's bidi, and then redoing it with
Qt, is not going to be very easy. The Bidi code is spread out all over
the place --- it's not just the bidi algorithm itself, which is easy
enough to turn off (just turn off the \rtl flag) --- it's also
everything that has to do with paragraph alignment, and making sure that
insets and all are displayed in the right place... It just sounds like
an awfully big job, as opposed to just telling Qt not to apply bidi (if
that's at all possible), and it's sure to introduce lots of bugs, at
least in the short term...
Abdel, I know that you agree with Guy on this one, so maybe you guys are
right... And it's true that for Arabic, letting Qt deal with everything
will probably simplify things a lot... However, it sounds like a really
big job to me, and I think that the alternative would work, and would be
much much simpler, even if it is a little backwards.
I hope we shall solve this bug soon.
Me too.
Dov
