2009/9/4 Uwe Stöhr <[email protected]>: > 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.
No problem at all. If it will help eLyXer users then I'm happy to document 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? I was envisioning an independent installation. But you are right, there is no problem in having elyxer.py in the scripts folder. > 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. Again, you are right. eLyXer 0.28 is out with all the changes; once you publish your installer I will update the documentation. Alex.
