On 2010-11-15, Guenter Milde wrote: > On 2010-11-15, Jürgen Spitzmüller wrote:
>> Maybe. Don't know. I think I would prefer them to be enabled with >> German (I always use them quite excessively). But then, I have not yet >> used polyglossia myself. >>> However, in any case might it be better to provide a PolyglossiaOpts >>> keyword, even if it is not used in the first version of the new file... >> I guess we should go for the PolyglossiaOpts right away. Done. Some comments: * Does # InternalEncoding <true|false> relate to a font-encoding switch with Babel? 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). * 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.) * 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. Günter
