Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Alex Fernandez
2009/9/4 Uwe Stöhr : > Yes he is. eLyXer is not yet part of LyX and thus it depends on the user > what converter he wants to use/install. Installing your own programs > requires to read the documentation of the new program. Therefore eLyXer > needs to describe this not LyX. > I know that this sound

Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Uwe Stöhr
Alex Fernandez schrieb: As long as eLyXer is not part of LyX, it won't appear in the LyX documentation. Otherwise I would also have to describe how to set up tex4ht and the like. Then how is the user supposed to know where to place elyxer.py so that LyX can recognize it? Yes he is. eLyXer is

Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Alex Fernandez
2009/9/4 Uwe Stöhr : >> This should be documented somewhere... Probably both in eLyXer >> documentation and LyX documentation. > > As long as eLyXer is not part of LyX, it won't appear in the LyX > documentation. Otherwise I would also have to describe how to set up tex4ht > and the like. Then how

Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Uwe Stöhr
Alex Fernandez schrieb: Note that elyxer.py must now be in LyX's scripts folder. This should be documented somewhere... Probably both in eLyXer documentation and LyX documentation. As long as eLyXer is not part of LyX, it won't appear in the LyX documentation. Otherwise I would also have to

Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Alex Fernandez
Hi José, 2009/9/4 José Matos : > On Thursday 03 September 2009 Uwe Stöhr wrote: >> Alex Fernandez schrieb: >> >>  elyxer.py --directory $r $i $o > > At least in shell for this to work you would need to use: > elyxer.py --directory "$r" "$i" "$o" Actually LyX replaces $i by "Intro.lyx", with quote

Re: [OT] eLyXer and Windows command line arguments

2009-09-04 Thread Alex Fernandez
2009/9/4 Uwe Stöhr : > I found the bug: to handle paths with spaces, python files need to be called > with the option -tt. > That's what we already do for all python scripts. I applied a patch to do > this also for eLyXer: > http://www.lyx.org/trac/changeset/31265 That was fast. > Note that elyxe

Re: [OT] eLyXer and Windows command line arguments

2009-09-03 Thread José Matos
On Thursday 03 September 2009 Uwe Stöhr wrote: > Alex Fernandez schrieb: > >> elyxer.py --directory $r $i $o At least in shell for this to work you would need to use: elyxer.py --directory "$r" "$i" "$o" so that if the expanding variables has an empty space the arguments will be self-contained.

Re: [OT] eLyXer and Windows command line arguments

2009-09-03 Thread Uwe Stöhr
Alex Fernandez schrieb: elyxer.py --directory $r $i $o and if the directory $r contains spaces, eLyXer fails to parse the parameter set correctly. I found the bug: to handle paths with spaces, python files need to be called with the option -tt. That's what we already do for all python script

Re: [OT] eLyXer and Windows command line arguments

2009-09-03 Thread Alex Fernandez
Hi again, 2009/9/1 Alex Fernandez : > Uwe Stöhr and I are trying to debug a weird issue with eLyXer that > appears only on Windows, and only on certain machines. In these cases > it appears that eLyXer 0.27 is not able to parse directories with > spaces, while on other similar machines it works pe

[OT] eLyXer and Windows command line arguments

2009-09-01 Thread Alex Fernandez
Hi list, Uwe Stöhr and I are trying to debug a weird issue with eLyXer that appears only on Windows, and only on certain machines. In these cases it appears that eLyXer 0.27 is not able to parse directories with spaces, while on other similar machines it works perfectly. The conversion is done fro