Hi,
> i have no opinion about it. note however that Uwe is currently the
> only one maintaining windows installers and if you break it on
> his setup you might break it on his installer also ;)
I tried to contact him but he was unable to confirm either way. From
what I have read his problem should _not_ happen on any machine with a
sane configuration (i.e. anyone not doing heavy development and trying
out things). It would probably be better to wait until he can test it,
but I wanted to make sure that the change made it into LyX 2.0.
The issue was essentially that when executing elyxer.py as a Python
script it did not understand the arguments passed, but tried to parse
it all as a big argument. However I tried on a very similar setup and
it worked for me. I have got no further reports from other Windows
users running eLyXer as a script, although the sample might not be
large.
> besides this i have one particular question about the code below:
> > + path, elyxer = checkProg('a LyX -> MS Word converter',
> > + ['elyxer.py --directory $$r $$i $$o', 'elyxer --html --directory
> > $$r
> > $$i $$o'],
> > + rc_entry = [ r'\converter lyx wordhtml "%%" ""' ])
> > + if elyxer.find('elyxer') >= 0:
> > + elyxerfound = True
> does elyxer do something specific for word output that we bump new target?
> we do this for htlatex which distinguishes xhtml output for openoffice
> and html for word. whats the point of doing it here?
Yes, it's exactly the same: XHTML for LyX "HTML" output and regular
HTML 4.0 (--html) for importing in Word.
Alex.
