On Fri, Sep 16, 2022 at 10:48 AM Jean-Marc Lasgouttes <lasgout...@lyx.org>
wrote:
>
> Le 14/09/2022 à 19:16, Csikos Bela a écrit :
> > Hello:
> >
> > I have an old document I made in lyx 2.0. Lyx 2.3.6.1 opens is but
> > interprets the code incorrectly and gives compilation error:
>
> Hello,
>
> Could you please create a ticket in trac? I can confirm that the file
> does not typeset in 2.4.0dev either.
>
> JMarc
Hi,
It seems that the problem, in this case, comes from the fact that argument
insets do not inherit the language settings of the layout, so lyx adds
"\foreignlanguage{english}" to the argument in the latex code, and enumitem
does not recognize it as a key. See the difference in the output tex files:
> > In lyx 2.0 the latex code is:
> >
> > \selectlanguage{magyar}%
> > \begin{enumerate}[nosep]
> > \inputencoding{latin2}%
> > \item Első item.\inputencoding{latin9}\foreignlanguage{english}{}\\
> > \foreignlanguage{english}{First item. }\selectlanguage{english}%
> > \end{enumerate}
> >
> > Opening the file in lyx 2.3.6.1 latex code is:
> >
> > \selectlanguage{magyar}%
> > \begin{enumerate}[\foreignlanguage{english}{nosep}]
> > \inputencoding{latin2}%
> > \item Első item.\inputencoding{latin9}\foreignlanguage{english}{}\\
> > \foreignlanguage{english}{First item. }\selectlanguage{english}%
> > \end{enumerate}
But, even if argument insets would inherit language settings, if i would
use a language that does not use the latin letters, such as hebrew, arabic,
etc., I would have to switch to english in the argument inset, and lyx
would add some language code to handle this.
Because of that, I think the proper solution would be to add to the
argument insets the PassThru tag, which will inforce lyx to not change what
written in the argument (this is especially important when using key-value
syntax, as in this case).
I've also mentioned a similar problem, regarding the Named Theorems module,
here <https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg218062.html>.
After setting the PassThru tag to true, it solved the problem.
It might be wise to check if this problem occurs in other modules.
Best Regards,
Udi
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
