Ok I had saved the cmd file as unicode and lyx couldnt read it.

So it seems the cmd way of doing things still works.

THanks for the suggestions and sorry that as usual pilot error was the cause!

Geoff
----- Original Message ----- From: "Geoffrey Lloyd" <[EMAIL PROTECTED]> To: "Jean-Pierre Chretien" <[EMAIL PROTECTED]>; <lyx-users@lists.lyx.org>
Sent: Monday, July 25, 2005 4:27 PM
Subject: Re: tex2lyx


>
From: "Geoffrey Lloyd" <[EMAIL PROTECTED]>
To: <lyx-users@lists.lyx.org>
Subject: tex2lyx
Date: Mon, 25 Jul 2005 16:03:46 +0100

Anyone managed to get this working with 1.3.6-1 for Windows

I have followed the install instruction and also the instructions for activation from within Lyx which are provided on the wiki
and I keep getting an error saying

Cannot convert file

Error while executing
tex2lyx.cmd "filename.tex" "filename.lyx"

Run it from a console, the popup is not enough informative.

I don't think the cmd workaround is needed anymore if you patch the *.py files
of the lyx-1.4 distribution in C:/Program Files/LyX/resources/lyx2lyx:
lyx-1.3.6 will be able to read the converted files. I edited the tex2lyx wiki page in that line.

However tex2lyx needs the other LyX-1.4 files, so copying tex2lyx in C:/Program Files/LyX/bin remains hazardous (it worked for me on some layouts, but this is not a general rule).
So editing the PATH variable remains necessary.
Then a MinGW console is your friend :-)

--
Jean-Pierre




Ok I have run it from the command window. I am still using the command file work around, firstly because I think it is a far more friendly way of doing things but it appears that this is where the problem is.

I get the message

c:\folder>\@
'\s@' is not recognized as an internal or external command, operable program or batch file.

where the \ is in fact a small square (like the sort you get when word cant find a font). @ is the first line of the tex2lyx.cmd file. If I change the first character so the error message changes.

If I do not use the script, can I still use tex2lyx from within lyx or do I have to go back to the command line.

Geoff


Reply via email to