Re: lyx2lyx bug in 2.x -> 1.6.x

On Sat, Jan 07, 2023 at 11:39:20AM -0500, Richard Kimberly Heck wrote: > On 1/6/23 14:02, Jürgen Spitzmüller wrote: > > Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly > > Heck: > > > And not that it matters, but git blame makes it look like I'm the one > > > who forgot this.

Re: lyx2lyx bug in 2.x -> 1.6.x

On 1/6/23 14:02, Jürgen Spitzmüller wrote: Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly Heck: And not that it matters, but git blame makes it look like I'm the one who forgot this. I'm not. I know. A closer look at the logs revealed tat you just fixed up the method. I

Re: lyx2lyx bug in 2.x -> 1.6.x

Am Freitag, dem 06.01.2023 um 13:51 -0500 schrieb Richard Kimberly Heck: > And not that it matters, but git blame makes it look like I'm the one > who forgot this. I'm not. I know. A closer look at the logs revealed tat you just fixed up the method. -- Jürgen -- lyx-devel mailing list

Re: lyx2lyx bug in 2.x -> 1.6.x

On 1/6/23 13:39, Richard Kimberly Heck wrote: On 1/6/23 08:41, Jürgen Spitzmüller wrote: Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller: A revert routine is missing that removes the newpage inset before such bibtex insets (in the formats before, a clear(double)page is

Re: lyx2lyx bug in 2.x -> 1.6.x

On 1/6/23 08:41, Jürgen Spitzmüller wrote: Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller: A revert routine is missing that removes the newpage inset before such bibtex insets (in the formats before, a clear(double)page is part of the code the bibtex insert generates.

Re: lyx2lyx bug in 2.x -> 1.6.x

Am Freitag, dem 06.01.2023 um 13:03 +0100 schrieb Jürgen Spitzmüller: > A revert routine is missing that removes the newpage inset before > such bibtex insets (in the formats before, a clear(double)page is > part of the code the bibtex insert generates. Added at d89a48483e3906. -- Jürgen

Re: lyx2lyx bug in 2.x -> 1.6.x

Am Donnerstag, dem 05.01.2023 um 23:45 -0500 schrieb Scott Kostyshak: > If convert_bibtex_clearpage(document) in lyx_2_0.py is commented out, > then the issue goes away (just to give an idea of where the bug is). A revert routine is missing that removes the newpage inset before such bibtex insets

lyx2lyx bug in 2.x -> 1.6.x

There is a minor issue in an old lyx2lyx routine in lyx_2_0.py that I describe below. If we do multiple roundtrips with KOMA-Script_Book.lyx back to the format used for LyX 1.6.x, there is no convergence. If I do the following command: lyx -e lyx16x KOMA-Script_Book.lyx && lyx -e lyx16x

Re: lyx2lyx bug: duplicating some lyx properties

On Sunday, January 03, 2016 04:32:49 AM Scott Kostyshak wrote: > Hopefully we can make progress on unit tests in the 2.3 cycle, for both > lyx2lyx and our C++ code and anything else. I would be happy to > eventually learn the testing framework and try to contribute. +1 I wholeheartedly agree

Re: lyx2lyx bug: duplicating some lyx properties

On Sun, Jan 03, 2016 at 10:24:47AM +0100, Georg Baum wrote: > Scott Kostyshak wrote: > > > On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote: > >> > >> What we have now is _one_ step in this direction. > > > > Dedicated tests requires understanding of the underlying mechanism. I do >

Re: lyx2lyx bug: duplicating some lyx properties

Scott Kostyshak wrote: > On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote: >> >> What we have now is _one_ step in this direction. > > Dedicated tests requires understanding of the underlying mechanism. I do > not know much at all about lyx2lyx (I'm not sure Kornel does either?). I

Re: lyx2lyx bug: duplicating some lyx properties

On Fri, Jan 01, 2016 at 01:22:53PM +0100, Kornel Benko wrote: > Am Donnerstag, 31. Dezember 2015 um 19:33:59, schrieb Georg Baum > > > This is not a bug. The conversion 501->500 must be lossy, since the format Thanks for the explanation. Good to know there is

Re: lyx2lyx bug: duplicating some lyx properties

Am Donnerstag, 31. Dezember 2015 um 19:33:59, schrieb Georg Baum > Scott Kostyshak wrote: > > > The test fails after doing lyx2lyx: > > > > cd lib/examples/fr > > lyx -e lyx21x Foils.lyx > > mv Foils.21.lyx Foils.lyx > > > > After doing a (manual) bisect, I

Re: lyx2lyx bug: duplicating some lyx properties

Am 28.12.2015 um 08:27 schrieb Scott Kostyshak: On Mon, Dec 28, 2015 at 08:25:11AM +0100, Kornel Benko wrote: Am Montag, 28. Dezember 2015 um 02:02:45, schrieb Scott Kostyshak On Sun, Dec 27, 2015 at 05:39:06PM +0100, Kornel Benko wrote: Am Sonntag, 27. Dezember 2015 um

Re: lyx2lyx bug: duplicating some lyx properties

Scott Kostyshak wrote: > The test fails after doing lyx2lyx: > > cd lib/examples/fr > lyx -e lyx21x Foils.lyx > mv Foils.21.lyx Foils.lyx > > After doing a (manual) bisect, I narrowed the failure down to the 500 vs. > 501 format change: > > cd lib/examples/fr && git checkout Foils.lyx && >

Re: lyx2lyx bug: duplicating some lyx properties

On Thu, Dec 31, 2015 at 01:38:56PM +0100, Georg Baum wrote: > Am 28.12.2015 um 08:27 schrieb Scott Kostyshak: > >On Mon, Dec 28, 2015 at 08:25:11AM +0100, Kornel Benko wrote: > >>Am Montag, 28. Dezember 2015 um 02:02:45, schrieb Scott Kostyshak > >> > >>>On Sun, Dec 27, 2015 at

Re: lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

On 05/27/2014 01:33 AM, Patrick O'Keeffe wrote: On 5/26/2014 2:27 PM, José Matos wrote: The problem according to my analysis is the line lastpar = ''.join(contents[-1]) where contents is an empty list. So probably something like if not contents: continue would work. A more precise fix

Re: lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

On 05/27/2014 01:33 AM, Patrick O'Keeffe wrote: On 5/26/2014 2:27 PM, José Matos wrote: The problem according to my analysis is the line lastpar = ''.join(contents[-1]) where contents is an empty list. So probably something like if not contents: continue would work. A more precise fix

lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

Hi, we got a bug reported at Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1098368 related with chunks conversions. According to git blame, Richard and Jürgen were the last to touch this code. :-) The problem according to my analysis is the line lastpar = ''.join(contents[-1])

Re: lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

On 5/26/2014 2:27 PM, José Matos wrote: The problem according to my analysis is the line lastpar = ''.join(contents[-1]) where contents is an empty list. So probably something like if not contents: continue would work. A more precise fix may be preferred: lastpar = ''.join(contents[-1]

lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

Hi, we got a bug reported at Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1098368 related with chunks conversions. According to git blame, Richard and Jürgen were the last to touch this code. :-) The problem according to my analysis is the line lastpar = ''.join(contents[-1])

Re: lyx2lyx bug reported to fedora: lyx_2_1.py:4356:convert_chunks:IndexError: list index out of range

On 5/26/2014 2:27 PM, José Matos wrote: The problem according to my analysis is the line lastpar = ''.join(contents[-1]) where contents is an empty list. So probably something like if not contents: continue would work. A more precise fix may be preferred: lastpar = ''.join(contents[-1]

Re: lyx2lyx bug

is that there is some buggy conversion code, and it seems to run only when the name is not quoted. Georg, this is the format 48 conversion code you introduced at 6b49b6b1. In this case, we end up converting I'll have a look (after I finihsed the lyx2lyx bug regarding math packages). I took care

Re: lyx2lyx bug

is that there is some buggy conversion code, and it seems to run only when the name is not quoted. Georg, this is the format 48 conversion code you introduced at 6b49b6b1. In this case, we end up converting I'll have a look (after I finihsed the lyx2lyx bug regarding math packages). I took care

Re: lyx2lyx bug

to run only when the name is not quoted. Georg, this is the format 48 conversion code you introduced at 6b49b6b1. In this case, we end up converting I'll have a look (after I finihsed the lyx2lyx bug regarding math packages). Georg

Re: lyx2lyx bug

version code, and it seems to run only when > the name is not quoted. > > Georg, this is the format 48 conversion code you introduced at 6b49b6b1. > In this case, we end up converting I'll have a look (after I finihsed the lyx2lyx bug regarding math packages). Georg

Re: lyx2lyx bug

Of coures I meant: layout2layout bug. On 04/22/2014 10:42 PM, Richard Heck wrote: On 04/22/2014 08:20 PM, aparsloe wrote: The Customisation manual (downloaded with LyX 2.1.0 an hour ago) says in Section 5.3.9: The layout for a Flex inset is being defined. In this case, |Type| must be of

Re: lyx2lyx bug

Of coures I meant: layout2layout bug. On 04/22/2014 10:42 PM, Richard Heck wrote: On 04/22/2014 08:20 PM, aparsloe wrote: The Customisation manual (downloaded with LyX 2.1.0 an hour ago) says in Section 5.3.9: The layout for a Flex inset is being defined. In this case, || must be of the

lyx2lyx bug

On 04/22/2014 08:20 PM, aparsloe wrote: The Customisation manual (downloaded with LyX 2.1.0 an hour ago) says in Section 5.3.9: The layout for a Flex inset is being defined. In this case, |Type| must be of the form |Flex:name|, where |name| may be be any valid identifier not used by a

lyx2lyx bug

On 04/22/2014 08:20 PM, aparsloe wrote: The Customisation manual (downloaded with LyX 2.1.0 an hour ago) says in Section 5.3.9: The layout for a Flex inset is being defined. In this case, || must be of the form "|Flex:|", where |name| may be be any valid identifier not used by a pre-existing

Re: [patch] fix lyx2lyx bug 2995

Uwe Stöhr wrote: José, Jürgen, OK for branch? I don't think this is the correct approach. The error you see is not bound to a specific LyX version, you can also produce it with LyX 1.5: - insert a table - make a cell of fixed width with some content - Edit-Paragraph-Center - remove fixed width

Re: [patch] fix lyx2lyx bug 2995

Am Montag, 24. September 2007 08:08:35 schrieb Jürgen Spitzmüller: I don't think this is the correct approach. The error you see is not bound to a specific LyX version, you can also produce it with LyX 1.5: - insert a table - make a cell of fixed width with some content -

Re: [patch] fix lyx2lyx bug 2995

I don't think this is the correct approach. The error you see is not bound to a specific LyX version, you can also produce it with LyX 1.5: - insert a table - make a cell of fixed width with some content - Edit-Paragraph-Center - remove fixed width from cell - view-dvi This is a

Re: [patch] fix lyx2lyx bug 2995

Uwe Stöhr wrote: This is a different bug. Bug 2995 is about that when you set the paragraph where the table is in to centered, it is correctly handled by LyX 1.3 but not by LyX 1.4 and later. So this is about the paragraph alignment outside the table, not inside. My reading of the bug

Re: [patch] fix lyx2lyx bug 2995

Uwe Stöhr wrote: > José, Jürgen, OK for branch? I don't think this is the correct approach. The error you see is not bound to a specific LyX version, you can also produce it with LyX 1.5: - insert a table - make a cell of fixed width with some content - Edit->Paragraph->Center - remove fixed

Re: [patch] fix lyx2lyx bug 2995

Am Montag, 24. September 2007 08:08:35 schrieb Jürgen Spitzmüller: > I don't think this is the correct approach. The error you see is not bound > to a specific LyX version, you can also produce it with LyX 1.5: > > - insert a table > - make a cell of fixed width with some content > -

Re: [patch] fix lyx2lyx bug 2995

> I don't think this is the correct approach. The error you see is not bound to > a specific LyX version, you can also produce it with LyX 1.5: > > - insert a table > - make a cell of fixed width with some content > - Edit->Paragraph->Center > - remove fixed width from cell > - view->dvi This is

Re: [patch] fix lyx2lyx bug 2995

Uwe Stöhr wrote: > This is a different bug. Bug 2995 is about that when you set the paragraph > where the table is in to centered, it is correctly handled by LyX 1.3 but > not by LyX 1.4 and later. So this is about the paragraph alignment outside > the table, not inside. My reading of the bug

[patch] fix lyx2lyx bug 2995

The attached patch fixes http://bugzilla.lyx.org/show_bug.cgi?id=2995 Documents with centered tables are wrongly converted to LyX 1.4's and newer file formats. The resulting files are unusable as they produce LaTeX-errors. The problem was that the \align tags within tables were not removed in

[patch] fix lyx2lyx bug 2995

The attached patch fixes http://bugzilla.lyx.org/show_bug.cgi?id=2995 Documents with centered tables are wrongly converted to LyX 1.4's and newer file formats. The resulting files are unusable as they produce LaTeX-errors. The problem was that the \align tags within tables were not removed in

lyx2lyx bug (was: Re: [patch] partial merging of CharStyle and InsetLayout handling)

Dov Feldstern wrote: The bigger problem, though, has nothing to do with your code: it looks like lyx2lyx (at least when run from the command line) is just ignoring anything with format above 276. If you change your file's format to 276, then lyx2lyx will work fine. The reason I say that this

Re: lyx2lyx bug (was: Re: [patch] partial merging of CharStyle and InsetLayout handling)

On Fri, Aug 17, 2007 at 05:20:08PM +0300, Dov Feldstern wrote: Dov Feldstern wrote: The bigger problem, though, has nothing to do with your code: it looks like lyx2lyx (at least when run from the command line) is just ignoring anything with format above 276. If you change your file's

lyx2lyx bug (was: Re: [patch] partial merging of CharStyle and InsetLayout handling)

Dov Feldstern wrote: The bigger problem, though, has nothing to do with your code: it looks like lyx2lyx (at least when run from the command line) is just ignoring anything with format above 276. If you change your file's format to 276, then lyx2lyx will work fine. The reason I say that this

Re: lyx2lyx bug (was: Re: [patch] partial merging of CharStyle and InsetLayout handling)

On Fri, Aug 17, 2007 at 05:20:08PM +0300, Dov Feldstern wrote: > Dov Feldstern wrote: > > The bigger problem, though, has nothing to do with your code: it looks like > > lyx2lyx (at least when run from the command line) is just ignoring anything > > with format above 276. If you change your

Re: lyx2lyx bug about armtex.sty

On Wednesday 09 May 2007 17:08:52 Uwe Stöhr wrote: Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Thanks for the report. The armtex-package shouldn't be set in every case to the preamble, only when Armenian was

Re: lyx2lyx bug about armtex.sty

Bo Peng schrieb: Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Fixed: http://www.lyx.org/trac/changeset/18250 regards Uwe

lyx2lyx bug about armtex.sty

Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Cheers, Bo

Re: lyx2lyx bug about armtex.sty

Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Thanks for the report. The armtex-package shouldn't be set in every case to the preamble, only when Armenian was used as document language. I'll have a look. regards

lyx2lyx bug about armtex.sty

Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Cheers, Bo

Re: lyx2lyx bug about armtex.sty

Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Thanks for the report. The armtex-package shouldn't be set in every case to the preamble, only when Armenian was used as document language. I'll have a look. regards

Re: lyx2lyx bug about armtex.sty

On Wednesday 09 May 2007 17:08:52 Uwe Stöhr wrote: > > Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view > > pdf, I see > > > > LaTex Error: File 'armtex.sty' not found. > > Thanks for the report. The armtex-package shouldn't be set in every case to > the preamble, only when

Re: lyx2lyx bug about armtex.sty

Bo Peng schrieb: Open any 1.5.x document, say faq, export to 1.4, open faq.lyx14, view pdf, I see LaTex Error: File 'armtex.sty' not found. Fixed: http://www.lyx.org/trac/changeset/18250 regards Uwe

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Jürgen Spitzmüller schrieb: QDocumentDialog.C: 407 // FIXME: hack to work around resizing bug in Qt = 4.2 #if QT_VERSION = 0x040200 docPS-updateGeometry(); #endif QCharacter.C: 94 // FIXME: hack to work around resizing bug in Qt = 4.2 #if

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Michael Gerz wrote: I am sorry, Jürgen, but the text-style-dialog-resize-bug is still there (Win/Qt 4.2.1/MSVC). I see. it is cured on Linux, and I'm running out of ideas. So if noone else has an idea, I fear you win people will have to live with that ;-( By looking at the code snippets

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Jürgen Spitzmüller schrieb: QDocumentDialog.C: 407 // FIXME: hack to work around resizing bug in Qt >= 4.2 #if QT_VERSION >= 0x040200 docPS->updateGeometry(); #endif QCharacter.C: 94 // FIXME: hack to work around resizing bug in Qt >= 4.2

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Michael Gerz wrote: > I am sorry, Jürgen, but the text-style-dialog-resize-bug is still there > (Win/Qt 4.2.1/MSVC). I see. it is cured on Linux, and I'm running out of ideas. So if noone else has an idea, I fear you win people will have to live with that ;-( > By looking at the code snippets

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Juergen Spitzmueller wrote: The only way to get the combo boxes resize properly seems to be to trigger show() again after the items have been inserted, see: http://lists.trolltech.com/qt-interest/2002-03/thread01170-0.html This is all but pretty, but I tried several more elegant solutions to

Re: [patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Juergen Spitzmueller wrote: > The only way to get the combo boxes resize properly seems to be to trigger > show() again after the items have been inserted, see: > http://lists.trolltech.com/qt-interest/2002-03/thread01170-0.html > > This is all but pretty, but I tried several more elegant

[patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Uwe Stöhr wrote: - the text style dialog is too small, see bug 3032:    http://bugzilla.lyx.org/show_bug.cgi?id=3032 The only way to get the combo boxes resize properly seems to be to trigger show() again after the items have been inserted, see:

[patch] Re: LyX1.5.0svn: lyx2lyx bug and dialog issue

Uwe Stöhr wrote: > - the text style dialog is too small, see bug 3032: >    http://bugzilla.lyx.org/show_bug.cgi?id=3032 The only way to get the combo boxes resize properly seems to be to trigger show() again after the items have been inserted, see:

LyX1.5.0svn: lyx2lyx bug and dialog issue

Two bug reports: - the text style dialog is too small, see bug 3032: http://bugzilla.lyx.org/show_bug.cgi?id=3032 - LyX-files with math-macros aren't correctly converted to LyX150svn's LyX-format, see bug 3034: http://bugzilla.lyx.org/show_bug.cgi?id=3034 regards Uwe

LyX1.5.0svn: lyx2lyx bug and dialog issue

Two bug reports: - the text style dialog is too small, see bug 3032: http://bugzilla.lyx.org/show_bug.cgi?id=3032 - LyX-files with math-macros aren't correctly converted to LyX150svn's LyX-format, see bug 3034: http://bugzilla.lyx.org/show_bug.cgi?id=3034 regards Uwe

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Helge Hafting wrote: Angus Leeming wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: Can you try to change the utf-8 to ucs-4 conversion to use either UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the other way ucs-4 - ucs-2, try with UCS-2BE and

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Helge Hafting wrote: Angus Leeming wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: Can you try to change the utf-8 to ucs-4 conversion to use either "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the other way ucs-4 -> ucs-2, try with UCS-2BE

lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Georg Baum wrote: Abdelrazak Younes wrote: No, I've reverted to 245. Maybe my problem is that lyx doesn't call the right lyx2lyx version... I am launching lyx from the scons build tree. Running from the build tree works for me. Run it with -dbg package, and it

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes [EMAIL PROTECTED] writes: | Abdelrazak Younes wrote: | Georg Baum wrote: | Abdelrazak Younes wrote: | | No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | right lyx2lyx version... I am launching lyx from the scons build tree. | | Running from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: I have converted by hand Intro.lyx: D:\program\lyx-msvc\Resources\lyx2lyxpython lyx2lyx -t 249 -o .\Intro.lyx ..\doc\Intro.lyx The resulting file seems to have the correct version number: #LyX 1.5.0svn created this file. For more info see http://www.lyx.org/

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Georg Baum wrote: Abdelrazak Younes wrote: I have converted by hand Intro.lyx: D:\program\lyx-msvc\Resources\lyx2lyxpython lyx2lyx -t 249 -o .\Intro.lyx ..\doc\Intro.lyx The resulting file seems to have the correct version number: #LyX 1.5.0svn created this file. For more info see

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: | Abdelrazak Younes wrote: | Georg Baum wrote: | Abdelrazak Younes wrote: | | No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | right lyx2lyx version... I am launching lyx from the scons build

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: | Abdelrazak Younes wrote: | Georg Baum wrote: | Abdelrazak Younes wrote: | | No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | right lyx2lyx version... I am launching lyx from the scons build

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Lars Gullik Bjønnes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: | Abdelrazak Younes wrote: | Georg Baum wrote: | Abdelrazak Younes wrote: | | No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | right lyx2lyx version... I am launching

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: | Abdelrazak Younes wrote: | Georg Baum wrote: | Abdelrazak Younes wrote: | | No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | right lyx2lyx version... I am launching lyx from the scons build

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes [EMAIL PROTECTED] writes: Can you try to change the utf-8 to ucs-4 conversion to use either UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the other way ucs-4 - ucs-2, try with UCS-2BE and UCS-2LE. And with the attached patch where I have put LE everywhere, the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: Can you try to change the utf-8 to ucs-4 conversion to use either UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the other way ucs-4 - ucs-2, try with UCS-2BE and UCS-2LE. And with the attached patch

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: Can you try to change the utf-8 to ucs-4 conversion to use either UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the other way ucs-4 - ucs-2, try with UCS-2BE and UCS-2LE. And with the attached patch where I have put

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting [EMAIL PROTECTED] writes: I thought UTF-8 didn't care about endianness, being a single-byte encoding? A conversion to UCS-4 can go wrong if he convert to the wrong UCS-4 format, but utf-8 is supposed to be the same no matter what endianness the machine uses? Sigh. Yes, you're

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting wrote: Angus Leeming wrote: Abdelrazak Younes [EMAIL PROTECTED] writes: Can you try to change the utf-8 to ucs-4 conversion to use either UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the other way ucs-4 - ucs-2, try with UCS-2BE and UCS-2LE. And with the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting wrote: I thought UTF-8 didn't care about endianness, being a single-byte encoding? That would be great: stuffing the whole unicode range in a single-byte encoding, but for obvious reasons that does not work. You are right that the endianness is not a problem in utf8, since it

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Well, the reference labels (and cross-reference) are part of the lyx format aren't they? They are. And that is the proof that you now have the ucs4 conversion machinery working: The labels are currently not stored in docstring, but in std::string as read in from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Georg Baum wrote: Abdelrazak Younes wrote: Well, the reference labels (and cross-reference) are part of the lyx format aren't they? They are. And that is the proof that you now have the ucs4 conversion machinery working: The labels are currently not stored in docstring, but in std::string as

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming [EMAIL PROTECTED] writes: | Abdelrazak Younes [EMAIL PROTECTED] writes: | Can you try to change the utf-8 to ucs-4 conversion to use either | UCS-4BE or UCS-4LE, instead of UCS-4? Also the conversion the | other way ucs-4 - ucs-2, try with UCS-2BE and UCS-2LE. | | And with the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes [EMAIL PROTECTED] writes: UTF-8 is chars so BOM has no place there... Right. I see that now, but it was the act of (trying to) explain that revealed to me that I actually didn't understand things after all. I now understand that Windows file formats tend to output directly

lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Georg Baum wrote: Abdelrazak Younes wrote: No, I've reverted to 245. Maybe my problem is that lyx doesn't call the right lyx2lyx version... I am launching lyx from the scons build tree. Running from the build tree works for me. Run it with -dbg package, and it

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > Georg Baum wrote: | >> Abdelrazak Younes wrote: | >> | >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | >>> right lyx2lyx version... I am launching lyx from the scons build tree. | >> | >>

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: > I have converted by hand Intro.lyx: > > D:\program\lyx-msvc\Resources\lyx2lyx>python lyx2lyx -t 249 -o > .\Intro.lyx ..\doc\Intro.lyx > > The resulting file seems to have the correct version number: > #LyX 1.5.0svn created this file. For more info see

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Georg Baum wrote: Abdelrazak Younes wrote: I have converted by hand Intro.lyx: D:\program\lyx-msvc\Resources\lyx2lyx>python lyx2lyx -t 249 -o .\Intro.lyx ..\doc\Intro.lyx The resulting file seems to have the correct version number: #LyX 1.5.0svn created this file. For more info see

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > Georg Baum wrote: | >> Abdelrazak Younes wrote: | >> | >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | >>> right lyx2lyx version... I am launching lyx from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > Georg Baum wrote: | >> Abdelrazak Younes wrote: | >> | >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | >>> right lyx2lyx version... I am launching lyx from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > Georg Baum wrote: | >> Abdelrazak Younes wrote: | >> | >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | >>> right lyx2lyx version... I

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: | Abdelrazak Younes wrote: | > Georg Baum wrote: | >> Abdelrazak Younes wrote: | >> | >>> No, I've reverted to 245. Maybe my problem is that lyx doesn't call the | >>> right lyx2lyx version... I am launching lyx from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> Can you try to change the utf-8 to ucs-4 conversion to use either >> "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the >> other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE. > And with the attached patch where I have put LE

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: Can you try to change the utf-8 to ucs-4 conversion to use either "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE. And with the attached

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: Can you try to change the utf-8 to ucs-4 conversion to use either "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE. And with the attached patch where I

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting <[EMAIL PROTECTED]> writes: > I thought UTF-8 didn't care about endianness, being a single-byte > encoding? A conversion to UCS-4 can go wrong if he convert > to the wrong UCS-4 format, but utf-8 is supposed to be > the same no matter what endianness the machine uses? Sigh. Yes,

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting wrote: Angus Leeming wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: Can you try to change the utf-8 to ucs-4 conversion to use either "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE. And

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Helge Hafting wrote: > I thought UTF-8 didn't care about endianness, being a single-byte > encoding? That would be great: stuffing the whole unicode range in a single-byte encoding, but for obvious reasons that does not work. You are right that the endianness is not a problem in utf8, since it

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Abdelrazak Younes wrote: > Well, the reference labels (and cross-reference) are part of the lyx > format aren't they? They are. And that is the proof that you now have the ucs4 conversion machinery working: The labels are currently not stored in docstring, but in std::string as read in from the

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Georg Baum wrote: Abdelrazak Younes wrote: Well, the reference labels (and cross-reference) are part of the lyx format aren't they? They are. And that is the proof that you now have the ucs4 conversion machinery working: The labels are currently not stored in docstring, but in std::string as

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Angus Leeming <[EMAIL PROTECTED]> writes: | Abdelrazak Younes <[EMAIL PROTECTED]> writes: | >> Can you try to change the utf-8 to ucs-4 conversion to use either | >> "UCS-4BE" or "UCS-4LE", instead of "UCS-4"? Also the conversion the | >> other way ucs-4 -> ucs-2, try with UCS-2BE and UCS-2LE. |

Re: lyx2lyx bug? (was Re: Track change status Michael? (Re: [PATCH] small setBuffer cleanup)

Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > UTF-8 is chars so BOM has no place there... Right. I see that now, but it was the act of (trying to) explain that revealed to me that I actually didn't understand things after all. I now understand that Windows file formats tend to output

  1   2   >