>>>>> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>> swedish if the inset is one with noFontChange() == true, else
>> norwegian. At least I think that it works like that.
Martin> Yes, that's how I think it *ought* to work. What else is
Martin> noFontChange for.
If I may object, noFontChange has not be designed for that at all :)
Originally, it was just supposed to tell that you could not put the
inset latex code into a \textbf{}, for example (imagine a figure float
with a paragraph break in there). It was just supposed to describe
LaTeX output peculiarities. Now it has grown into something else, but
I am not sure what.
Martin> A more serious problem: we do not have an inherit_language. I
Martin> think we should. In LyX as it is in CVS, default_language
Martin> plays this role. With the proposed patch, the role is taken
Martin> over by the buffer language, which is better, but in a way
Martin> just as inappropriate. The roles of buffer language and
Martin> "no-defined-language flag" are mixed up.
Dekel Tsur has always fought against an inherit_language value, on the
ground that a text does have a language and is not supposed to inherit
anything when you do some cut-and-paste. I can see some value in the
argument, but it causes many problems.
JMarc
