On Fri, Feb 25, 2000 at 07:59:22PM +0100, Lars Gullik Bj&resh;nnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
> 
> | Actually, it is possible to use LyX 1.1.5cvs to write Arabic documents
> | (instructions given bellow).
> 
> But there are places where RTL support is dependant on the language
> "hebrew" being used. That does not look right to me.

Did I mention that the Arabic support is a hack?

> | However, there are several limitations to this hack:
> | 
> | 1. BIGGEST LIMITATION:
> |    The text rendering in the LyX screen doesn't use ligatures.
> 
> mmm, I have thought about this (ligatures that is) and have the
> feeling that the cursor positonining will then be a lot harder to do
> correctly.

Why? I think that you only need to change LyXText::SingleWidth

> 
> | 2. There are many problems caused by the limitations of arabtex.
> | Maybe it is better to use omega instead of arabtex.
> 
> Is omega ready for this task as of now?

I don't know what is the current status of omega, but in the future we 
should make LyX use Unicode for storing the text, and then use omega for
the typesetting.

> 
> | 3. xdvi isn't updated automatically after buffer-typeset command
> |     (Why?)
> 
> Is this a problem with arabtex?
> Sounds weird, if it is a more general problem...you have to have xdvi
> setup to refresh on file change.

The problem was with the arablatex script. To fix it, the last line
should be "cat < _$f.dvi >! $f.dvi" (instead of "mv  -f _$f.dvi $f.dvi")

> | 3. Add the following lines to ~/.lyx/lyxrc
> | 

> This one I particulary do not like, this is not a LyX property but a
> language one. I think we should use Jean-Marcs suggestion and store
> rtl info in the babel struct.

I don't like it either :-(
There is other language info which is currently stored in lyxrc (like
screen_font_encoding and kbmap_primary) which shouldn't be stores there.

> | 4. Start LyX, select the Arabic article class in the document layout popup,
> | and select default input encoding.
> 
> This should also not be needed, the regular article class should
> ideally work.
> 

Agreed again.

Reply via email to