Re: Anybody Wanna Own Some Bugs?

[Jürgen Spitzmüller]

2014-04-24 0:29 GMT+02:00 Vincent van Ravesteijn v...@lyx.org:

 You could sign me up for those two.

Done.

 However, I'm not sure what it means to be the ticket owner.

I think the main purpose is that someone knowledgeable in the respective
area checks the severity of the bug, maybe invites people to fix it or
fixes it himself. Having an owner at least should assure that urgent issues
do not vanish in the dust of trac.

Jürgen


 Vincent

Re: Feature request

[Rainer M Krug]

Scott Kostyshak skost...@lyx.org writes:

 On Thu, Apr 24, 2014 at 1:29 PM, Pavel Sanda sa...@lyx.org wrote:
 Scott Kostyshak wrote:
 Another problem is that some mailing lists require/encourage quote
 prior messages in entirety (e.g.

 It makes any longer exchange unreadable.

 Agreed.

 When involved in the exchange I usually care to strip it no matter what the
 other party does, but anyway it's not nice to let other people do your 
 work...

 My point is that I think many do it out of ignorance, not laziness. At
 least that was the case for me. I wish someone had told me sooner. In
 the end it is my fault for not having remembered the list netiquette.

Gmail has folding, Thunderbird has folding, GNUS has folding, and I
assume most email clients have folding / hiding of quotes.

As stated, some mailing lists wish to have the whole thread, to make
reading a reply separately possible. 

Snipping of sections I do not reply to is OK, but selectively snipping
out of sections I reply to make it possible to change the original
meaning. 

So I think no snipping is not a major problem.

Rainer


 Scott

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


pgp5RWA1JYiz0.pgp
Description: PGP signature

Re: Feature request

[Scott Kostyshak]

On Fri, Apr 25, 2014 at 9:50 AM, Rainer M Krug rai...@krugs.de wrote:

 Gmail has folding, Thunderbird has folding, GNUS has folding, and I
 assume most email clients have folding / hiding of quotes.

 As stated, some mailing lists wish to have the whole thread, to make
 reading a reply separately possible.

 Snipping of sections I do not reply to is OK, but selectively snipping
 out of sections I reply to make it possible to change the original
 meaning.

Agreed. There is a tradeoff. By keeping the whole conversation you do
not take things out of context. But you make it more difficult to
quickly get the main point. It is subjective what is out of context
but I have actually never seen an argument because of this on the
mailing lists I participate in.

 So I think no snipping is not a major problem.

Well, some people view it as a problem and because it is listed on the
List Netiquette (http://www.lyx.org/MailingLists#toc7) in my opinion
we should follow it, or argue to change the Netiquette. I actually
like the rule as it is; I just didn't follow it because I thought the
opposite was the encouraged behavior.

Scott

[ANNOUNCE] LyX 2.1.0 Released

[Richard Heck]

The LyX development team is pleased to announce the release of LyX 
2.1.0. This release represents the result of more than three years of 
hard work. Many bugs have been fixed, and several new features have been 
added. The new features in LyX 2.1 are detailed in 
http://wiki.lyx.org/LyX/NewInLyX21 and include:


* Native IPA inset and IPA toolbar
* New supported languages
* Tex Fonts Additions
* Basic support for Math OpenType fonts
* Document class categories
* Enhanced support for LaTeX options
* Much improved Beamer support
* New supported LaTeX commands
* New export command-line option
* Table rotations
* Layout enhancements
* New modules
* Equation Editor mode

We hope you enjoy using LyX 2.1.0 and that it makes you a more 
productive writer. Should you experience any difficulties, please send 
an email to the user list (lyx-us...@lists.lyx.org), the development 
list (lyx-devel@lists.lyx.org), or file a bug report 
(http://www.lyx.org/trac/wiki/BugTrackerHome).

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Jürgen Spitzmüller]

2014-04-25 17:44 GMT+02:00:

 Author: rgheck
 Date: Fri Apr 25 17:44:36 2014
 New Revision: 41003
 URL: http://www.lyx.org/trac/changeset/41003

 Log:
 Announce 2.1.0.


Excellent. Congrats to everybody. Small typo below:


 +pSource tarballs can be found at our
 +a href=\ftp://ftp.lyx.org/pub/lyx/stable/2.1.x/\;ftp server/a. There
 +are also a href=\ftp://ftp.lyx.org/pub/lyx/bin/2.1.0/\binaries/a for


the closing angle after the href tag is missing.


 +pThe file
 +a href=\
 http://git.lyx.org/?p=lyx.git;a=blob_plain;f=RELEASE-NOTES;hb=fde16219ca7860fdfe8adf171d109a7cce61e7b4\
 
 +RELEASE-NOTES/a lists some known issues and problems compared
 +to the current stable releases (LyX 2.1.x).


Should this read compared to the previous stable releases (LyX 2.0.x)?

+pIf you have trouble using LyX or have a question, consult the
 +documentation that comes with LyX (under Help) and the
 +a href=\http://wiki.lyx.org/\;LyX wiki/a.
 +You can also send email to the LyX users'
 +list (lyx-users at lists.lyx.org)./p);


The mail address could be linked.

Jürgen

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Richard Heck]

On 04/25/2014 11:58 AM, Jürgen Spitzmüller wrote:


+pIf you have trouble using LyX or have a question, consult the
+documentation that comes with LyX (under Help) and the
+a href=\http://wiki.lyx.org/\ http://wiki.lyx.org/%5CLyX
wiki/a.
+You can also send email to the LyX users'
+list (lyx-users at lists.lyx.org http://lists.lyx.org)./p);


The mail address could be linked.


I copied this from earlier versions, and it seems we didn't link it before.

Fixed the other issues.

Richard

Re: Feature request

[Pavel Sanda]

Rainer M Krug wrote:
 Gmail has folding, Thunderbird has folding, GNUS has folding, and I
 assume most email clients have folding / hiding of quotes.

Well, there exists world beyond gmail and thunderbird and this world
still produces reasonable traffic on this list.

But I agree that until delete-thread function is removed from my
email client it is not a major problem for me :)

Pavel

OSX Problem With 2.1.0 [Was: Re: launch incomplete]

[Richard Heck]

We got this report on the user list.

Richard


 Original Message 
Subject:Re: launch incomplete
Date:   Fri, 25 Apr 2014 19:33:26 +0200
From:   Anders Ekberg a...@mac.com
To: David Nuddleman da...@xsharp.com, lyx-us...@lists.lyx.org



Can partly confirm on MacBook Air 10.9.2.
Judging from Console there seems to be some font problems with messages on
the form:
2014-04-25 19:26:32,724 lyx[33795]: CoreText performance note: Client
called CTFontCreateWithName() using name Courier New and got font with
PostScript name CourierNewPSMT. For best performance, only use
PostScript names when calling this API.

However the main error seems to be LuaTeX:

2014-04-25 19:28:35,338 ReportCrash[33894]: Saved crash report for
luatex[33204] version ??? to
/Users/anek/Library/Logs/DiagnosticReports/luatex_2014-04-25-192835_AM125.c
rash

BUT after working for four minutes, the program actually loaded and the
users guide seems to compile as it should.

So, many thanks for a great job (as always)!

Anders


-Original Message-
From: David Nuddleman da...@xsharp.com
Date: Friday 25 April 2014 19:04
To: lyx-us...@lists.lyx.org
Subject: launch incomplete


Download of LyX-2.1.0+qt4-cocoa.dmg after mounting, copying to
applications folder. Launch seems to abort.

OS X 10.9.2 Quad-Core Intel Xeon

After GSoC proposal rejection

[Mitul Modi]

Hello,

I had applied for GSoC for project Implement 3-box drawing of
insets(http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/mitul15/5629499534213120)
which was not selected. I want to do this project out of GSoC. So if
mentors can tell what was lacking in proposal or strategy and suggest
how should I go further in this project with.

Thank you.

-- 
Regards

Mitul

Re: Feature request

[Vincent van Ravesteijn]

Scott Kostyshak schreef op 25-4-2014 16:00:

So I think no snipping is not a major problem.

Well, some people view it as a problem and because it is listed on the
List Netiquette (http://www.lyx.org/MailingLists#toc7) in my opinion
we should follow it, or argue to change the Netiquette. I actually
like the rule as it is; I just didn't follow it because I thought the
opposite was the encouraged behavior.

Scott
Does the netiquette say something about hijacking a thread to discuss a 
non-related subject ?


Vincent

Re: Feature request

[Scott Kostyshak]

On Fri, Apr 25, 2014 at 3:36 PM, Vincent van Ravesteijn v...@lyx.org wrote:

 Does the netiquette say something about hijacking a thread to discuss a
 non-related subject ?

Good point.

Scott

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Vincent van Ravesteijn]

Jürgen Spitzmüller schreef op 25-4-2014 17:58:

2014-04-25 17:44 GMT+02:00:

Author: rgheck
Date: Fri Apr 25 17:44:36 2014
New Revision: 41003
URL: http://www.lyx.org/trac/changeset/41003

Log:
Announce 2.1.0.


Excellent. Congrats to everybody.


Yes, congratulations.

Thanks Richard finishing off.

Vincent

severe lyx2lyx problem for 2.1 = 2.0 conversion

[Georg Baum]

I am sorry that this comes so late, but I found severe problems in lyx2lyx 
which occur for 2.1 = 2.0 conversion while testing my fix for bug #9069. 
If you do the roundtrip 2.0 = 2.1 = 2.0 for the 2.0.8 user guide, you get 
a document with invalid header settings and data loss where argument and 
index insets are mixed. I fixed these two problems at 
http://www.lyx.org/trac/changeset/2fe07e1fe1e/lyxgit and 
http://www.lyx.org/trac/changeset/5710f68c340/lyxgit.

What to do now? These fixes as well as 
http://www.lyx.org/trac/changeset/cacd2a041d2/lyxgit and 
http://www.lyx.org/trac/changeset/52d25886131/lyxgit should go to 2.1.1. 
Richard, is this OK?

I also think that the final 2.0.x release should have them. I know that 
this would create much additional work, since 2.0.8 is already tagged and  
packaged (and therefore can't be changed anymore), but I don't think that 
it is acceptable to tell people that it can read 2.1 files if in fact 
these files will not be converted correctly in most cases.

The question is of course how to avoid such bugs in the future, and I 
believe that we need automated lyx2lyx roundtrip tests: Such tests would 
have found the problems.


Georg

Re: severe lyx2lyx problem for 2.1 = 2.0 conversion

[Richard Heck]

On 04/25/2014 05:05 PM, Georg Baum wrote:

I am sorry that this comes so late, but I found severe problems in lyx2lyx
which occur for 2.1 = 2.0 conversion while testing my fix for bug #9069.
If you do the roundtrip 2.0 = 2.1 = 2.0 for the 2.0.8 user guide, you get
a document with invalid header settings and data loss where argument and
index insets are mixed. I fixed these two problems at
http://www.lyx.org/trac/changeset/2fe07e1fe1e/lyxgit and
http://www.lyx.org/trac/changeset/5710f68c340/lyxgit.

What to do now? These fixes as well as
http://www.lyx.org/trac/changeset/cacd2a041d2/lyxgit and
http://www.lyx.org/trac/changeset/52d25886131/lyxgit should go to 2.1.1.
Richard, is this OK?


Yes, those look good.


I also think that the final 2.0.x release should have them. I know that
this would create much additional work, since 2.0.8 is already tagged and
packaged (and therefore can't be changed anymore), but I don't think that
it is acceptable to tell people that it can read 2.1 files if in fact
these files will not be converted correctly in most cases.


I'm inclined to agree. It would mean re-packaging for everyone, but it 
shouldn't be too bad. Other opinions?



The question is of course how to avoid such bugs in the future, and I
believe that we need automated lyx2lyx roundtrip tests: Such tests would
have found the problems.


That would be a good idea.

Richard

Re: lyx2lyx bug

[Richard Heck]

On 04/24/2014 02:47 PM, Georg Baum wrote:

Richard Heck wrote:


This is close to right, but the problem is in the conversion of layouts.
It's fine not to quote the names. Look at e.g. logicalmkup.module. Mone
of the InsetLayout names are quoted, yet they work fine. The problem 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 of this at 7e1541dd. The module on which it failed was 
actually ill-formed, but there was the issue about quoted names, and I 
simplified and sped up the code a bit.


Richard

Re: severe lyx2lyx problem for 2.1 = 2.0 conversion

[Pavel Sanda]

Richard Heck wrote:
 I'm inclined to agree. It would mean re-packaging for everyone, but it 
 shouldn't be too bad. Other opinions?

We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.
Pavel

Re: severe lyx2lyx problem for 2.1 = 2.0 conversion

[Richard Heck]

On 04/25/2014 06:48 PM, Pavel Sanda wrote:

Richard Heck wrote:

I'm inclined to agree. It would mean re-packaging for everyone, but it
shouldn't be too bad. Other opinions?

We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.


Yes, that's true.

rh

Re: severe lyx2lyx problem for 2.1 = 2.0 conversion

[Pavel Sanda]

Richard Heck wrote:
 On 04/25/2014 06:48 PM, Pavel Sanda wrote:
 Richard Heck wrote:
 I'm inclined to agree. It would mean re-packaging for everyone, but it
 shouldn't be too bad. Other opinions?
 We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.

 Yes, that's true.

If the question was whether we should repackage at all then I think yes as 
well. P

Re: severe lyx2lyx problem for 2.1 = 2.0 conversion

[Pavel Sanda]

Georg Baum wrote:
 a document with invalid header settings and data loss where argument and 
 index insets are mixed. I fixed these two problems at 

BTW how often this dataloss happens - only if index inset is present?
(I ask whether immediate 2.1.(0.)1 release is needed or we can wait weeks...)

Pavel

Shortcuts for 'post' arguments

[aparsloe]

The Alt+A 1, etc. shortcuts  for custom inset arguments are a real boon. 
However, I note that a 'post' argument, following the main argument, 
doesn't get a shortcut, which is a pity. Is this oversight or are there 
technical reasons preventing the extension of shortcuts to 'post' arguments?


Andrew

Re: Anybody Wanna Own Some Bugs?

[Jürgen Spitzmüller]

2014-04-24 0:29 GMT+02:00 Vincent van Ravesteijn :
>
> You could sign me up for those two.
>
Done.

> However, I'm not sure what it means to be the ticket owner.
>
I think the main purpose is that someone knowledgeable in the respective
area checks the severity of the bug, maybe invites people to fix it or
fixes it himself. Having an owner at least should assure that urgent issues
do not vanish in the dust of trac.

Jürgen


> Vincent
>

Re: Feature request

[Rainer M Krug]

Scott Kostyshak  writes:

> On Thu, Apr 24, 2014 at 1:29 PM, Pavel Sanda  wrote:
>> Scott Kostyshak wrote:
>>> Another problem is that some mailing lists require/encourage "quote
>>> prior messages in entirety" (e.g.
>>
>> It makes any longer exchange unreadable.
>
> Agreed.
>
>> When involved in the exchange I usually care to strip it no matter what the
>> other party does, but anyway it's not nice to let other people do your 
>> work...
>
> My point is that I think many do it out of ignorance, not laziness. At
> least that was the case for me. I wish someone had told me sooner. In
> the end it is my fault for not having remembered the list netiquette.

Gmail has folding, Thunderbird has folding, GNUS has folding, and I
assume most email clients have folding / hiding of quotes.

As stated, some mailing lists wish to have the whole thread, to make
reading a reply separately possible. 

Snipping of sections I do not reply to is OK, but selectively snipping
out of sections I reply to make it possible to change the original
meaning. 

So I think no snipping is not a major problem.

Rainer

>
> Scott

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, 
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug

PGP: 0x0F52F982


pgp5RWA1JYiz0.pgp
Description: PGP signature

Re: Feature request

[Scott Kostyshak]

On Fri, Apr 25, 2014 at 9:50 AM, Rainer M Krug  wrote:

> Gmail has folding, Thunderbird has folding, GNUS has folding, and I
> assume most email clients have folding / hiding of quotes.
>
> As stated, some mailing lists wish to have the whole thread, to make
> reading a reply separately possible.
>
> Snipping of sections I do not reply to is OK, but selectively snipping
> out of sections I reply to make it possible to change the original
> meaning.

Agreed. There is a tradeoff. By keeping the whole conversation you do
not take things out of context. But you make it more difficult to
quickly get the main point. It is subjective what is "out of context"
but I have actually never seen an argument because of this on the
mailing lists I participate in.

> So I think no snipping is not a major problem.

Well, some people view it as a problem and because it is listed on the
List Netiquette (http://www.lyx.org/MailingLists#toc7) in my opinion
we should follow it, or argue to change the Netiquette. I actually
like the rule as it is; I just didn't follow it because I thought the
opposite was the encouraged behavior.

Scott

[ANNOUNCE] LyX 2.1.0 Released

[Richard Heck]

The LyX development team is pleased to announce the release of LyX 
2.1.0. This release represents the result of more than three years of 
hard work. Many bugs have been fixed, and several new features have been 
added. The new features in LyX 2.1 are detailed in 
http://wiki.lyx.org/LyX/NewInLyX21 and include:


* Native IPA inset and IPA toolbar
* New supported languages
* Tex Fonts Additions
* Basic support for Math OpenType fonts
* Document class categories
* Enhanced support for LaTeX options
* Much improved Beamer support
* New supported LaTeX commands
* New export command-line option
* Table rotations
* Layout enhancements
* New modules
* Equation Editor "mode"

We hope you enjoy using LyX 2.1.0 and that it makes you a more 
productive writer. Should you experience any difficulties, please send 
an email to the user list (lyx-us...@lists.lyx.org), the development 
list (lyx-devel@lists.lyx.org), or file a bug report 
(http://www.lyx.org/trac/wiki/BugTrackerHome).

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Jürgen Spitzmüller]

2014-04-25 17:44 GMT+02:00:

> Author: rgheck
> Date: Fri Apr 25 17:44:36 2014
> New Revision: 41003
> URL: http://www.lyx.org/trac/changeset/41003
>
> Log:
> Announce 2.1.0.
>

Excellent. Congrats to everybody. Small typo below:


> +Source tarballs can be found at our
> +ftp://ftp.lyx.org/pub/lyx/stable/2.1.x/\;>ftp server. There
> +are also ftp://ftp.lyx.org/pub/lyx/bin/2.1.0/\"binaries for
>

the closing angle after the href tag is missing.


> +The file
> + http://git.lyx.org/?p=lyx.git;a=blob_plain;f=RELEASE-NOTES;hb=fde16219ca7860fdfe8adf171d109a7cce61e7b4\
> ">
> +RELEASE-NOTES lists some known issues and problems compared
> +to the current stable releases (LyX 2.1.x).


Should this read "compared to the previous stable releases (LyX 2.0.x)"?

+If you have trouble using LyX or have a question, consult the
> +documentation that comes with LyX (under Help) and the
> +http://wiki.lyx.org/\;>LyX wiki.
> +You can also send email to the LyX users'
> +list (lyx-users at lists.lyx.org).");
>

The mail address could be linked.

Jürgen

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Richard Heck]

On 04/25/2014 11:58 AM, Jürgen Spitzmüller wrote:


+If you have trouble using LyX or have a question, consult the
+documentation that comes with LyX (under Help) and the
+http://wiki.lyx.org/\ ">LyX
wiki.
+You can also send email to the LyX users'
+list (lyx-users at lists.lyx.org ).");


The mail address could be linked.


I copied this from earlier versions, and it seems we didn't link it before.

Fixed the other issues.

Richard

Re: Feature request

[Pavel Sanda]

Rainer M Krug wrote:
> Gmail has folding, Thunderbird has folding, GNUS has folding, and I
> assume most email clients have folding / hiding of quotes.

Well, there exists world beyond gmail and thunderbird and this world
still produces reasonable traffic on this list.

But I agree that until delete-thread function is removed from my
email client it is not a major problem for me :)

Pavel

OSX Problem With 2.1.0 [Was: Re: launch incomplete]

[Richard Heck]

We got this report on the user list.

Richard


 Original Message 
Subject:Re: launch incomplete
Date:   Fri, 25 Apr 2014 19:33:26 +0200
From:   Anders Ekberg 
To: David Nuddleman , lyx-us...@lists.lyx.org



Can partly confirm on MacBook Air 10.9.2.
Judging from Console there seems to be some font problems with messages on
the form:
2014-04-25 19:26:32,724 lyx[33795]: CoreText performance note: Client
called CTFontCreateWithName() using name "Courier New" and got font with
PostScript name "CourierNewPSMT". For best performance, only use
PostScript names when calling this API.

However the main error seems to be LuaTeX:

2014-04-25 19:28:35,338 ReportCrash[33894]: Saved crash report for
luatex[33204] version ??? to
/Users/anek/Library/Logs/DiagnosticReports/luatex_2014-04-25-192835_AM125.c
rash

BUT after working for four minutes, the program actually loaded and the
users guide seems to compile as it should.

So, many thanks for a great job (as always)!

Anders


-Original Message-
From: David Nuddleman 
Date: Friday 25 April 2014 19:04
To: 
Subject: launch incomplete


Download of LyX-2.1.0+qt4-cocoa.dmg after mounting, copying to
applications folder. Launch seems to abort.

OS X 10.9.2 Quad-Core Intel Xeon

After GSoC proposal rejection

[Mitul Modi]

Hello,

I had applied for GSoC for project "Implement 3-box drawing of
insets"(http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/mitul15/5629499534213120)
which was not selected. I want to do this project out of GSoC. So if
mentors can tell what was lacking in proposal or strategy and suggest
how should I go further in this project with.

Thank you.

-- 
Regards

Mitul

Re: Feature request

[Vincent van Ravesteijn]

Scott Kostyshak schreef op 25-4-2014 16:00:

So I think no snipping is not a major problem.

Well, some people view it as a problem and because it is listed on the
List Netiquette (http://www.lyx.org/MailingLists#toc7) in my opinion
we should follow it, or argue to change the Netiquette. I actually
like the rule as it is; I just didn't follow it because I thought the
opposite was the encouraged behavior.

Scott
Does the netiquette say something about hijacking a thread to discuss a 
non-related subject ?


Vincent

Re: Feature request

[Scott Kostyshak]

On Fri, Apr 25, 2014 at 3:36 PM, Vincent van Ravesteijn  wrote:

> Does the netiquette say something about hijacking a thread to discuss a
> non-related subject ?

Good point.

Scott

Re: r41003 - www-user/trunk/farm/cookbook/LyX

[Vincent van Ravesteijn]

Jürgen Spitzmüller schreef op 25-4-2014 17:58:

2014-04-25 17:44 GMT+02:00:

Author: rgheck
Date: Fri Apr 25 17:44:36 2014
New Revision: 41003
URL: http://www.lyx.org/trac/changeset/41003

Log:
Announce 2.1.0.


Excellent. Congrats to everybody.


Yes, congratulations.

Thanks Richard finishing off.

Vincent

severe lyx2lyx problem for 2.1 => 2.0 conversion

[Georg Baum]

I am sorry that this comes so late, but I found severe problems in lyx2lyx 
which occur for 2.1 => 2.0 conversion while testing my fix for bug #9069. 
If you do the roundtrip 2.0 => 2.1 => 2.0 for the 2.0.8 user guide, you get 
a document with invalid header settings and data loss where argument and 
index insets are mixed. I fixed these two problems at 
http://www.lyx.org/trac/changeset/2fe07e1fe1e/lyxgit and 
http://www.lyx.org/trac/changeset/5710f68c340/lyxgit.

What to do now? These fixes as well as 
http://www.lyx.org/trac/changeset/cacd2a041d2/lyxgit and 
http://www.lyx.org/trac/changeset/52d25886131/lyxgit should go to 2.1.1. 
Richard, is this OK?

I also think that the final 2.0.x release should have them. I know that 
this would create much additional work, since 2.0.8 is already tagged and  
packaged (and therefore can't be changed anymore), but I don't think that 
it is acceptable to tell people that it can read 2.1 files if in fact 
these files will not be converted correctly in most cases.

The question is of course how to avoid such bugs in the future, and I 
believe that we need automated lyx2lyx roundtrip tests: Such tests would 
have found the problems.


Georg

Re: severe lyx2lyx problem for 2.1 => 2.0 conversion

[Richard Heck]

On 04/25/2014 05:05 PM, Georg Baum wrote:

I am sorry that this comes so late, but I found severe problems in lyx2lyx
which occur for 2.1 => 2.0 conversion while testing my fix for bug #9069.
If you do the roundtrip 2.0 => 2.1 => 2.0 for the 2.0.8 user guide, you get
a document with invalid header settings and data loss where argument and
index insets are mixed. I fixed these two problems at
http://www.lyx.org/trac/changeset/2fe07e1fe1e/lyxgit and
http://www.lyx.org/trac/changeset/5710f68c340/lyxgit.

What to do now? These fixes as well as
http://www.lyx.org/trac/changeset/cacd2a041d2/lyxgit and
http://www.lyx.org/trac/changeset/52d25886131/lyxgit should go to 2.1.1.
Richard, is this OK?


Yes, those look good.


I also think that the final 2.0.x release should have them. I know that
this would create much additional work, since 2.0.8 is already tagged and
packaged (and therefore can't be changed anymore), but I don't think that
it is acceptable to tell people that it can read 2.1 files if in fact
these files will not be converted correctly in most cases.


I'm inclined to agree. It would mean re-packaging for everyone, but it 
shouldn't be too bad. Other opinions?



The question is of course how to avoid such bugs in the future, and I
believe that we need automated lyx2lyx roundtrip tests: Such tests would
have found the problems.


That would be a good idea.

Richard

Re: lyx2lyx bug

[Richard Heck]

On 04/24/2014 02:47 PM, Georg Baum wrote:

Richard Heck wrote:


This is close to right, but the problem is in the conversion of layouts.
It's fine not to quote the names. Look at e.g. logicalmkup.module. Mone
of the InsetLayout names are quoted, yet they work fine. The problem 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 of this at 7e1541dd. The module on which it failed was 
actually ill-formed, but there was the issue about quoted names, and I 
simplified and sped up the code a bit.


Richard

Re: severe lyx2lyx problem for 2.1 => 2.0 conversion

[Pavel Sanda]

Richard Heck wrote:
> I'm inclined to agree. It would mean re-packaging for everyone, but it 
> shouldn't be too bad. Other opinions?

We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.
Pavel

Re: severe lyx2lyx problem for 2.1 => 2.0 conversion

[Richard Heck]

On 04/25/2014 06:48 PM, Pavel Sanda wrote:

Richard Heck wrote:

I'm inclined to agree. It would mean re-packaging for everyone, but it
shouldn't be too bad. Other opinions?

We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.


Yes, that's true.

rh

Re: severe lyx2lyx problem for 2.1 => 2.0 conversion

[Pavel Sanda]

Richard Heck wrote:
> On 04/25/2014 06:48 PM, Pavel Sanda wrote:
>> Richard Heck wrote:
>>> I'm inclined to agree. It would mean re-packaging for everyone, but it
>>> shouldn't be too bad. Other opinions?
>> We should have 2.0.8.1 (or 2.0.9), 2.0.8 packages are already in the wild.
>
> Yes, that's true.

If the question was whether we should repackage at all then I think yes as 
well. P

Re: severe lyx2lyx problem for 2.1 => 2.0 conversion

[Pavel Sanda]

Georg Baum wrote:
> a document with invalid header settings and data loss where argument and 
> index insets are mixed. I fixed these two problems at 

BTW how often this dataloss happens - only if index inset is present?
(I ask whether immediate 2.1.(0.)1 release is needed or we can wait weeks...)

Pavel

Shortcuts for 'post' arguments

[aparsloe]

The Alt+A 1, etc. shortcuts  for custom inset arguments are a real boon. 
However, I note that a 'post' argument, following the main argument, 
doesn't get a shortcut, which is a pity. Is this oversight or are there 
technical reasons preventing the extension of shortcuts to 'post' arguments?


Andrew