Am Montag, 30. Januar 2006 17:20 schrieb Martin Vermeer:
> However, if I have the language inheritance code included in
> applyOuterFont, i.e.:
> 
>       if (font.language() == bufferFont().language())
>                 font.setLanguage(font_.language());
> 
> then you cannot truthfully present buffer language text inside a
> non-buffer-language inset, even if the loaded file contains such.
> Precisely the problem I mentioned earlier. For some unfathomable reason,
> 1.3 doesn't have this problem. I would say, leave this code out.

If I understand you correctly the workaround is to explicitly set the 
language in the inset (and you seem to do it in the patch), so I don't 
see this as a big problem.

> It appears that that is not easily possible, for the above reason. I
> would prefer 1.4 to fully honour existing 1.3 files, even if that means
> that the user-visible behaviour changes slightly. It's illusory, after
> the major rewriting that has happened, to precisely duplicate 1.3
> behaviour anyway.

I agree. If you ask me, your latest patch should go in.


Georg

Reply via email to