On Wed, Sep 06, 2023 at 05:58:18PM +0100, José Matos wrote:
> The fix was then simple and also follows attached. Please commit it.
Thanks, José! In master at 77fc67d3.
Scott
signature.asc
Description: PGP signature
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Wed, 2023-09-06 at 07:36 +0100, José Matos wrote:
> So it seems that what should not happen happened. :-)
>
> This means that something unexpected is happening and the code is not
> able to react to it.
My analysis was not entirely correct. :-)
In any case the issue is that function returns
On Tue, 2023-09-05 at 21:07 -0400, Richard Kimberly Heck wrote:
> lyx2lyx warning: An error occurred in 604, at 0x7fe2423d7600>
> Traceback (most recent call last):
> File "/usr/local/share/lyx/lyx2lyx/lyx2lyx", line 97, in
> main()
> File "/usr/local/share/lyx/lyx2lyx/lyx2lyx",
Ideas?
Forwarded Message
Subject:Re: Can't open 2.4.0-beta5 doc in 2.4.0-beta3
Date: Tue, 5 Sep 2023 20:03:16 -0500
From: Christopher Menzel
To: Richard Kimberly Heck
CC: LyX Users
On 5 Sep 2023, at 5:01 PM, Richard Kimberly Heck wrote:
On 9/5/23
On 12/21/22 02:55, Jürgen Spitzmüller wrote:
Am Mittwoch, dem 21.12.2022 um 08:09 +0100 schrieb Jürgen Spitzmüller:
The problem seems to be in the revert_starred_refs method, which
overwrites parts of the surrounding document and thus deletes a plain
layout begin. If you comment out that
On Wed, Dec 21, 2022 at 08:55:18AM +0100, Jürgen Spitzmüller wrote:
> Am Mittwoch, dem 21.12.2022 um 08:09 +0100 schrieb Jürgen Spitzmüller:
> > The problem seems to be in the revert_starred_refs method, which
> > overwrites parts of the surrounding document and thus deletes a plain
> > layout
Am Mittwoch, dem 21.12.2022 um 08:09 +0100 schrieb Jürgen Spitzmüller:
> The problem seems to be in the revert_starred_refs method, which
> overwrites parts of the surrounding document and thus deletes a plain
> layout begin. If you comment out that method, the error disappears.
I think I fixed
Am Montag, dem 19.12.2022 um 16:57 -0500 schrieb Scott Kostyshak:
> The problem is that the code is supposed to append, then pop. then
> append, then pop. There is a mismatch somewhere and the code pops
> without a preceding append, so the list of languages is empty.
The problem seems to be in
On Sun, Dec 11, 2022 at 09:42:33PM +, José Matos wrote:
> On Sun, 2022-12-11 at 15:29 -0500, Scott Kostyshak wrote:
> > convert_hebrew_parentheses
> > elif current_languages[-1] == 'hebrew' and not
> > line.startswith('\\'):
> > IndexError: list index out of range
>
> This happens only
On Sun, 2022-12-11 at 15:29 -0500, Scott Kostyshak wrote:
> convert_hebrew_parentheses
> elif current_languages[-1] == 'hebrew' and not
> line.startswith('\\'):
> IndexError: list index out of range
This happens only when current_languages is an empty list:
In [1]: [][-1]
On current master, for the Russian UserGuide, I get:
$ lyx -e lyx23x UserGuide.lyx
starting local cmake binary for lyx
lyx2lyx warning: An error occurred in 565,
Traceback (most recent call last):
File "/home/scott/lyxbuilds/master-master/repo/lib/lyx2lyx/lyx2lyx", line 97,
in
main()
On Sun, Dec 11, 2022 at 12:13:28PM +0100, Enrico Forestieri wrote:
> On Sun, Dec 11, 2022 at 12:06:34AM +0100, Yuriy Skalko wrote:
> >
> > And opening such file with non-existing version in LyX (master, Win10)
> > gives that old message:
> >
> > is from a newer version of LyX and the lyx2lyx
On 12/11/22 06:13, Enrico Forestieri wrote:
On Sun, Dec 11, 2022 at 12:06:34AM +0100, Yuriy Skalko wrote:
And opening such file with non-existing version in LyX (master,
Win10) gives that old message:
is from a newer version of LyX and the lyx2lyx script failed
to convert it.
Yes, this
On Sun, Dec 11, 2022 at 12:06:34AM +0100, Yuriy Skalko wrote:
And opening such file with non-existing version in LyX (master, Win10)
gives that old message:
is from a newer version of LyX and the lyx2lyx script failed to
convert it.
Yes, this is true for the Windows version. The problem
And opening such file with non-existing version in LyX (master, Win10)
gives that old message:
is from a newer version of LyX and the lyx2lyx script failed to
convert it.
Yuriy
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 10.12.2022 15:22, Scott Kostyshak wrote:
If you open a new .lyx file than the lyx2lyx version can handle we used to get:
is from a newer version of LyX and the lyx2lyx script failed to
convert it.
Now we get:
is not a readable LyX document.
You can test this by just manually
On 12/10/22 09:22, Scott Kostyshak wrote:
If you open a new .lyx file than the lyx2lyx version can handle we used to get:
is from a newer version of LyX and the lyx2lyx script failed to
convert it.
Now we get:
is not a readable LyX document.
You can test this by just manually
If you open a new .lyx file than the lyx2lyx version can handle we used to get:
is from a newer version of LyX and the lyx2lyx script failed to
convert it.
Now we get:
is not a readable LyX document.
You can test this by just manually incremending the number in the first
line of a .lyx
e missing glyphs.
> >
> >
> > It took some more time to find out that I can reproduce Scott's findings
> > setting a higher version number:
> >
> > --- a/lib/examples/ko/Welcome.lyx
> > +++ b/lib/examples/ko/Welcome.lyx
> > @@ -1,5 +1,5 @@
&g
higher version number:
>
> --- a/lib/examples/ko/Welcome.lyx
> +++ b/lib/examples/ko/Welcome.lyx
> @@ -1,5 +1,5 @@
> #LyX 2.4 created this file. For more info see https://www.lyx.org/
> -\lyxformat 575
> +\lyxformat 576
>\begin_document
>\b
s://www.lyx.org/
-\lyxformat 575
+\lyxformat 576
\begin_document
\begin_header
Now, the re-created "Welcome.23-after.lyx" and "Welcome.23-before.lyx"
differed and "Welcome.23-before.lyx" compiled fine while
"Welcome.23-after.lyx" failed
On Sun, Mar 01, 2020 at 09:43:52PM -, Guenter Milde wrote:
> On 2020-02-23, Scott Kostyshak wrote:
> > On Fri, Feb 21, 2020 at 11:26:08AM -0500, Scott Kostyshak wrote:
> >> The following tests are failing on master:
>
> >> export/examples/ko/Welcome_lyx22 (Failed)
> >>
On 2020-02-23, Scott Kostyshak wrote:
> On Fri, Feb 21, 2020 at 11:26:08AM -0500, Scott Kostyshak wrote:
>> The following tests are failing on master:
>> export/examples/ko/Welcome_lyx22 (Failed)
>> export/examples/ko/Welcome_lyx23 (Failed)
>> To reproduce manually, export Welcome.lyx in
On 2020-02-23, Scott Kostyshak wrote:
> On Fri, Feb 21, 2020 at 11:26:08AM -0500, Scott Kostyshak wrote:
>> The following tests are failing on master:
>> export/examples/ko/Welcome_lyx22 (Failed)
>> export/examples/ko/Welcome_lyx23 (Failed)
>> To reproduce manually, export Welcome.lyx in
On Fri, Feb 21, 2020 at 11:26:08AM -0500, Scott Kostyshak wrote:
> The following tests are failing on master:
>
> export/examples/ko/Welcome_lyx22 (Failed)
> export/examples/ko/Welcome_lyx23 (Failed)
>
> To reproduce manually, export Welcome.lyx in mater to LyX 2.3.x format.
> Then open the
The following tests are failing on master:
export/examples/ko/Welcome_lyx22 (Failed)
export/examples/ko/Welcome_lyx23 (Failed)
To reproduce manually, export Welcome.lyx in mater to LyX 2.3.x format.
Then open the created file either with master or 2.3.x and compile with
the default format
Am Samstag, den 31.08.2019, 11:21 +0200 schrieb Jürgen Spitzmüller:
> However, it seems that
> revert_languages (which is called here) misses some languages in
> Branches.
I think this is by design, since the missed ones were polyglossia-only
and we had also babel-only languages.
Jürgen
On Sat, Aug 31, 2019 at 11:21:36AM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, den 30.08.2019, 21:24 -0400 schrieb Scott Kostyshak:
> > I get the following error when trying to export supported-
> > languages.lyx
> > to 2.3.x format:
> >
> > $ lyx -e lyx23x
Am Freitag, den 30.08.2019, 21:24 -0400 schrieb Scott Kostyshak:
> I get the following error when trying to export supported-
> languages.lyx
> to 2.3.x format:
>
> $ lyx -e lyx23x autotests/export/latex/languages/supported-
> languages.lyx
> Warning: An error ocurred in 575,
I get the following error when trying to export supported-languages.lyx
to 2.3.x format:
$ lyx -e lyx23x autotests/export/latex/languages/supported-languages.lyx
Warning: An error ocurred in 575,
Traceback (most recent call last):
File
Am Mittwoch, den 12.09.2018, 10:27 +0200 schrieb Kornel Benko:
> Try
> # lyx2lyx -V 1.6 autotests/export/lyx2lyx/lyx_2_1_test.lyx |
> lyx2lyx
> Warning: Lyx2lyx knows nothing about module 'graphicboxes'.
> Please check if short title insets have been converted correctly.
>
Try
# lyx2lyx -V 1.6 autotests/export/lyx2lyx/lyx_2_1_test.lyx | lyx2lyx
Warning: Lyx2lyx knows nothing about module 'graphicboxes'. Please
check if short title insets have been converted correctly.
Warning: Lyx2lyx knows nothing about module 'bicaption'. Please check
if
Am Samstag, 4. August 2018 12:51:19 CEST schrieb Enrico Forestieri
:
> On Thu, Aug 02, 2018 at 10:54:47PM +0200, Kornel Benko wrote:
> > Am Mittwoch, 1. August 2018 20:10:38 CEST schrieb Kornel Benko
> > :
> > > Am Mittwoch, 1. August 2018 19:26:15 CEST schrieb Enrico Forestieri
> > > :
> > > >
On Thu, Aug 02, 2018 at 10:54:47PM +0200, Kornel Benko wrote:
> Am Mittwoch, 1. August 2018 20:10:38 CEST schrieb Kornel Benko
> :
> > Am Mittwoch, 1. August 2018 19:26:15 CEST schrieb Enrico Forestieri
> > :
> > > It is not possible loading the attached document with current master
> > >
Am Mittwoch, 1. August 2018 20:10:38 CEST schrieb Kornel Benko :
> Am Mittwoch, 1. August 2018 19:26:15 CEST schrieb Enrico Forestieri
> :
> > It is not possible loading the attached document with current master
> > because lyx2lyx fails with the following error:
> >
> > Warning: An error
Am Mittwoch, 1. August 2018 19:26:15 CEST schrieb Enrico Forestieri
:
> It is not possible loading the attached document with current master
> because lyx2lyx fails with the following error:
>
> Warning: An error ocurred in 482,
> Traceback (most recent call last):
> File
It is not possible loading the attached document with current master
because lyx2lyx fails with the following error:
Warning: An error ocurred in 482,
Traceback (most recent call last):
File "/usr/local/src/lyx/lyx-devel/lib/lyx2lyx/lyx2lyx", line 96, in
main()
File
Am Freitag, 27. April 2018 12:39:12 CEST schrieb Kornel Benko :
> This looks again like language nesting problem ...
> Open autotests/export/lyx2lyx/lyx_2_1_test.lyx
> Try to compile ...
> ...
> ! Missing \endcsname inserted.
>
> \protect
> l.55 ...oreignlanguage{english}{-60}}{
This looks again like language nesting problem ...
Open autotests/export/lyx2lyx/lyx_2_1_test.lyx
Try to compile ...
...
! Missing \endcsname inserted.
\protect
l.55 ...oreignlanguage{english}{-60}}{ with rotated}
The control sequence marked
Am Sonntag, den 08.01.2017, 12:02 -0500 schrieb Scott Kostyshak:
> > I can try to fix this at the lyx2lyx level once I am out of the
> > biblatex tunnel.
>
> OK.
Well, it turned out to be a pretty stupid typo of mine.
Should be cured now.
Jürgen
>
> Scott
signature.asc
Description: This is
On Sun, Jan 08, 2017 at 04:38:12PM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, den 08.01.2017, 10:24 -0500 schrieb Scott Kostyshak:
> > OK then I guess we should invert the tests (and perhaps continue the
> > debate in a bug report). The other possibility is the change the
> > regex
> > that
Am Sonntag, den 08.01.2017, 10:24 -0500 schrieb Scott Kostyshak:
> OK then I guess we should invert the tests (and perhaps continue the
> debate in a bug report). The other possibility is the change the
> regex
> that checks for lyx2lyx errors to ignore these ones but that doesn't
> seem like a
On Sun, Jan 08, 2017 at 04:09:41PM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, den 08.01.2017, 09:24 -0500 schrieb Scott Kostyshak:
> > > I'd prefer to convert them to the respective Unicode characters and
> > > do the
> > > replacement as preamble fallback macro definition.
> >
> > Is there
Am Sonntag, den 08.01.2017, 09:24 -0500 schrieb Scott Kostyshak:
> > I'd prefer to convert them to the respective Unicode characters and
> > do the
> > replacement as preamble fallback macro definition.
>
> Is there agreement this is the right thing to do?
No.
Jürgen
>
> Scott
signature.asc
On Sat, Dec 31, 2016 at 02:02:19PM +, Guenter Milde wrote:
> >> Is this a concern or should it be ignored?
>
> > Can be ignored IMHO.
>
> I'd prefer to convert them to the respective Unicode characters and do the
> replacement as preamble fallback macro definition.
Is there agreement this
On 2016-12-31, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Samstag, den 31.12.2016, 06:41 -0500 schrieb Scott Kostyshak:
>> $ lyx master -e lyx22x UserGuide.lyx
>> $ lyx master -e lyx22x UserGuide.22.lyx
>> unusual contents found: [formula simple [grid
Am Samstag, den 31.12.2016, 06:41 -0500 schrieb Scott Kostyshak:
> $ lyx master -e lyx22x UserGuide.lyx
> $ lyx master -e lyx22x UserGuide.22.lyx
> unusual contents found: [formula simple [grid [row [cell [symbol
> langle][kern -2.5pt][symbol langle] [formula simple [grid [row
> [cell
>
See the following:
$ lyx master -e lyx22x UserGuide.lyx
$ lyx master -e lyx22x UserGuide.22.lyx
unusual contents found: [formula simple [grid [row [cell [symbol langle][kern
-2.5pt][symbol langle] [formula simple [grid [row [cell
unusual contents found: [formula simple [grid [row
On 05/18/2014 07:56 PM, Richard Heck wrote:
On 05/18/2014 06:48 PM, Scott Kostyshak wrote:
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error Buffer... ended
unexpectedly, which means
On 05/18/2014 07:56 PM, Richard Heck wrote:
On 05/18/2014 06:48 PM, Scott Kostyshak wrote:
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error "Buffer... ended
unexpectedly, which means
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error Buffer... ended
unexpectedly, which means that it is probably corrupted.
There was also a warning
Warning: Can't find end of second ERT!!
On 05/18/2014 06:48 PM, Scott Kostyshak wrote:
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error Buffer... ended
unexpectedly, which means that it is probably corrupted.
There was also
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error "Buffer... ended
unexpectedly, which means that it is probably corrupted."
There was also a warning
"Warning: Can't find end of second
On 05/18/2014 06:48 PM, Scott Kostyshak wrote:
I'm not sure if this is a known issue or not.
If in LyX 2.2git I export beamerlyxexample1.lyx to 2.0.x format and
then reopen it in LyX 2.2git, I get an error "Buffer... ended
unexpectedly, which means that it is probably corrupted."
There was
On 08/26/2009 03:24 PM, Vincent van Ravesteijn wrote:
Steve Litt schreef:
OK, I've researched it a little more, and during the lyx --export
latex, LyX is converting a LyX idx inset containing chapter 2|(
without the quotes to the following LaTeX:
\index{chapter 2|(@chapter 2\textbar{}(}
The
rgheck schreef:
On 08/26/2009 03:24 PM, Vincent van Ravesteijn wrote:
Steve Litt schreef:
OK, I've researched it a little more, and during the lyx --export
latex, LyX is converting a LyX idx inset containing chapter 2|(
without the quotes to the following LaTeX:
\index{chapter 2|(@chapter
I already tried saving it as 1.5.x file and reimporting it in 1.6.x,
no problems whatsoever, besides Steve said he only has 1.6.3 and he
could create a new example from scratch.
Maybe something with default fontencoding in stead of T1 or
something... ?!?
Vincent
Steve,
What's your
On 08/26/2009 03:24 PM, Vincent van Ravesteijn wrote:
Steve Litt schreef:
OK, I've researched it a little more, and during the lyx --export
latex, LyX is converting a LyX idx inset containing "chapter 2|("
without the quotes to the following LaTeX:
\index{chapter 2|(@chapter 2\textbar{}(}
rgheck schreef:
On 08/26/2009 03:24 PM, Vincent van Ravesteijn wrote:
Steve Litt schreef:
OK, I've researched it a little more, and during the lyx --export
latex, LyX is converting a LyX idx inset containing "chapter 2|("
without the quotes to the following LaTeX:
\index{chapter 2|(@chapter
I already tried saving it as 1.5.x file and reimporting it in 1.6.x,
no problems whatsoever, besides Steve said he only has 1.6.3 and he
could create a new example from scratch.
Maybe something with default fontencoding in stead of T1 or
something... ?!?
Vincent
Steve,
What's your
Hi,
some of my old lyx-files cannot be read by the newest lyx.
lyx2lys tries to convert to 325-format, which leads to an error.
Trying manually to convert with lyx2lyx, it was ok up to the 310 -format, e.g.:
python -tt '/usr/local/share/lyx1.6/lyx2lyx/lyx2lyx' -t 310 -o xx.lyx
On Wednesday 02 April 2008 12:49:37 Kornel Benko wrote:
Hi,
some of my old lyx-files cannot be read by the newest lyx.
lyx2lys tries to convert to 325-format, which leads to an error.
Trying manually to convert with lyx2lyx, it was ok up to the 310 -format,
e.g.: python -tt
Hi,
some of my old lyx-files cannot be read by the newest lyx.
lyx2lys tries to convert to 325-format, which leads to an error.
Trying manually to convert with lyx2lyx, it was ok up to the 310 -format, e.g.:
python -tt '/usr/local/share/lyx1.6/lyx2lyx/lyx2lyx' -t 310 -o xx.lyx
On Wednesday 02 April 2008 12:49:37 Kornel Benko wrote:
> Hi,
> some of my old lyx-files cannot be read by the newest lyx.
>
> lyx2lys tries to convert to 325-format, which leads to an error.
>
> Trying manually to convert with lyx2lyx, it was ok up to the 310 -format,
> e.g.: python -tt
64 matches
Mail list logo