2009/9/4 Uwe Stöhr <[email protected]>: >> 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 is the user supposed to know where to place elyxer.py so that LyX can recognize it? The scripts folder is not trivial to find, and unless eLyXer is bundled with LyX (or people know how to integrate both) nobody will be able to use it. I can add it to eLyXer documentation but it would be better to have it elsewhere. IMHO you gave the correct solution to the slightly wrong problem. eLyXer is supposed to be a standalone tool; as such it should work as long as it's on the execution path (somewhere in %PATH%). But then it is a Python script, so it needs the Python executable to run it. The problem we were seeing might be caused by executing the script directly: elyxer.py --directory $r $i $o instead of running it with Python: python elyxer.py --directory $r $i $o (the -tt option, we may deduce, is immaterial: it will probably work without it). But running it from Python directly requires, as you have correctly done, placing the script in a particular place. That is nice as an interim solution, but long term it would be better to make eLyXer a real standalone tool (e.g. with py2exe) and use that in the bin directory (or in the %PATH%). I will explore this alternate solution. > It think its time to raise the version number of eLyXer , e.g. to 0.5 ;-) Why not :) Once I am really happy with the tool I will release a 1.0. Alex.
