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 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 hard for your but at least in my installer I include eLyXer as default HTML
converter. But I can also understand that other users prefer tex4ht.
The scripts folder is not trivial to find,
That's not true. For example to install custom layouts, the user have to copy the files to the
layouts folder. I've never heard that people failed to do this.
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.
I don't understand your point. I want to have eLyXer integrated to LyX in the long run. For now we
don't integrate it until our own LyX fileformat refactoring is done. But anyway, eLyXer is designed
for LyX and cannot be used by any other fileformat. So what is wrong treating it as just another
script in our scripts folder?
> 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%).
What would be the advantage? For me as packager it only makes life harder without any benefit
because eLyXer would do the same job it is designed for: Converting LyX to HTML files.
regards Uwe
