Guenter Milde wrote: > Done. Great. Could you send the file?
> Some comments: > > * Does > > # InternalEncoding <true|false> > > relate to a font-encoding switch with Babel? yes. > Then it should be true also for e.g. languages with cyrillic script > (even if T2A - T2C are standard font encodings, the font-encoding > switch is hard-coded in Babel and interferes with XeTeX/LuaTeX). This bool is currently (only) used in Paragraph::Private::latexSpecialChar to avoid the use of latexSpecialT1 when such a language is used within a T1- encoded document. It cures some bug, but I do not remember right now which one. It might be that we need to add some more languages, yes. But we will have to re-check first if it really is necessary. > * Encoding <default_encoding> (not with XeTeX/LuaTeX) > > is the default of the LaTeX source (for LaTeX the "input encoding"). > The keyword name should reflect this (in our Unicode-times) rather > restricted meaning. (I prefer utf-8 as default LaTeX input encoding > if the users locale indicates utf-8 is in use on the system, but this > is yet another change.) I'm not sure I understand you here. The encoding is not the default, it is used whenever we switch to said language. And for classic LaTeX, I thing we should stick with these encodings for now. I don't consider inputenc's utf8 support mature enough. > * Language codes: > > the "best current practice" for language codes on the Web advises to > use country codes only if necessary to disambiguate. > http://www.rfc-editor.org/rfc/bcp/bcp47.txt > http://www.w3.org/International/articles/language-tags/ > > I suggest to drop the country codes whenever the default variant of a > language is used. I'm not sure. We need these codes, amongst others, for the spellchecker and the thesaurus. Changing the codes right now could break working things. As said, I do not want to change more than necessary at this point of the development cycle. Refinements can be done for LyX 2.1. > Günter Jürgen