Am Mittwoch, dem 17.04.2024 um 23:31 +0200 schrieb Jean-Marc
Lasgouttes:
> > I wouldn't rate it a bug, but I also would prefer if insets
> > (generally,
> > not only in the case here) would inherit language changes from
> > selections.
>
> Do inset inherit language from outside world? I think we
Le 12/04/2024 à 13:57, Jürgen Spitzmüller a écrit :
This happens also at other places, where optional arguments are not
translated.
I can provide a more complete record about Additional.
I wouldn't rate it a bug, but I also would prefer if insets (generally,
not only in the case here) would
Am Freitag, dem 12.04.2024 um 17:10 +0100 schrieb José Matos:
> In principle I agree with you.
> Is there a counter example where this is undesirable?
Theoretically I can think of cases where one uses, for instance, info
insets in a specific language that should not be changed. But this case
is
On Fri, 2024-04-12 at 13:57 +0200, Jürgen Spitzmüller wrote:
> I wouldn't rate it a bug, but I also would prefer if insets
> (generally, not only in the case here) would inherit language changes
> from selections.
In principle I agree with you.
Is there a counter example where this is
Am Donnerstag, dem 11.04.2024 um 11:18 +0200 schrieb Jean-Pierre
Chrétien:
> When I select section 4.10.1.1 in the French copy of Additional.lyx
> and convert
> it to French, I see that the optional argument of the list items
> remain
> untranslated. This trigger compilation errors like :
>
>
Dear Developers
When I select section 4.10.1.1 in the French copy of Additional.lyx and convert
it to French, I see that the optional argument of the list items remain
untranslated. This trigger compilation errors like :
Missing \endscname inserted
because of the \foreignlanguage{}
