Hi!
It seems that bidirectional text is not working correctly in 1.5.0svn.
There was an extensive discussion regarding this in July
(http://marc.theaimsgroup.com/?l=lyx-devel&m=115290273717059&w=2), and I
don't know what ever came of that, but the problem still seems to exist.
Is anyone working on this at the moment?
Actually, after playing around with it a bit, it looks like the
generated latex is okay (after adding the cp1255 encoding according to
Georg's instructions), and the problems are only in the frontend (see
details below).
Is anyone out there trying (or succeeding) to use 1.5 with a
bidirectional language?
Dov
Specifically, these are the problems I've run into:
1. Just changing the language using the "language hebrew" LFUN,
results in text which is marked as hebrew, but still appears on the
screen as english. In the latex output, this text appears as hebrew
giberrish.
2. Just changing the keyboard input to hebrew results in the text
showing up as hebrew on the screen. However: (a) while each word is
correctly displayed RTL, the words are still displayed in LTR order,
which is wrong; (b) the text is not marked as hebrew; hence, the latex
doesn't even compile, because it gets all kinds of unexpected characters.
3. Doing both 1 & 2 together results in text which shows up on the
screen as hebrew, and is correctly marked as hebrew. However, problem 2a
still exists, i.e., each word is displayed RTL, but the order of the
words is still LTR. Also, if the paragraph's language (which is
determined by the language of the first letter in the paragraph) is
Hebrew, the entire paragraph should be right-aligned (and indentation
should be from the right, etc.), but it is not. The latex output,
though, is correct in all these aspects.
(In older versions of LyX, only changing the language was necessary,
and you never had to deal with changing the keyboard input. I'm not sure
how all this works / used to work on windows --- I'm on Linux.)
And again, all this only works if I set the document's encoding to
cp1255, after adding it to the hardcoded list of encodings, as Georg
explained. Otherwise, you get the message about changing the encoding to
utf8...
