Re: pdf (lua) of a lyx document

Am Freitag, dem 04.02.2022 um 11:22 +0100 schrieb Wolfgang Engelmann via lyx-users: > Jürgen, I did send the document to Jean-Marc privately because of its > size on 2 Feb 2022 17:50 > Should I send it to you too? Yes, please. Jürgen signature.asc Description: This is a digitally signed

Re: pdf (lua) of a lyx document

Am Freitag, dem 04.02.2022 um 11:23 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: > I missed this test indeed. But what about line 1772 of > output_latex.cpp? I missed this occurrence. Yes, here the test seems to be missing. Is this the place Wolfgang's test file points to? Jürgen

Re: pdf (lua) of a lyx document

Le 04/02/2022 à 11:30, Jürgen Spitzmüller via lyx-users a écrit : Am Freitag, dem 04.02.2022 um 11:23 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: I missed this test indeed. But what about line 1772 of output_latex.cpp? I missed this occurrence. Yes, here the test seems to be missing.

Re: pdf (lua) of a lyx document

Am Mittwoch, dem 02.02.2022 um 16:47 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: > The place where this pop() method is used (popLanguageName) is > related to our use of nested languages. And indeed, it does not check > that some language has been saved before pop-ing it. But we check

Re: pdf (lua) of a lyx document

Le 04/02/2022 à 10:02, Jürgen Spitzmüller via lyx-users a écrit : Am Mittwoch, dem 02.02.2022 um 16:47 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: The place where this pop() method is used (popLanguageName) is related to our use of nested languages. And indeed, it does not check that some

Re: pdf (lua) of a lyx document

Am 04.02.22 um 10:02 schrieb Jürgen Spitzmüller via lyx-users: Am Mittwoch, dem 02.02.2022 um 16:47 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: The place where this pop() method is used (popLanguageName) is related to our use of nested languages. And indeed, it does not check that some

Re: pdf (lua) of a lyx document

Am Freitag, dem 04.02.2022 um 11:23 +0100 schrieb Jean-Marc Lasgouttes via lyx-users: > I see also Font::latexWriteEndChanges and Paragraph.cpp:2808 that are > not very clear. And these one should be audited, too. Jürgen signature.asc Description: This is a digitally signed message part --

Re: pdf (lua) of a lyx document

Am Freitag, dem 04.02.2022 um 11:30 +0100 schrieb Jürgen Spitzmüller via lyx-users: > Am Freitag, dem 04.02.2022 um 11:23 +0100 schrieb Jean-Marc > Lasgouttes > via lyx-users: > > I missed this test indeed. But what about line 1772 of > > output_latex.cpp? > > I missed this occurrence. Yes, here

Re: pdf (lua) of a lyx document

Le 04/02/2022 à 11:22, Wolfgang Engelmann via lyx-users a écrit : Jürgen, I did send the document to Jean-Marc privately because of its size on 2 Feb 2022 17:50 Should I send it to you too? Wolfgang, I am very sorry, but I cannot find this message of yours. Anyway, the best is indeed that

Re: pdf (lua) of a lyx document

Am Freitag, dem 04.02.2022 um 17:27 +0100 schrieb Jürgen Spitzmüller via lyx-users: > However, Wolfgang's file reveals more language nesting problems which > I need to tackle. Actually, the other problems seem to be related to problems in the complex setup. So from LyX's side, the issue seems

question about "itemize"

Suppose I have an itemized list like    paragraph 1   - paragraph 2    paragraph 3 where paragraph 2 is nested. If I enter this by choosing the "itemize" environment, then typing paragraph 1 paragraph 2 paragraph 3 LyX creates paragraph 3 as a new item. Is there a way to have