On Thursday 01 August 2002 10:49, Jean-Marc Lasgouttes wrote: > > Will symbolic links work under cygwin?
Good question. > Dekel> (perhaps lyxconvert.py should be renamed to lyxconvert?) > > A problem we have with scripts is that the python (or perl) > interpreter will not be at the same place on different systems. I'd > like to avoid to create all the scripts from configure like we do for > reLyX. What about the present solution: #!/usr/bin/env python Do you know any system where this fails? > For running scripts from inside lyx, a solution would be to rely on > script extension to know how to invike it: for example, lyxconvert.py > would be invoked as > python lyxconvert.py But python lyx2lyx will works as well, you don't need the extension. The knowleadge present in the extension should (could) be somewhere else. > Also, the calling code could arrange to define a few variables like > LYX_DIR, or whatever can be useful for the script. As an example > reLyXmain.pl could be invoked with LYX_DIR and PACKAGE set to the > right values, so that the script reLyX is not needed. I do not know > whether lyx2lyx will need to find lyx data directory in this way, > though. Since I added that code to reLyX this shouldn't ever be a problem to lyx2lyx. :-) > However, this would not work from inside lyx. A solution would be to > run them from lyx, like > lyx --run-script reLyXmain.pl > > This is not a very satisfactory solution, but we need to find a way to > make our scripts portable. One other question, does reLyX has internationalization? I have moved all the error, and warnings, messages to a single file to easy that possibility. I have seen also pygettext, but that seems to be only present in python 2.2 > JMarc -- José Abílio
