Le 19/07/2019 à 18:34, Jürgen Spitzmüller a écrit :
I am not sure I can follow, but it would not be good if it would not be
aware of language varieties. This is probably a general problem with
the approach: if I have selected to write a document in Austrian German
(de_AT), I would not want LyX to force German German (de_DE) on me,
even if my keyboard would be setup as de_DE.
This is exactly what the feature does. It tries first to switch to a
language among those use in the document.
If I keep that, I may have to rewrite getLanguage which causes
performance issues in my testing. It should be integrated into
updateBuffer anyway (and toc backend should too, bu this is a
different
story).
Actually, my problem was not getLanguages, but having the Code pane
open... I think the current implementation works for now.
JMarc
