On 2013-04-02, Uwe Stöhr wrote:
> Am 22.03.2013 09:42, schrieb Guenter Milde:

>>>>>> So, maybe for the time being it could be better to just exclude
>>>>>> Kazakh from the "Cyrillic languages" to let the "textcyr" feature
>>>>>> work.

>> With the current state of textcyr, the fix should be far more easy ---
>> change the default latex input encoding to ASCII.

> I don't have much time at the moment, could you please take over?

I can provide a patch, but I am not a developer, so I cannot apply it.

>>> But Kazakh is not supported by polyglossia. I already marked Kazakh as
>>> unsupported by babel _and_ polyglossia.

>> In this case, I'd comment the whole Kazakh section out:

> I was unsure because it seemed that there was a Kazakh babel support
> file available because someone once added Kazakh support to LyX. I
> again tried to google it but cannot find anything. but maybe Kazakh
> users still have it and commenting Kazakh out would break LyX for them
> completely.

I did not find any Babel file for Kazakh. 

However, there is a file "kazakh.def" as part of the montex package
http://www.ctan.org/pkg/montex (an alternative to Babel for Mongolian
LaTeX). (There is a considerable Kazakh minority in Mongolia.)
However, this file seems to be an alias for Xalx.def, it says:

  % Description: Conventional Labels, litteral numbering and date,
  %              given in Modern Mongolian (Xalx)

I agree that removing Kazakh may be break existing documents that work
around the issues. (And it seems a file-format change, so cannot be
reverted soon.)

Until bug 8600 (http://www.lyx.org/trac/ticket/8600) is solved, I propose
the following patch:

--- /usr/local/src/lyx/lib/languages~   2013-03-25 14:47:18.000000000 +0100
+++ /tmp/languages23038.5907    2013-04-03 14:48:20.000000000 +0200
@@ -598,7 +598,7 @@
 # not supported by babel
 Language kazakh
        GuiName         "Kazakh"
-       Encoding        pt154
+       Encoding        ascii
        LangCode        kk_KZ
        PostBabelPreamble
        \input{t2aenc.def}

this should solve cases where Kazakh text parts are used in a non-Cyrillic
document while the PostBabelPreamble is still sensible to prevent unecessary
font switches for punctuation and other ASCII characters in a Kazakh
document using the Cyrillic script.


Günter

Reply via email to