Dear Uwe, On 2013-03-18, Uwe Stöhr wrote: > Am 16.03.2013 16:24, schrieb Guenter Milde:
>> Besides try-and error with different Cyrillic-using languages, you can >> also look into Babel's *.ldf files for the respective languages. For >> example russian.ldf comes with code to set the font encoding to one of >> the Cyrillic encodings (OT2, T2A, T2B, T2C, X2). This may be missing in >> some cases - where the user is expected to do this "by hand", usually by >> giving the respective font encoding as last argument to "fontenc". This >> should also be documented in the Babel documentation. > Many thanks for this info. I had a closer look and that Serbian does > not load T2A is because this babel file is designed for Latin Serbian > only - as you already pointed out. For Kazakh there is no babel file > available at all, but a colleague of mine is from Kazakhstan and I > will ask him to create one. Good idea. Maybe we can also find someone for Serbian (Cyrillic). LyX could ship copies until babel-beta becomes mainstream... ... >> LyX assumes Babel to set the correct font encoding for Cyrillic-using >> languages. \textcyr is inserted if you use Cyrillic characters in a >> "non-Cyrillic" language like German or English. >> This still does not solve the issue with Latin script for auto-generated >> strings (Glava for Chapter, etc.). > Yes, but better than having a non-compilable document as this is the > case now. The correct name with Cyrillic letters can be set by the > users in the preamble. So to provide at least a basic Serbian Cyrillic > support, I propose to commit your change, see attached. OK? The "Serbian" fix looks OK (just document the Latin auto-text somewhere). According to wikipedia, the Kasach language can be written in three scripts: Latin, Cyrillic, or Arab. http://de.wikipedia.org/wiki/Kasachische_Sprache#Entwicklung_der_Schriftsprache It would be good to find out where LyX "decides" which Language uses the Cyrillic script. I suppose there is a list in the C-code of the "textcyr" feature. I'd provide both "Kazakh (Latin)" (excluded from the list of Cyrillic-using languages) and "Kazakh (Cyrillic)" (with the caveat that it is currently incompletely supported). There remains the problem that in a non-Kazakh document, the font switch for parts in Kazach is missing (there is no \extraskazakh we could add something to). So, maybe for the time beeing it could be better to just exclude Kazach from the "Cyrillic languages" to let the "textcyr" feature work. >> The new Babel maintainer is open for contributions. >> http://www.ctan.org/pkg/babel-beta/ > Good to know. I thought babel is dead. I know the new babel maintainer > and will contact him to create a Serbian Cyrillic and Kazakh ldf-file. AFAIK, Javier plans to provide the framework and give "language maintenance" into the hands of individual developers. Instead of separate files, I propose "script=latin" vs. "script=cyrillic" switches for both, Serbian and Kazakh (check with Javier, how language options should be defined). Günter
