> Second we should weight the pros and cons of design decisions we take. That
> is why the discussion in the mailing list is important, the first and
> quickest solution generally is not the best, the process is iterative.
Of course but nobody replied to this topic and your first statement was: Commit
it.
In the last 4 days I had a long discussion with Georg about this and he helped me a lot to make the
patch better although his general reluctance to these supports.
> Are there any quirks in the support for Armenian? If there are please
> document that somewhere so that we can point people to the right place.
The only quirk is a minor one: Armenian is called with the babel language option "English" as there
is no Armenian babel support yet. The also loaded Armtex-package does later the job of babel. So
calling babel doesn't harm, I also found documents in the web were they did the same, but babel is
not really needed. Georg therefore implemented in his patch for bug 3043 a method that babel must
not be called. I'm working to get this part of the patch working but there is an entry in lyxrc.cpp
that makes babel loading in any case.
I documented the babel call in lib/languages.
So the current solution with calling babel with english doesn't harm but to be perfect, babel
needn't to be called.
(This is the same as for the CJK languages support btw..)
regards Uwe
