Martin Vermeer wrote:

Hmmm. Actually this is straightforwardly fixable. It's just a policy
choice, how we understand noFontChange(). See attached. Only text.C and
rowpainter.C were changed. Works for me... 1.3 does it this way too (in
fact, it has *only* noFontChange-type insets; but language is inherited
into all of them. So I guess this is a regression fix.)
Excellent! Applying a language over a selection now takes effect inside
all sorts of insets. I am running out of language complaints. ;-)
The only inset not affected is ERT, but that is as expected.

I also tested that pasting insets into a region with different
language doesn't change language inside the inset.

Language and language changes are now they way they should be.

Helge Hafting

Reply via email to