Am Donnerstag, den 28.03.2019, 17:51 +0000 schrieb Guenter Milde: > Changing the default input encodings in "lib/languages" creates a > backwards-incompatibility that cannot be solved for some documents. > > A lyx2lyx conversion (as outlined in > https://www.lyx.org/trac/ticket/11115#comment:16) will break > documents > with text parts in Japanese, Chinese, Korean, Arab, or Farsi and > "\inputencoding auto", because > > a) the setting "\inputencoding auto" has two components: > > * use the encoding as specified in "lib/languages" as main > encoding > > * switch the input encoding for text parts in different languages,
Please provide an example file for this. I am sure this can be fixed in a clean way. In any case, giving up the Encoding option in languages is not an option. > b) these languages are only supported with a "native" fixed-8-bit > encoding or utf8. Don't understand. > What are the benefits of changing default encodings in > lib/languages over changing "\inputencoding" in templates and > examples? Changing the templates only helps people who use templates. Many users don't (I don't use templates, for instance, except for my own ones). And many also don't have a defaults.lyx template you could change. So with your solution a significant group of users will stick with 8bit encodings forever. IMHO changing the languages definition is the only proper way to go. Fiddling with templates encoding is just finger-painting and a half baked solution. I have this on my agenda, and I will definitely go on to change languages for 2.4.0, so be aware that all work you do on templates might be wasted time. Jürgen > > > Günter >
signature.asc
Description: This is a digitally signed message part
