Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-11, Richard Heck wrote:
 M-L wrote:
 On Mon, 09 Mar 2009 17:34:24 -0400
 rgheck rgh...@bobjweil.com wrote:
 M-L wrote:
 rgheck rgh...@bobjweil.com wrote:

 As Jurgen said, export to 1.5.x should work on Windows, too. But
 you have to find the right file: FILENAME.lyx15.

 But maybe not many are so stupid and would look for the new version file
 by default, rather than assume the original is now altered?

The same effect can be achieved by a destination file choosing
dialogue (with the default file name and path pre-selected).
The added bonus is that you are able to modify the target
destination/name.

 If someone wants to file an enhancement request over at bugzilla about 
 this, and then cc me (rgh...@comcast.net),
 I'll see if I can get to it for 1.6.3. (We're frozen for 1.6.2, which
 should be out in a few days.)

I added the request for where to export also as choice from GUI 
to Bug # 4501 http://bugzilla.lyx.org/show_bug.cgi?id=4501
lyx -e  should have an option of where to export.

Maybe someone with right permission could change the topic to 
LyX should have an option of where to export.

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Pavel Sanda]

Guenter Milde wrote:
 Maybe someone with right permission could change the topic to 
 LyX should have an option of where to export.

or somebody with the right permissions could give long standing
contributors bigger rights in bugzilla.

pavel

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-11, Richard Heck wrote:
 M-L wrote:
 On Mon, 09 Mar 2009 17:34:24 -0400
 rgheck rgh...@bobjweil.com wrote:
 M-L wrote:
 rgheck rgh...@bobjweil.com wrote:

 As Jurgen said, export to 1.5.x should work on Windows, too. But
 you have to find the right file: FILENAME.lyx15.

 But maybe not many are so stupid and would look for the new version file
 by default, rather than assume the original is now altered?

The same effect can be achieved by a destination file choosing
dialogue (with the default file name and path pre-selected).
The added bonus is that you are able to modify the target
destination/name.

 If someone wants to file an enhancement request over at bugzilla about 
 this, and then cc me (rgh...@comcast.net),
 I'll see if I can get to it for 1.6.3. (We're frozen for 1.6.2, which
 should be out in a few days.)

I added the request for where to export also as choice from GUI 
to Bug # 4501 http://bugzilla.lyx.org/show_bug.cgi?id=4501
lyx -e  should have an option of where to export.

Maybe someone with right permission could change the topic to 
LyX should have an option of where to export.

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Pavel Sanda]

Guenter Milde wrote:
 Maybe someone with right permission could change the topic to 
 LyX should have an option of where to export.

or somebody with the right permissions could give long standing
contributors bigger rights in bugzilla.

pavel

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-11, Richard Heck wrote:
> M-L wrote:
>> On Mon, 09 Mar 2009 17:34:24 -0400
>> rgheck  wrote:
>>> M-L wrote:
 rgheck  wrote:

> As Jurgen said, export to 1.5.x should work on Windows, too. But
> you have to find the right file: FILENAME.lyx15.

>> But maybe not many are so stupid and would look for the new version file
>> by default, rather than assume the original is now altered?

The same effect can be achieved by a "destination file choosing"
dialogue (with the default file name and path pre-selected).
The added bonus is that you are able to modify the target
destination/name.

> If someone wants to file an enhancement request over at bugzilla about 
> this, and then cc me (rgh...@comcast.net),
> I'll see if I can get to it for 1.6.3. (We're frozen for 1.6.2, which
> should be out in a few days.)

I added the request for "where to export" also as choice from GUI 
to Bug # 4501 
"lyx -e  should have an option of where to export".

Maybe someone with right permission could change the topic to 
"LyX should have an option of where to export".

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Pavel Sanda]

Guenter Milde wrote:
> Maybe someone with right permission could change the topic to 
> "LyX should have an option of where to export".

or somebody with the right permissions could give long standing
contributors bigger rights in bugzilla.

pavel

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Richard Heck]

M-L wrote:

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck rgh...@bobjweil.com wrote:

  

M-L wrote:


On Mon, 09 Mar 2009 07:58:49 -0400
rgheck rgh...@bobjweil.com wrote:
  
  

As Jurgen said, export to 1.5.x should work on Windows, too. But
you have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in
windows. It seems that was the problem and I didn't know a new file
was generated, just thought the original was converted. I sent the
wrong file and therefore LyX produced the error message on my Linux
box.

  
  

Perhaps it'd be worth our issuing a message after the conversion,
saying what file has been exported.

rh



Or maybe for dummies like me - that: the new version file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

  
If someone wants to file an enhancement request over at bugzilla about 
this, and then cc me (rgh...@comcast.net), I'll see if I can get to it 
for 1.6.3. (We're frozen for 1.6.2, which should be out in a few days.)


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Richard Heck]

M-L wrote:

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck rgh...@bobjweil.com wrote:

  

M-L wrote:


On Mon, 09 Mar 2009 07:58:49 -0400
rgheck rgh...@bobjweil.com wrote:
  
  

As Jurgen said, export to 1.5.x should work on Windows, too. But
you have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in
windows. It seems that was the problem and I didn't know a new file
was generated, just thought the original was converted. I sent the
wrong file and therefore LyX produced the error message on my Linux
box.

  
  

Perhaps it'd be worth our issuing a message after the conversion,
saying what file has been exported.

rh



Or maybe for dummies like me - that: the new version file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

  
If someone wants to file an enhancement request over at bugzilla about 
this, and then cc me (rgh...@comcast.net), I'll see if I can get to it 
for 1.6.3. (We're frozen for 1.6.2, which should be out in a few days.)


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Richard Heck]

M-L wrote:

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck  wrote:

  

M-L wrote:


On Mon, 09 Mar 2009 07:58:49 -0400
rgheck  wrote:
  
  

As Jurgen said, export to 1.5.x should work on Windows, too. But
you have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in
windows. It seems that was the problem and I didn't know a new file
was generated, just thought the original was converted. I sent the
wrong file and therefore LyX produced the error message on my Linux
box.

  
  

Perhaps it'd be worth our issuing a message after the conversion,
saying what file has been exported.

rh



Or maybe for dummies like me - that: the "new version" file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

  
If someone wants to file an enhancement request over at bugzilla about 
this, and then cc me (rgh...@comcast.net), I'll see if I can get to it 
for 1.6.3. (We're frozen for 1.6.2, which should be out in a few days.)


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Uwe Stöhr wrote:
 Guenter Milde schrieb:

 As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
 and is easily overseen by a user, I propose to open a destination-chooser
 (save-file dialogue) with export. 

 I propose to export to name-lyx15.lyx instead to name.lyx15

This would be an improvement. But still I would like to be able to set the
destination path and filename from LyX.

Example 1: 

* Export name.lyx (1.6 format) to the usb-stick at
  /media/usbdisk/name.lyx (1.5 format).
* take the usb-stick home and edit name.lyx with my old LyX 1.5,
* open it without any renaming etc,
* save back to the usb-stick (still 1.5 format of course),
* open with LyX 1.6,
...

Example 2: 

* At Feierabend, Export name.lyx to 1.5 format but overwriting the
  original.
* Use some syncing software to move all modified files to the usb-stick.
* -- as in Example 1.

Example 3:

* Export name.lyx to HTML with TTH, save it as name-tth.html
* Export name.lyx to HTML with LaTeX2HTML, save it as name-l2h.html
* Export name.lyx to HTML with L4H, save it as name-l4h.html
* Compare the results and decide which to publish on the web (or import
  with Word or ...).

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Joe(theWordy)Philbrook]

,
It would appear that on Mar 9, Guenter Milde did say:

 On 2009-03-09, Joe(theWordy)Philbrook wrote:
 
  One of my computers is running lyx 1.6.1 on which I
  recently wrote a couple of documents. Then I had occasion
  to modify one of the .lyx files on a different linux box. 
  But the available version of lyx was only 1.5.6 and when I
  tried to open the document I was informed that it had been
  created by a different version of lyx. And that the
  lyx2lyx script had failed. sigh
 
 LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know
 how to handle the new format.

Yeah, that makes sense. Conversely then I expect when ver 1.6.1 opens a
document from ver 1.5.6, it recognizes the old format and converts it
so silently that I didn't know it had even run this lyx2lyx thingy.
 
  Is there a way to tell lyx 1.6.1 to save in an older lyx format?
 
 Yes. FileExportLyx and then choose the desired version.

Good. Then at least if I KNOW I'll need to access the durned thing
ahead of time... 

  OR is there a conversion script that can convert a 
  (lyx version 0.6.1).lyx  file into something lyx 1.5.6 can open???

 Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.
 
 You can 
 
 * upgrade to 1.5.7 (save but maybe not possible)
 * replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
   (on your own risk, backup the original),
 * place the lyx2lyx package in usr/local/, say and call by hand.  

I don't think the one from 1.5.7 can handle it else I wouldn't have
had the error that got me to start this thread. But if the one from
1.6.1 can be called by hand, AND doesn't depend on specific libraries
that are only installed on the Linux that has lyx 1.6.1, then It
might be smart to at least put a copy of it in my ~/bin on the other
linux installations... Then If I happen to forget to export after
editing with the one instance of lyx ver 1.6.1 I'll still be able to
access the document when I'm using a different linux box.  

  (For assorted reasons I multi-boot several versions of
   linux. On Both my desktop AND my laptop. I never really
   know ahead of time which one I'll be using when I find
   the time to work on a book I'm trying to write.) 

The biggest problem should be that I have about a half dozen .lyx files
that I open all at once via a script when I work on the story.  But
since that script finishes by backing up my .lyxfiles to a usbstick from
which I can import the latest changes to my laptop, then I suppose
that the version of the script on the linux with the lyx ver 1.6.1
could also mv ${filename}.lyx ${filename}-v161.lyx, then invoke
lyx2lyx to save the lyx 1.5.6 version as ${filename}.lyx... That way
my script will always open the 1.5.6 compatabe copy. 


NOTE: I just did a little testing and this can be made to work. But
it's not quite as simple as you described...

I found the lyx2lyx script and copied it's whole directory to a data
partiion. But when I ran:

cd ~/lyxstuff
/mnt/lyx2lyx/lyx2lyx -t 276 -o ${filename}.lyx ${filename}-v16.lyx

It coplained that /mnt/unicodesymbols wasn't there and output a zero
length ${filename}.lix file. But when I inserted all the non directory
files from /usr/share/lyx it worked.


-- 
|   ---   ___
|   0   -  Joe (theWordy) Philbrook
|   ^   J(tWdy)P
|~\___/~ jtw...@ttlc.net

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Uwe Stöhr wrote:
 Guenter Milde schrieb:

 As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
 and is easily overseen by a user, I propose to open a destination-chooser
 (save-file dialogue) with export. 

 I propose to export to name-lyx15.lyx instead to name.lyx15

This would be an improvement. But still I would like to be able to set the
destination path and filename from LyX.

Example 1: 

* Export name.lyx (1.6 format) to the usb-stick at
  /media/usbdisk/name.lyx (1.5 format).
* take the usb-stick home and edit name.lyx with my old LyX 1.5,
* open it without any renaming etc,
* save back to the usb-stick (still 1.5 format of course),
* open with LyX 1.6,
...

Example 2: 

* At Feierabend, Export name.lyx to 1.5 format but overwriting the
  original.
* Use some syncing software to move all modified files to the usb-stick.
* -- as in Example 1.

Example 3:

* Export name.lyx to HTML with TTH, save it as name-tth.html
* Export name.lyx to HTML with LaTeX2HTML, save it as name-l2h.html
* Export name.lyx to HTML with L4H, save it as name-l4h.html
* Compare the results and decide which to publish on the web (or import
  with Word or ...).

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Joe(theWordy)Philbrook]

,
It would appear that on Mar 9, Guenter Milde did say:

 On 2009-03-09, Joe(theWordy)Philbrook wrote:
 
  One of my computers is running lyx 1.6.1 on which I
  recently wrote a couple of documents. Then I had occasion
  to modify one of the .lyx files on a different linux box. 
  But the available version of lyx was only 1.5.6 and when I
  tried to open the document I was informed that it had been
  created by a different version of lyx. And that the
  lyx2lyx script had failed. sigh
 
 LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know
 how to handle the new format.

Yeah, that makes sense. Conversely then I expect when ver 1.6.1 opens a
document from ver 1.5.6, it recognizes the old format and converts it
so silently that I didn't know it had even run this lyx2lyx thingy.
 
  Is there a way to tell lyx 1.6.1 to save in an older lyx format?
 
 Yes. FileExportLyx and then choose the desired version.

Good. Then at least if I KNOW I'll need to access the durned thing
ahead of time... 

  OR is there a conversion script that can convert a 
  (lyx version 0.6.1).lyx  file into something lyx 1.5.6 can open???

 Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.
 
 You can 
 
 * upgrade to 1.5.7 (save but maybe not possible)
 * replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
   (on your own risk, backup the original),
 * place the lyx2lyx package in usr/local/, say and call by hand.  

I don't think the one from 1.5.7 can handle it else I wouldn't have
had the error that got me to start this thread. But if the one from
1.6.1 can be called by hand, AND doesn't depend on specific libraries
that are only installed on the Linux that has lyx 1.6.1, then It
might be smart to at least put a copy of it in my ~/bin on the other
linux installations... Then If I happen to forget to export after
editing with the one instance of lyx ver 1.6.1 I'll still be able to
access the document when I'm using a different linux box.  

  (For assorted reasons I multi-boot several versions of
   linux. On Both my desktop AND my laptop. I never really
   know ahead of time which one I'll be using when I find
   the time to work on a book I'm trying to write.) 

The biggest problem should be that I have about a half dozen .lyx files
that I open all at once via a script when I work on the story.  But
since that script finishes by backing up my .lyxfiles to a usbstick from
which I can import the latest changes to my laptop, then I suppose
that the version of the script on the linux with the lyx ver 1.6.1
could also mv ${filename}.lyx ${filename}-v161.lyx, then invoke
lyx2lyx to save the lyx 1.5.6 version as ${filename}.lyx... That way
my script will always open the 1.5.6 compatabe copy. 


NOTE: I just did a little testing and this can be made to work. But
it's not quite as simple as you described...

I found the lyx2lyx script and copied it's whole directory to a data
partiion. But when I ran:

cd ~/lyxstuff
/mnt/lyx2lyx/lyx2lyx -t 276 -o ${filename}.lyx ${filename}-v16.lyx

It coplained that /mnt/unicodesymbols wasn't there and output a zero
length ${filename}.lix file. But when I inserted all the non directory
files from /usr/share/lyx it worked.


-- 
|   ---   ___
|   0   -  Joe (theWordy) Philbrook
|   ^   J(tWdy)P
|~\___/~ jtw...@ttlc.net

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Uwe Stöhr wrote:
> Guenter Milde schrieb:

>> As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
>> and is easily overseen by a user, I propose to open a destination-chooser
>> (save-file dialogue) with export. 

> I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

This would be an improvement. But still I would like to be able to set the
destination path and filename from LyX.

Example 1: 

* Export name.lyx (1.6 format) to the usb-stick at
  /media/usbdisk/name.lyx (1.5 format).
* take the usb-stick home and edit name.lyx with my old LyX 1.5,
* open it without any renaming etc,
* save back to the usb-stick (still 1.5 format of course),
* open with LyX 1.6,
...

Example 2: 

* At Feierabend, Export name.lyx to 1.5 format but overwriting the
  original.
* Use some syncing software to move all modified files to the usb-stick.
* -- as in Example 1.

Example 3:

* Export name.lyx to HTML with TTH, save it as name-tth.html
* Export name.lyx to HTML with LaTeX2HTML, save it as name-l2h.html
* Export name.lyx to HTML with L4H, save it as name-l4h.html
* Compare the results and decide which to publish on the web (or import
  with Word or ...).

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Joe(theWordy)Philbrook]

,
It would appear that on Mar 9, Guenter Milde did say:

> On 2009-03-09, Joe(theWordy)Philbrook wrote:
> 
> > One of my computers is running lyx 1.6.1 on which I
> > recently wrote a couple of documents. Then I had occasion
> > to modify one of the .lyx files on a different linux box. 
> > But the available version of lyx was only 1.5.6 and when I
> > tried to open the document I was informed that it had been
> > created by a different version of lyx. And that the
> > lyx2lyx script had failed. 
 
> LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know
> how to handle the new format.

Yeah, that makes sense. Conversely then I expect when ver 1.6.1 opens a
document from ver 1.5.6, it recognizes the old format and converts it
so silently that I didn't know it had even run this lyx2lyx thingy.
 
> > Is there a way to tell lyx 1.6.1 to save in an older lyx format?
> 
> Yes. File>Export>Lyx and then choose the desired version.

Good. Then at least if I KNOW I'll need to access the durned thing
ahead of time... 

> > OR is there a conversion script that can convert a 
> > (lyx version 0.6.1).lyx  file into something lyx 1.5.6 can open???

> Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.
> 
> You can 
> 
> * upgrade to 1.5.7 (save but maybe not possible)
> * replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
>   (on your own risk, backup the original),
> * place the lyx2lyx package in usr/local/, say and call "by hand".  

I don't think the one from 1.5.7 can handle it else I wouldn't have
had the error that got me to start this thread. But if the one from
1.6.1 can be called by hand, AND doesn't depend on specific libraries
that are only installed on the Linux that has lyx 1.6.1, then It
might be smart to at least put a copy of it in my ~/bin on the other
linux installations... Then If I happen to forget to export after
editing with the one instance of lyx ver 1.6.1 I'll still be able to
access the document when I'm using a different linux box.  

  (For assorted reasons I multi-boot several versions of
   linux. On Both my desktop AND my laptop. I never really
   know ahead of time which one I'll be using when I find
   the time to work on a book I'm trying to write.) 

The biggest problem should be that I have about a half dozen .lyx files
that I open all at once via a script when I work on the story.  But
since that script finishes by backing up my .lyxfiles to a usbstick from
which I can import the latest changes to my laptop, then I suppose
that the version of the script on the linux with the lyx ver 1.6.1
could also" mv ${filename}.lyx ${filename}-v161.lyx, then invoke
lyx2lyx to save the lyx 1.5.6 version as ${filename}.lyx... That way
my script will always open the 1.5.6 compatabe copy. 


NOTE: I just did a little testing and this can be made to work. But
it's not quite as simple as you described...

I found the lyx2lyx script and copied it's whole directory to a data
partiion. But when I ran:

cd ~/lyxstuff
/mnt/lyx2lyx/lyx2lyx -t 276 -o ${filename}.lyx ${filename}-v16.lyx

It coplained that /mnt/unicodesymbols wasn't there and output a zero
length ${filename}.lix file. But when I inserted all the non directory
files from /usr/share/lyx it worked.


-- 
|   ---   ___
|   <0>   <->  Joe (theWordy) Philbrook
|   ^   J(tWdy)P
|~\___/~ <>

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Joe(theWordy)Philbrook wrote:

 One of my computers is running lyx 1.6.1 on which I recently wrote a
 couple of documents. Then I had occasion to modify one of the .lyx files 
 on a different linux box.  But the available version of lyx was only
 1.5.6 and when I tried to open the document I was informed that it had
 been created by a different version of lyx. And that the lyx2lyx script
 had failed. sigh

 I'm reasonably certain I hadn't used any new advanced features from
 ver 1.6.1 that ver 1.5.6 doesn't have. 
...
 So I was a bit surprised that version 1.5.6 couldn't open the resulting
 document.

LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know how
to handle the new format.

 Is there a way to tell lyx 1.6.1 to save in an older lyx format?

Yes. FileExportLyx and then choose the desired version.

 OR is there a conversion script that can convert a (lyx version 1.6.1).lyx  
 file into something lyx 1.5.6 can open???

Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.

You can 

* upgrade to 1.5.7 (save but maybe not possible)
* replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
  (on your own risk, backup the original),
* place the lyx2lyx package in usr/local/, say and call by hand.  

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

Joe(theWordy)Philbrook wrote:
 Is there a way to tell lyx 1.6.1 to save in an older lyx format?

FileExportLyX 1.5.x

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 08:35:40 +0100
Jürgen Spitzmüller juer...@spitzmueller.org wrote:

 Joe(theWordy)Philbrook wrote:
  Is there a way to tell lyx 1.6.1 to save in an older lyx format?
 
 FileExportLyX 1.5.x
 
 Jürgen

I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

No joy there at all.

Charlie
-- 
Registered Linux User:- 329524
***
Be true to your work, your word, and your
friend. ...Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
 windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

What exactly doesn't work?

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Siegfried Meunier-Guttin-Cluzel]

Since I often have this problem, I've found a workaround ( not a nice 
one, but it works when the formats aren't too different).

I simply change the number of the LyX format.
Open your file with a text editor and see the second line e. g.
\lyxformat 276
Change this number to match the number used on the old file format and 
it can work.

Of couse make backups, since it can be dangerous.

Hope it helps.
Siegfried.

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and 
shared this with us all:
--} Since I often have this problem, I've found a workaround ( not a nice
--} one, but it works when the formats aren't too different).
--} I simply change the number of the LyX format.
--} Open your file with a text editor and see the second line e. g.
--} \lyxformat 276
--} Change this number to match the number used on the old file format and
--} it can work.
--} Of couse make backups, since it can be dangerous.
--}
--} Hope it helps.
--} Siegfried.

Thank you.

I recall that I once had to change many documents from LyX 1.6.1 and deleted 
the first 6 or so lines at the top of the documents and replaced them with 6 
or so lines of the older version. I didn't realise it was this simple. 
Anything that works is a nice workaround.

So thank you.

Charlie

-- 
Registered Linux User:- 329524
***
I scarcely remember counting upon any Happiness—I look not for it if it be not 
in the present hour—nothing startles me beyond the Moment. The setting sun 
will always set me to rights—or if a Sparrow come before my Window I take 
part in its existence and pick about the Gravel. ---JOHN KEATS

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I recall that I once had to change many documents from LyX 1.6.1 and
 deleted the first 6 or so lines at the top of the documents and replaced
 them with 6 or so lines of the older version. I didn't realise it was this
 simple. Anything that works is a nice workaround.

Note that the possibility to corrupt your documents that way is high, and you 
might not even notice that in the first place. If you would give us some more 
details about _what_ fails, we might have a chance to fix the problem. Without 
further information, there's probably not much we can do.

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 11:21:45 +0100
Jürgen Spitzmüller juer...@spitzmueller.org wrote:

 M-L wrote:
  I recall that I once had to change many documents from LyX 1.6.1 and
  deleted the first 6 or so lines at the top of the documents and
  replaced them with 6 or so lines of the older version. I didn't
  realise it was this simple. Anything that works is a nice
  workaround.
 
 Note that the possibility to corrupt your documents that way is high,
 and you might not even notice that in the first place. If you would
 give us some more details about _what_ fails, we might have a chance
 to fix the problem. Without further information, there's probably not
 much we can do.
 
 Jürgen

I created some files on LyX 1.6.1 in windows XP and then went to:

File - then to Export - then to LyX 1.5.x 

With each of them.

Then emailed them as an attachment and later picked it up on my Linux
Debian Lenny machine and tried to open it with LyX 1.5.5

It wouldn't open but gave me the wrong version error message.

So I can't tell you what went wrong, it didn't and wouldn't show
anything but the error message, and when that was clicked off, just an
empty LyX screen with LYX on it?

So sorry, I can't give you some more details about _what_ fails,
because I don't know. The error message was nothing more than that. I
just know it doesn't work for me.

But I have done as stated above and changed the lines and that does
work.

I know - it doesn't help - it just works and the documents I have done
this with, I am still working on and they are fine. It would appear
that one way [the right way?] works for you and another works for me and
some other people?

Thank you,

Charlie

-- 
Registered Linux User:- 329524
***
The law will never make men free, it is men that have to make the law
free. .Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I created some files on LyX 1.6.1 in windows XP and then went to:

 File - then to Export - then to LyX 1.5.x

 With each of them.

 Then emailed them as an attachment and later picked it up on my Linux
 Debian Lenny machine and tried to open it with LyX 1.5.5

 It wouldn't open but gave me the wrong version error message.

Maybe you picked the wrong file? Note that Export does not overwrite the 
original document, but creates a new one with the suffix *.lyx15 (this is to 
preserve the native new features of 1.6, which will end up in ERT if you re-
open the 1.5 file).

You can check this by the format number. The exported file (to 1.5.x) has
\lyxformat 276

while the 1.6.x file has
\lyxformat 345

To open the *.lyx15 file, you might need to change the suffix back to *.lyx 
(some versions know this suffix, though).

 So I can't tell you what went wrong, it didn't and wouldn't show
 anything but the error message, and when that was clicked off, just an
 empty LyX screen with LYX on it?

 So sorry, I can't give you some more details about what fails,
 because I don't know. The error message was nothing more than that. I
 just know it doesn't work for me.

A minimal example file would help as well.

 But I have done as stated above and changed the lines and that does
 work.

 I know - it doesn't help - it just works and the documents I have done
 this with, I am still working on and they are fine. It would appear
 that one way [the right way?] works for you and another works for me and
 some other people?

No. The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).

So if it works for you, it is pure luck.

Jürgen

RE: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Vincent van Ravesteijn - TNW]

I created some files on LyX 1.6.1 in windows XP and then went to:

[...]

Then emailed them as an attachment and later picked it up on
my Linux Debian Lenny machine and tried to open it with LyX
1.5.5

I've heard this before. I think this was raised as a possible cause for
bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different
OS'es and lyx2lyx).

Vincent

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

Jürgen Spitzmüller wrote:
The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).


  
Let me just clarify what Jurgen means by this by giving an example. In 
LyX 1.5, a BibTeX inset would be written in the LyX file this way:


\begin_inset LatexCommand bibtex
bibfiles heck
options plain

\end_inset

In 1.6, it's like this:

\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles heck
options plain

\end_inset

There's a similar difference with citations and other command insets. 
Changing the format might work with these, if the parser happens to skip 
over the CommandInset bibtex bit that it doesn't recognize. But if 
that did work, it'd be by pure luck, and there are similar cases that 
won't work.


As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.


Richard

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

M-L wrote:

On Mon, 09 Mar 2009 07:58:49 -0400
rgheck rgh...@bobjweil.com wrote:
  
As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in windows.
It seems that was the problem and I didn't know a new file was
generated, just thought the original was converted. I sent the wrong
file and therefore LyX produced the error message on my Linux box.

  
Perhaps it'd be worth our issuing a message after the conversion, saying 
what file has been exported.


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, M-L wrote:
 On Mon, 09 Mar 2009 07:58:49 -0400
 rgheck rgh...@bobjweil.com wrote:

 As Jurgen said, export to 1.5.x should work on Windows, too. But you 
 have to find the right file: FILENAME.lyx15.

 Thank you for that. I will have to look for the right file in windows.
 It seems that was the problem and I didn't know a new file was
 generated, just thought the original was converted. I sent the wrong
 file and therefore LyX produced the error message on my Linux box.

As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 

(This would also solve the: Why do I have to remove/rename a html file
(with a separate tool) if I want to compare the output of different html
export tools? annoyance.)

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Uwe Stöhr]

Guenter Milde schrieb:


As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 


I propose to export to name-lyx15.lyx instead to name.lyx15

regards Uwe

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

Uwe Stöhr wrote:

Guenter Milde schrieb:

As FILENAME.lyx15 will not be recognised as a LyX file by most file 
managers
and is easily overseen by a user, I propose to open a 
destination-chooser
(save-file dialogue) with export. 


I propose to export to name-lyx15.lyx instead to name.lyx15

Yes, that's been discussed many times and probably ought to be done now. 
But I think it'd still be worth at least telling the user what file has 
been exported. This is supposed to be done in the status bar, but it 
seems instantly to get over-written with the buffer-export pdf type 
message.


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck rgh...@bobjweil.com wrote:

 M-L wrote:
  On Mon, 09 Mar 2009 07:58:49 -0400
  rgheck rgh...@bobjweil.com wrote:

  As Jurgen said, export to 1.5.x should work on Windows, too. But
  you have to find the right file: FILENAME.lyx15.
 
  
  Thank you for that. I will have to look for the right file in
  windows. It seems that was the problem and I didn't know a new file
  was generated, just thought the original was converted. I sent the
  wrong file and therefore LyX produced the error message on my Linux
  box.
 

 Perhaps it'd be worth our issuing a message after the conversion,
 saying what file has been exported.
 
 rh

Or maybe for dummies like me - that: the new version file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

Thanks again.
Charlie
-- 
Registered Linux User:- 329524
***
Mountains should be climbed with as little effort as possible and
without desire. The reality of your own nature should determine the
speed. If you become restless, speed up. If you become winded, slow
down. You climb the mountain in an equilibrium between restlessness and
exhaustion. Then, when you're no longer thinking ahead, each footstep
isn't just a means to an end but a unique event in
itself. ..Robert Pirsig

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Joe(theWordy)Philbrook wrote:

 One of my computers is running lyx 1.6.1 on which I recently wrote a
 couple of documents. Then I had occasion to modify one of the .lyx files 
 on a different linux box.  But the available version of lyx was only
 1.5.6 and when I tried to open the document I was informed that it had
 been created by a different version of lyx. And that the lyx2lyx script
 had failed. sigh

 I'm reasonably certain I hadn't used any new advanced features from
 ver 1.6.1 that ver 1.5.6 doesn't have. 
...
 So I was a bit surprised that version 1.5.6 couldn't open the resulting
 document.

LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know how
to handle the new format.

 Is there a way to tell lyx 1.6.1 to save in an older lyx format?

Yes. FileExportLyx and then choose the desired version.

 OR is there a conversion script that can convert a (lyx version 1.6.1).lyx  
 file into something lyx 1.5.6 can open???

Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.

You can 

* upgrade to 1.5.7 (save but maybe not possible)
* replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
  (on your own risk, backup the original),
* place the lyx2lyx package in usr/local/, say and call by hand.  

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

Joe(theWordy)Philbrook wrote:
 Is there a way to tell lyx 1.6.1 to save in an older lyx format?

FileExportLyX 1.5.x

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 08:35:40 +0100
Jürgen Spitzmüller juer...@spitzmueller.org wrote:

 Joe(theWordy)Philbrook wrote:
  Is there a way to tell lyx 1.6.1 to save in an older lyx format?
 
 FileExportLyX 1.5.x
 
 Jürgen

I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

No joy there at all.

Charlie
-- 
Registered Linux User:- 329524
***
Be true to your work, your word, and your
friend. ...Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
 windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

What exactly doesn't work?

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Siegfried Meunier-Guttin-Cluzel]

Since I often have this problem, I've found a workaround ( not a nice 
one, but it works when the formats aren't too different).

I simply change the number of the LyX format.
Open your file with a text editor and see the second line e. g.
\lyxformat 276
Change this number to match the number used on the old file format and 
it can work.

Of couse make backups, since it can be dangerous.

Hope it helps.
Siegfried.

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and 
shared this with us all:
--} Since I often have this problem, I've found a workaround ( not a nice
--} one, but it works when the formats aren't too different).
--} I simply change the number of the LyX format.
--} Open your file with a text editor and see the second line e. g.
--} \lyxformat 276
--} Change this number to match the number used on the old file format and
--} it can work.
--} Of couse make backups, since it can be dangerous.
--}
--} Hope it helps.
--} Siegfried.

Thank you.

I recall that I once had to change many documents from LyX 1.6.1 and deleted 
the first 6 or so lines at the top of the documents and replaced them with 6 
or so lines of the older version. I didn't realise it was this simple. 
Anything that works is a nice workaround.

So thank you.

Charlie

-- 
Registered Linux User:- 329524
***
I scarcely remember counting upon any Happiness—I look not for it if it be not 
in the present hour—nothing startles me beyond the Moment. The setting sun 
will always set me to rights—or if a Sparrow come before my Window I take 
part in its existence and pick about the Gravel. ---JOHN KEATS

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I recall that I once had to change many documents from LyX 1.6.1 and
 deleted the first 6 or so lines at the top of the documents and replaced
 them with 6 or so lines of the older version. I didn't realise it was this
 simple. Anything that works is a nice workaround.

Note that the possibility to corrupt your documents that way is high, and you 
might not even notice that in the first place. If you would give us some more 
details about _what_ fails, we might have a chance to fix the problem. Without 
further information, there's probably not much we can do.

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 11:21:45 +0100
Jürgen Spitzmüller juer...@spitzmueller.org wrote:

 M-L wrote:
  I recall that I once had to change many documents from LyX 1.6.1 and
  deleted the first 6 or so lines at the top of the documents and
  replaced them with 6 or so lines of the older version. I didn't
  realise it was this simple. Anything that works is a nice
  workaround.
 
 Note that the possibility to corrupt your documents that way is high,
 and you might not even notice that in the first place. If you would
 give us some more details about _what_ fails, we might have a chance
 to fix the problem. Without further information, there's probably not
 much we can do.
 
 Jürgen

I created some files on LyX 1.6.1 in windows XP and then went to:

File - then to Export - then to LyX 1.5.x 

With each of them.

Then emailed them as an attachment and later picked it up on my Linux
Debian Lenny machine and tried to open it with LyX 1.5.5

It wouldn't open but gave me the wrong version error message.

So I can't tell you what went wrong, it didn't and wouldn't show
anything but the error message, and when that was clicked off, just an
empty LyX screen with LYX on it?

So sorry, I can't give you some more details about _what_ fails,
because I don't know. The error message was nothing more than that. I
just know it doesn't work for me.

But I have done as stated above and changed the lines and that does
work.

I know - it doesn't help - it just works and the documents I have done
this with, I am still working on and they are fine. It would appear
that one way [the right way?] works for you and another works for me and
some other people?

Thank you,

Charlie

-- 
Registered Linux User:- 329524
***
The law will never make men free, it is men that have to make the law
free. .Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
 I created some files on LyX 1.6.1 in windows XP and then went to:

 File - then to Export - then to LyX 1.5.x

 With each of them.

 Then emailed them as an attachment and later picked it up on my Linux
 Debian Lenny machine and tried to open it with LyX 1.5.5

 It wouldn't open but gave me the wrong version error message.

Maybe you picked the wrong file? Note that Export does not overwrite the 
original document, but creates a new one with the suffix *.lyx15 (this is to 
preserve the native new features of 1.6, which will end up in ERT if you re-
open the 1.5 file).

You can check this by the format number. The exported file (to 1.5.x) has
\lyxformat 276

while the 1.6.x file has
\lyxformat 345

To open the *.lyx15 file, you might need to change the suffix back to *.lyx 
(some versions know this suffix, though).

 So I can't tell you what went wrong, it didn't and wouldn't show
 anything but the error message, and when that was clicked off, just an
 empty LyX screen with LYX on it?

 So sorry, I can't give you some more details about what fails,
 because I don't know. The error message was nothing more than that. I
 just know it doesn't work for me.

A minimal example file would help as well.

 But I have done as stated above and changed the lines and that does
 work.

 I know - it doesn't help - it just works and the documents I have done
 this with, I am still working on and they are fine. It would appear
 that one way [the right way?] works for you and another works for me and
 some other people?

No. The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).

So if it works for you, it is pure luck.

Jürgen

RE: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Vincent van Ravesteijn - TNW]

I created some files on LyX 1.6.1 in windows XP and then went to:

[...]

Then emailed them as an attachment and later picked it up on
my Linux Debian Lenny machine and tried to open it with LyX
1.5.5

I've heard this before. I think this was raised as a possible cause for
bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different
OS'es and lyx2lyx).

Vincent

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

Jürgen Spitzmüller wrote:
The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).


  
Let me just clarify what Jurgen means by this by giving an example. In 
LyX 1.5, a BibTeX inset would be written in the LyX file this way:


\begin_inset LatexCommand bibtex
bibfiles heck
options plain

\end_inset

In 1.6, it's like this:

\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles heck
options plain

\end_inset

There's a similar difference with citations and other command insets. 
Changing the format might work with these, if the parser happens to skip 
over the CommandInset bibtex bit that it doesn't recognize. But if 
that did work, it'd be by pure luck, and there are similar cases that 
won't work.


As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.


Richard

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

M-L wrote:

On Mon, 09 Mar 2009 07:58:49 -0400
rgheck rgh...@bobjweil.com wrote:
  
As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in windows.
It seems that was the problem and I didn't know a new file was
generated, just thought the original was converted. I sent the wrong
file and therefore LyX produced the error message on my Linux box.

  
Perhaps it'd be worth our issuing a message after the conversion, saying 
what file has been exported.


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Guenter Milde]

On 2009-03-09, M-L wrote:
 On Mon, 09 Mar 2009 07:58:49 -0400
 rgheck rgh...@bobjweil.com wrote:

 As Jurgen said, export to 1.5.x should work on Windows, too. But you 
 have to find the right file: FILENAME.lyx15.

 Thank you for that. I will have to look for the right file in windows.
 It seems that was the problem and I didn't know a new file was
 generated, just thought the original was converted. I sent the wrong
 file and therefore LyX produced the error message on my Linux box.

As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 

(This would also solve the: Why do I have to remove/rename a html file
(with a separate tool) if I want to compare the output of different html
export tools? annoyance.)

Günter

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[Uwe Stöhr]

Guenter Milde schrieb:


As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 


I propose to export to name-lyx15.lyx instead to name.lyx15

regards Uwe

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[rgheck]

Uwe Stöhr wrote:

Guenter Milde schrieb:

As FILENAME.lyx15 will not be recognised as a LyX file by most file 
managers
and is easily overseen by a user, I propose to open a 
destination-chooser
(save-file dialogue) with export. 


I propose to export to name-lyx15.lyx instead to name.lyx15

Yes, that's been discussed many times and probably ought to be done now. 
But I think it'd still be worth at least telling the user what file has 
been exported. This is supposed to be done in the status bar, but it 
seems instantly to get over-written with the buffer-export pdf type 
message.


rh

Re: lyx2lyx script failed... lyx 1.6.1 lyx 1.5.6

[M-L]

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck rgh...@bobjweil.com wrote:

 M-L wrote:
  On Mon, 09 Mar 2009 07:58:49 -0400
  rgheck rgh...@bobjweil.com wrote:

  As Jurgen said, export to 1.5.x should work on Windows, too. But
  you have to find the right file: FILENAME.lyx15.
 
  
  Thank you for that. I will have to look for the right file in
  windows. It seems that was the problem and I didn't know a new file
  was generated, just thought the original was converted. I sent the
  wrong file and therefore LyX produced the error message on my Linux
  box.
 

 Perhaps it'd be worth our issuing a message after the conversion,
 saying what file has been exported.
 
 rh

Or maybe for dummies like me - that: the new version file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

Thanks again.
Charlie
-- 
Registered Linux User:- 329524
***
Mountains should be climbed with as little effort as possible and
without desire. The reality of your own nature should determine the
speed. If you become restless, speed up. If you become winded, slow
down. You climb the mountain in an equilibrium between restlessness and
exhaustion. Then, when you're no longer thinking ahead, each footstep
isn't just a means to an end but a unique event in
itself. ..Robert Pirsig

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, Joe(theWordy)Philbrook wrote:

> One of my computers is running lyx 1.6.1 on which I recently wrote a
> couple of documents. Then I had occasion to modify one of the .lyx files 
> on a different linux box.  But the available version of lyx was only
> 1.5.6 and when I tried to open the document I was informed that it had
> been created by a different version of lyx. And that the lyx2lyx script
> had failed. 

> I'm reasonably certain I hadn't used any new advanced features from
> ver 1.6.1 that ver 1.5.6 doesn't have. 
...
> So I was a bit surprised that version 1.5.6 couldn't open the resulting
> document.

LyX 1.5.6 pre-dates 1.6.1 and hence the conversion script does not know how
to handle the new format.

> Is there a way to tell lyx 1.6.1 to save in an older lyx format?

Yes. File>Export>Lyx and then choose the desired version.

> OR is there a conversion script that can convert a (lyx version 1.6.1).lyx  
> file into something lyx 1.5.6 can open???

Yes, the lyx2lyx script of 1.6.x and 1.5.7 can do this.

You can 

* upgrade to 1.5.7 (save but maybe not possible)
* replace the lyx2lyx dir with the version from 1.6.x or 1.5.7.
  (on your own risk, backup the original),
* place the lyx2lyx package in usr/local/, say and call "by hand".  

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

Joe(theWordy)Philbrook wrote:
> Is there a way to tell lyx 1.6.1 to save in an older lyx format?

File>Export>LyX 1.5.x

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 08:35:40 +0100
Jürgen Spitzmüller  wrote:

> Joe(theWordy)Philbrook wrote:
> > Is there a way to tell lyx 1.6.1 to save in an older lyx format?
> 
> File>Export>LyX 1.5.x
> 
> Jürgen

I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

No joy there at all.

Charlie
-- 
Registered Linux User:- 329524
***
Be true to your work, your word, and your
friend. ...Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I've tried that but it doesn't work, or it doesn't work from LyX 1.6.1
> windows converting to LyX 1.5.x to be read by LyX 1.5.5 debian Lenny.

What exactly doesn't work?

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Siegfried Meunier-Guttin-Cluzel]

Since I often have this problem, I've found a workaround ( not a nice 
one, but it works when the formats aren't too different).

I simply change the number of the LyX format.
Open your file with a text editor and see the second line e. g.
\lyxformat 276
Change this number to match the number used on the old file format and 
it can work.

Of couse make backups, since it can be dangerous.

Hope it helps.
Siegfried.

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009, Siegfried Meunier-Guttin-Cluzel engaged keyboard and 
shared this with us all:
>--} Since I often have this problem, I've found a workaround ( not a nice
>--} one, but it works when the formats aren't too different).
>--} I simply change the number of the LyX format.
>--} Open your file with a text editor and see the second line e. g.
>--} \lyxformat 276
>--} Change this number to match the number used on the old file format and
>--} it can work.
>--} Of couse make backups, since it can be dangerous.
>--}
>--} Hope it helps.
>--} Siegfried.

Thank you.

I recall that I once had to change many documents from LyX 1.6.1 and deleted 
the first 6 or so lines at the top of the documents and replaced them with 6 
or so lines of the older version. I didn't realise it was this simple. 
Anything that works is a nice workaround.

So thank you.

Charlie

-- 
Registered Linux User:- 329524
***
I scarcely remember counting upon any Happiness—I look not for it if it be not 
in the present hour—nothing startles me beyond the Moment. The setting sun 
will always set me to rights—or if a Sparrow come before my Window I take 
part in its existence and pick about the Gravel. ---JOHN KEATS

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I recall that I once had to change many documents from LyX 1.6.1 and
> deleted the first 6 or so lines at the top of the documents and replaced
> them with 6 or so lines of the older version. I didn't realise it was this
> simple. Anything that works is a nice workaround.

Note that the possibility to corrupt your documents that way is high, and you 
might not even notice that in the first place. If you would give us some more 
details about _what_ fails, we might have a chance to fix the problem. Without 
further information, there's probably not much we can do.

Jürgen

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 9 Mar 2009 11:21:45 +0100
Jürgen Spitzmüller  wrote:

> M-L wrote:
> > I recall that I once had to change many documents from LyX 1.6.1 and
> > deleted the first 6 or so lines at the top of the documents and
> > replaced them with 6 or so lines of the older version. I didn't
> > realise it was this simple. Anything that works is a nice
> > workaround.
> 
> Note that the possibility to corrupt your documents that way is high,
> and you might not even notice that in the first place. If you would
> give us some more details about _what_ fails, we might have a chance
> to fix the problem. Without further information, there's probably not
> much we can do.
> 
> Jürgen

I created some files on LyX 1.6.1 in windows XP and then went to:

File - then to Export - then to LyX 1.5.x 

With each of them.

Then emailed them as an attachment and later picked it up on my Linux
Debian Lenny machine and tried to open it with LyX 1.5.5

It wouldn't open but gave me the wrong version error message.

So I can't tell you what went wrong, it didn't and wouldn't show
anything but the error message, and when that was clicked off, just an
empty LyX screen with LYX on it?

So sorry, I can't give you some more details about _what_ fails,
because I don't know. The error message was nothing more than that. I
just know it doesn't work for me.

But I have done as stated above and changed the lines and that does
work.

I know - it doesn't help - it just works and the documents I have done
this with, I am still working on and they are fine. It would appear
that one way [the right way?] works for you and another works for me and
some other people?

Thank you,

Charlie

-- 
Registered Linux User:- 329524
***
The law will never make men free, it is men that have to make the law
free. .Henry David Thoreau

***
Debian, just the best way to create magic
___

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Jürgen Spitzmüller]

M-L wrote:
> I created some files on LyX 1.6.1 in windows XP and then went to:
>
> File - then to Export - then to LyX 1.5.x
>
> With each of them.
>
> Then emailed them as an attachment and later picked it up on my Linux
> Debian Lenny machine and tried to open it with LyX 1.5.5
>
> It wouldn't open but gave me the wrong version error message.

Maybe you picked the wrong file? Note that Export does not overwrite the 
original document, but creates a new one with the suffix *.lyx15 (this is to 
preserve the native new features of 1.6, which will end up in ERT if you re-
open the 1.5 file).

You can check this by the format number. The exported file (to 1.5.x) has
\lyxformat 276

while the 1.6.x file has
\lyxformat 345

To open the *.lyx15 file, you might need to change the suffix back to *.lyx 
(some versions know this suffix, though).

> So I can't tell you what went wrong, it didn't and wouldn't show
> anything but the error message, and when that was clicked off, just an
> empty LyX screen with LYX on it?
>
> So sorry, I can't give you some more details about what fails,
> because I don't know. The error message was nothing more than that. I
> just know it doesn't work for me.

A minimal example file would help as well.

> But I have done as stated above and changed the lines and that does
> work.
>
> I know - it doesn't help - it just works and the documents I have done
> this with, I am still working on and they are fine. It would appear
> that one way [the right way?] works for you and another works for me and
> some other people?

No. The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).

So if it works for you, it is pure luck.

Jürgen

RE: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Vincent van Ravesteijn - TNW]

>I created some files on LyX 1.6.1 in windows XP and then went to:
>
>[...]
>
>Then emailed them as an attachment and later picked it up on
>my Linux Debian Lenny machine and tried to open it with LyX
>1.5.5

I've heard this before. I think this was raised as a possible cause for
bug http://bugzilla.lyx.org/show_bug.cgi?id=5822. (I mean the different
OS'es and lyx2lyx).

Vincent

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

Jürgen Spitzmüller wrote:
The method proposed by Siegfried works if (and only if) you do not use a 
new feature of LyX 1.6 and if you do not use a feature whose semantics was 
changed (which is the case for many features).


  
Let me just clarify what Jurgen means by this by giving an example. In 
LyX 1.5, a BibTeX inset would be written in the LyX file this way:


\begin_inset LatexCommand bibtex
bibfiles "heck"
options "plain"

\end_inset

In 1.6, it's like this:

\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles "heck"
options "plain"

\end_inset

There's a similar difference with citations and other "command" insets. 
Changing the format might work with these, if the parser happens to skip 
over the "CommandInset bibtex" bit that it doesn't recognize. But if 
that did work, it'd be by pure luck, and there are similar cases that 
won't work.


As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.


Richard

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

M-L wrote:

On Mon, 09 Mar 2009 07:58:49 -0400
rgheck  wrote:
  
As Jurgen said, export to 1.5.x should work on Windows, too. But you 
have to find the right file: FILENAME.lyx15.




Thank you for that. I will have to look for the right file in windows.
It seems that was the problem and I didn't know a new file was
generated, just thought the original was converted. I sent the wrong
file and therefore LyX produced the error message on my Linux box.

  
Perhaps it'd be worth our issuing a message after the conversion, saying 
what file has been exported.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Guenter Milde]

On 2009-03-09, M-L wrote:
> On Mon, 09 Mar 2009 07:58:49 -0400
> rgheck  wrote:

>> As Jurgen said, export to 1.5.x should work on Windows, too. But you 
>> have to find the right file: FILENAME.lyx15.

> Thank you for that. I will have to look for the right file in windows.
> It seems that was the problem and I didn't know a new file was
> generated, just thought the original was converted. I sent the wrong
> file and therefore LyX produced the error message on my Linux box.

As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 

(This would also solve the: "Why do I have to remove/rename a html file
(with a separate tool) if I want to compare the output of different html
export tools?" annoyance.)

Günter

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[Uwe Stöhr]

Guenter Milde schrieb:


As FILENAME.lyx15 will not be recognised as a LyX file by most file managers
and is easily overseen by a user, I propose to open a destination-chooser
(save-file dialogue) with export. 


I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

regards Uwe

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[rgheck]

Uwe Stöhr wrote:

Guenter Milde schrieb:

As FILENAME.lyx15 will not be recognised as a LyX file by most file 
managers
and is easily overseen by a user, I propose to open a 
destination-chooser
(save-file dialogue) with export. 


I propose to export to "name-lyx15.lyx" instead to "name.lyx15"

Yes, that's been discussed many times and probably ought to be done now. 
But I think it'd still be worth at least telling the user what file has 
been exported. This is supposed to be done in the status bar, but it 
seems instantly to get over-written with the "buffer-export pdf" type 
message.


rh

Re: lyx2lyx script failed... lyx 1.6.1 >>lyx 1.5.6

[M-L]

On Mon, 09 Mar 2009 17:34:24 -0400
rgheck  wrote:

> M-L wrote:
> > On Mon, 09 Mar 2009 07:58:49 -0400
> > rgheck  wrote:
> >   
> >> As Jurgen said, export to 1.5.x should work on Windows, too. But
> >> you have to find the right file: FILENAME.lyx15.
> >>
> >> 
> > Thank you for that. I will have to look for the right file in
> > windows. It seems that was the problem and I didn't know a new file
> > was generated, just thought the original was converted. I sent the
> > wrong file and therefore LyX produced the error message on my Linux
> > box.
> >
> >   
> Perhaps it'd be worth our issuing a message after the conversion,
> saying what file has been exported.
> 
> rh

Or maybe for dummies like me - that: the "new version" file has
been created?

But maybe not many are so stupid and would look for the new version file
by default, rather than assume the original is now altered?

Thanks again.
Charlie
-- 
Registered Linux User:- 329524
***
Mountains should be climbed with as little effort as possible and
without desire. The reality of your own nature should determine the
speed. If you become restless, speed up. If you become winded, slow
down. You climb the mountain in an equilibrium between restlessness and
exhaustion. Then, when you're no longer thinking ahead, each footstep
isn't just a means to an end but a unique event in
itself. ..Robert Pirsig

***
Debian, just the best way to create magic
___