Re: Lyx 2.3.7 maxima

2023-01-10 Thread Dr Eberhard W Lisse
No, I am asking because it might not be working for others if it is not working for me, so I though I'd report it. And have a look at it while I am there). el On 10/01/2023 03:41, Stephan Witt wrote: > Am 09.01.2023 um 23:25 schrieb Dr Eberhard W Lisse : >> >> Hi, >> >> I just saw the

Re: LyX 1.0

2023-01-10 Thread Jean-Marc Lasgouttes
Le 10/01/2023 à 11:23, Patrick Dupre a écrit : Yes, I can share it. Not sure about the exact result ! Hi there, This LyX 1.0 file from Patrick is not readable with current versions. Experiments show that lyx2lyx first complains about a malformed file when converting to LyX 1.4. I do not

Re: Work around AMS book unicode issue?

2023-01-10 Thread Jean-Marc Lasgouttes
Le 10/01/2023 à 03:42, Scott Kostyshak a écrit : The attached patch works around an AMS book unicode issue, as discussed here: https://tex.stackexchange.com/questions/671116/how-to-find-and-fix-the-origin-of-invalid-unicode-character-generated-by-lyx Disadvantage of the workaround is the

Re: LyX 1.0

2023-01-10 Thread José Matos
On Tue, 2023-01-10 at 11:36 +0100, Jean-Marc Lasgouttes wrote: > Le 10/01/2023 à 11:23, Patrick Dupre a écrit : > > Yes, I can share it. > > Not sure about the exact result ! > > Hi there, > > This LyX 1.0 file from Patrick is not readable with current versions. > Experiments show that lyx2lyx

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jürgen Spitzmüller
Am Sonntag, dem 08.01.2023 um 19:49 +0100 schrieb Jean-Marc Lasgouttes: > Is there a reason why we need that instead of comparing dates as > string? > Something like > if (package_date >= "2015/09/01") { > [...] How would "comparing dates as strings" work? Wouldn't we

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jürgen Spitzmüller
Am Dienstag, dem 10.01.2023 um 17:28 +0100 schrieb Jean-Marc Lasgouttes: > Am I wrong that > "2015/10/01" >= "2014/06/01" > ? > > I may be missing something obvious. Maybe I miss something obvious, but I thought strings can only be compared for equality (== or !=) not size difference (unless you

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jean-Marc Lasgouttes
Le 10/01/2023 à 17:26, Jürgen Spitzmüller a écrit : Am Sonntag, dem 08.01.2023 um 19:49 +0100 schrieb Jean-Marc Lasgouttes: Is there a reason why we need that instead of comparing dates as string? Something like if (package_date >= "2015/09/01") { [...] How would

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jürgen Spitzmüller
Am Dienstag, dem 10.01.2023 um 16:08 +0100 schrieb Jean-Marc Lasgouttes: > and in the 'magic' use of \@parse@command in chkconfig.ltx That's a command from the LaTeX kernel that can parse a LaTeX package string, strip the name and anything expect for the date and can also handle different date

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jean-Marc Lasgouttes
We have lexicographic ordering, right? https://en.cppreference.com/w/cpp/string/basic_string/operator_cmp How would we sort strings otherwise? JMarc Le 10 janvier 2023 18:34:15 GMT+01:00, "Jürgen Spitzmüller" a écrit : >Maybe I miss something obvious, but I thought strings can only be

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jean-Marc Lasgouttes
Le 08/01/2023 à 19:49, Jean-Marc Lasgouttes a écrit : For some reason (maybe because I am in C++11 mode) the eatLine() does not grab the potential second part of the line, but the package name in the next line. OK, ignore that. It turns out I had an old version of chkconfig.ltx in my ~/.lyx

Re: Embedded Objects xhtml tests failing due to xmllint

2023-01-10 Thread Thibaut Cuvelier
On Tue, 10 Jan 2023 at 04:11, Scott Kostyshak wrote: > I'll paste the errors at the bottom of this message. Thibaut, is this > related to recent work? > It's highly likely, I'm having a look! -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Beta 2?

2023-01-10 Thread Richard Kimberly Heck
Seem like a good time to do beta 2? Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Work around AMS book unicode issue?

2023-01-10 Thread Scott Kostyshak
On Tue, Jan 10, 2023 at 11:46:08AM +0100, Jean-Marc Lasgouttes wrote: > Le 10/01/2023 à 03:42, Scott Kostyshak a écrit : > > The attached patch works around an AMS book unicode issue, as discussed > > here: > > > > > >

Re: Beta 2?

2023-01-10 Thread Jean-Marc Lasgouttes
Right. Something I will ask for soon is permission for upgrading included boost on devel and stable. It is not possible to build stable without lots of warnings these days. JMarc Le 10 janvier 2023 21:50:06 GMT+01:00, Richard Kimberly Heck a écrit : >Seem like a good time to do beta 2? >

Re: Embedded Objects xhtml tests failing due to xmllint

2023-01-10 Thread Thibaut Cuvelier
On Wed, 11 Jan 2023 at 00:15, Thibaut Cuvelier wrote: > On Tue, 10 Jan 2023 at 04:11, Scott Kostyshak wrote: > >> I'll paste the errors at the bottom of this message. Thibaut, is this >> related to recent work? >> > > It's highly likely, I'm having a look! > That problem should be fixed at

Re: Using lyxhtml_validity.py

2023-01-10 Thread Kornel Benko
Am Wed, 11 Jan 2023 01:12:40 +0100 schrieb Thibaut Cuvelier : > > Still > >         Error: Bad value "content-type" for attribute "http-equiv" on > > element "meta". > > > > Should we ignore this error? > > > I don't think we should ignore it. It really seems to be platform-dependent >

Re: [LyX/master] Improve LaTeX version checking

2023-01-10 Thread Jürgen Spitzmüller
Am Dienstag, dem 10.01.2023 um 20:11 +0100 schrieb Jean-Marc Lasgouttes: > We have lexicographic ordering, right? > https://en.cppreference.com/w/cpp/string/basic_string/operator_cmp > > How would we sort strings otherwise? Oh, I never thought about that. Still, I think the current method is

Re: Using lyxhtml_validity.py

2023-01-10 Thread Kornel Benko
Am Wed, 11 Jan 2023 06:55:11 +0100 schrieb Kornel Benko : > Am Wed, 11 Jan 2023 01:12:40 +0100 > schrieb Thibaut Cuvelier : > > > > Still > > >         Error: Bad value "content-type" for attribute "http-equiv" on > > > element > > > "meta". > > > > > > Should we ignore this error? > > > >