Hi Jean-Marc, On Tue, Sep 15, 2009 at 2:39 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > I have not followed the tread well enough to know whether the real > problem has been stated somwhere, but it is indeed the point from where > we should start.
Ok, let's start again. By the way, this problem was already explained to the list some days ago: http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg154337.html > When reading this I thought: "if there is a bug with elyxer.py and > windows that can be solved by using some elyxerbridge.py script, why is > this code not included in the original python script?" Because it exists solely for use in LyX, and it is more user friendly if it is already in place in its LyX folder. It saves a step for users, and makes life easier for integrators. > Reading the first message of this thread, one answer that comes to mind > is the elyxer is now only a library, without any user-side script, and > that therefore you want to distribute a script with LyX. Did I get it > right? In this case I am a bit puzzled, because such a script does > belong with the library. More or less: eLyXer is now distributed both as a library and as a script, so the users can choose how they want to install it. elyxerbridge is not a user-side script, but a LyX-side script. > Could you enlighten me? Sure, I can try. When LyX runs eLyXer it wants to execute the following command: > elyxer.py --directory "directory path" "input file.lyx" "output file.html" This means that elyxer.py has to be an executable file (on Linux and Mac OS X) or have a file association with the Python executable file (on Windows). But on some instances of Windows XP doing it this way causes eLyXer to receive the parameters without quotes: > elyxer.py --directory directory path input file.lyx output file.html so it is impossible for it to deal with spaces in directories. Alex.
