a) Currently the characters are painted in two ways in the current source:
1) the source itself handles the shaping
2) Qt handles the shaping
It seems that it is possible to let Qt do a part (not all) of the first item
too. I am not sure yet! I will investigate the suggestion more.
b) The current code in the method "Paragraph::transformChar" has a bug,
when the prev_char is a COMPOSE character (such as FATHA) and the previous BASE
character is a SPECIAL character (such as ALEF). In this case the current
character (such as BAA) gets the medial form and gets connected to the previous
SPECIAL character which is not correct. The correct way to handle this
situation is that, similar to the next_char, the first previous non-COMPOSE
character should be assigned to the prev_char if exists.
c) Suppose that we have a text with a mixture of English, Arabic, and Farsi
languages. Therefore consider a paragraph that its main language is English and
it contains both Arabic and Farsi words. The current part of the source that
converts LyX to LaTeX uses the command "\R{}" for both Arabic and Farsi words.
Of course I am not a LaTeX and/or Babel expert but it seems better if LyX uses
the command "\foreinlanguage" instead. Otherwise, how can LaTeX distinguish
between these two languages?
d) When TeX-LaTeX is not installed the menu item "Export to LaTeX (plain)" does
not exist. Isn't it strange?
Mostafa
Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
Yes and no:
Yes, we need generic support.
No, we cannot make abstraction of the language setting, if only because
of LateX support.
I suggest that you get used to the source code and do some testing with
1.5.osvn. Don't hesitate to ask question.
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
