Dov Feldstern schrieb:
To repeat myself: ArabTeX without arabi can't be used due to the
missing babel interface and
ArabTeX is not babel-based, and therefore doesn't require a babel
interface.
But LyX currenly uses babel to handle the different languages. Therefore arabi will be used when LyX
inserts \selectlanguage{arabic}.
I don't understand why you don't want to have ONE package for Arabic AND Farsi. This fixes many
problems and keeps it maintainable. Having support for two packages side by side requires much more
maintaining work and expect it will introduce new problems we are currently not aware of.
, more important, due to the missing input encodings.
ArabTeX can use many different encodings, including a
transliteration-type encoding which uses plain ASCII, I think. It does
not include cp1256 by default, AFAICT. However, (a) it does include
other encodings (iso-8859-8, for example), which LyX did support until
recently, I'm not sure if it still does;
Yes but not cp1256 which is required on Windows.
(b) as you have pointed out,
one can use ArabTeX with the cp1256 encoding provided by arabi.
Yes, but then you use automatically arabi not arabTeX, see my explanation above.
arabi is not yet perfect; the fonts for
ArabTeX are nicer; because that's the way it used to be done.
Every pacakge has its disadvantages. I mean we can discuss this again and again without changing
this. But we have to decide what package to use arabTeX OR arabi - both is not an option.
The point is, we used to support it, and we shouldn't just drop that support if
it's not absolutely necessary.
We never supported this since the user has to some manual adjustments before it works. When LyX
would automatically load arabTeX when the user uses Arabic as document language then you can say we
support it.
regards Uwe
