Am Sonntag, 25. März 2007 00:12 schrieb Abdelrazak Younes: > Georg Baum wrote: > > Dov Feldstern wrote: > > > >> Attached is a patch applying this fix. Hebrew should now work even with > >> real, legal, locale settings! (I haven't tested the Arabic at all, I > >> have never used Arabic in LyX and have no idea what the current state > >> is, or what it ever was. I also am not currently set up for testing > >> Arabic, and I'm not sure how one would go about it. I'd be happy to get > >> any input on this.) > > Each and every arabic letter has a different shape if it is at the > beginning, the middle or the end or a word. So it would really be better > to let Qt handle that really.
I agree, but I fear it is not possible: The shaping is supposed to happen after applying the bidi algorithm (according to unicode.org). Since I believe that we need to do our own bidi stuff (see below). I also think we need to do our own shaping. > >> * I'm not sure that using Qt's Bidi would mean that we wouldn't need > >> to use our own anyhow. We'd still need to know how things look on the > >> screen, for laying out insets; for cursor movements across the screen; > >> etc. So would we really be able to just use Qt's bidi? > > > > I agree with you here, this last point being the main reason. > > I still disagree and still think we should let Qt decide at word level > and disable the LyX bidi code there. How would navigation etc be handled when insets are involved? I believe that we need some sort of our own bidi stuff even if we let qt handle bidi of normal text. > Arabic support is obviously broken > now. But as I haven't done anything up to now, I won't complain. I fixed that yesterday (at least I think I did), so all that needs to be done is testing. Georg
