>>>>> "José" == José Abílio Oliveira Matos <[EMAIL PROTECTED]> writes:
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. José> What about the present solution: #!/usr/bin/env python Ah. I did not notice it... Note that you should always add a space after #! José> Do you know any system where this fails? I do not now, but a google search seems to propose this as a common trick. >> 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 José> But python lyx2lyx will works as well, you don't need the José> extension. The knowleadge present in the extension should José> (could) be somewhere else. I mean that lyx runScript (or whatever name) method could use the extension to guess the interpreter it should use. I am not sure yet it is a good idea, just a proposal. José> One other question, does reLyX has internationalization? I José> have moved all the error, and warnings, messages to a single José> file to easy that possibility. José> I have seen also pygettext, but that seems to be only present José> in python 2.2 I think we can worry about that later, but gettext support would certainly be nice. JMarc
