Re: Bug in language conversion ?
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 have a > problem > with this idea of inheritance. At least, it should work as it does > for fonts. Note that I am just talking about a change of language here, not general inheritance. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Bug in language conversion ?
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 inherit language changes from selections. Do inset inherit language from outside world? I think we have a problem with this idea of inheritance. At least, it should work as it does for fonts. JMarc -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Bug in language conversion ?
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 also there on top level. For any multilingual passage one could wish to only change one language to another one, not all. But that's maybe rationale for a dedicated lfun. In practice, I am more often annoyed by the fact that language changes do not make it into insets than I would probably be by such special cases. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Bug in language conversion ?
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 undesirable? -- José Abílio -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Bug in language conversion ?
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 :
>
> Missing \endscname inserted
>
> because of the \foreignlanguage{} encapsulating the argument of the
> optional
> command.
>
> 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 inherit language changes from
selections.
--
Jürgen
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Bug in language conversion ?
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{} encapsulating the argument of the optional
command.
This happens also at other places, where optional arguments are not translated.
I can provide a more complete record about Additional.
--
Jean-Pierre
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
