Dov Feldstern schrieb:
Concerning the page: I would not mention the bind file because this is
unnecessary. New users will be scared about every preferences
fiddling. We don't use special bind files for the other languages, and
when the user is experianced enough, he can create any time later its
own bind file.
How do you expect a user to type an English--Arabic document using these
instructions, without a key binding? You don't even mention the
"language" command anywhere, and without that there's no way that it can
work...
I don't understand, writing English and Arabic is like for every other mixed language document. Just
use the character dialog as usual.
And I don't expect a user to do "Alt-X language arabic_arabtex"
every time he wants to switch back and forth between Arabic and English.
So using a binding is the only reasonable way to type mixed documents.
And I think that being able to mix Arabic with English is a pretty basic
requirement...
I haven't said that a bind file is not useful, I just don't would have it in the main install
section but rather in a tipps section at the end. With arabi, language switching is as easy as for
every other language so these users don't need a bind file as requirement. They aslo want perhaps to
have it too, that's why I propose to put in the tips section.
BTW, in Hebrew we do use the key bindings. The fact that it's not
included by default with LyX is unfortunate;
Why then not add a new bind file to LyX's SVN for Hebrew and Arabic?
> As far as I can tell, Arabi support in LyX does not fully work yet.
For me it works much better than than arabtex.
Not for me. I am absolutely unable to generate clean latex directly from
LyX. If I just open a new document, switch its language to
Arabic(arabi), and start typing, I get the following error when
generating latex:
"Package babel Error: You haven't specified a language option."
Not here.
The LyX file and the generated latex are attached.
(1) Does the latex file work for you?
Yes.
(2) Does the LyX file work for you? Is the generated latex the same as
mine?
Yes.
(3) If you follow the same procedure, do you get a LyX file which looks
different than mine?
No, I get exactly what you sent.
> * latex preamble: instead of
"\documentclass[arabic,english]{article}", should be just
> "documentclass{article}"
This is correct. You only get Arabic AND english when you have both
languages in your document.
Yes of course. When I only have Arabic, like in the file you sent, there is correctly only arabic as
option.
You're not paying attention to what I wrote: I don't want either of
them; even just the [arabic] is superfluous here. There shouldn't be
*anything*.
I don't understand, of course there must be arabic when writing Arabic.
> * latex preamble: instead of "\usepackage{babel}", should be
> "\usepackage[arabic,english]{babel}"
This is already the case. We load the babel languages in the class
options.
Again, not for me it isn't. Right now, I believe, the languages are
being inserted in the documentclass command, not in the
\usepackage{babel} command; and for me that's not working, maybe its an
issue of the arabi version, but it's not working.
I also don't understand this, because you can put every package option to the documentclass options
and it works, no matter what package you are using. The the given option is used for all used
LaTeX-packages.
But you already get
\usepackage[T1,LFE,LAE]{fontenc}
when using arabic_arabi.
If the document language is "Arabic(arabi)", then it's fine. But if the
document language is English, then it doesn't get inserted
automatically. But again, this is not crucial right now, as it works
either way.
Of course not, because if you don't use Arabic or Farsi, LFE and LAE are not needed, also not when
using arabTeX.
> * In Tools -> Preferences... -> Look and feel -> Keyboard, make
sure that "Use keyboard map" is
> checked, and then type in @@null@@ as "first", and @@arabic@@ as
"second".
Why not using Arabic directly as the first keyboard map?
Does it work for you that way? It doesn't work for me...
Works fine.
I think that the keymap support is just not built for that kind of
thing. Again, the correct way to do this IMO is to associate a language
with a keymap.
This is not an option because keymaps are only needed when you don't have a keyboard of the language
you will write. I assume that 98% of our users don't need keymaps.
regards Uwe
