On 09/15/2009 07:44 PM, Alex Fernandez wrote:
When reading this I thought: "if there is a bug with elyxer.py and
windows that can be solved by using some elyxerbridge.py script, why is
this code not included in the original python script?"
Because it exists solely for use in LyX, and it is more user friendly if it is
already in place in its LyX folder. It saves a step for users, and makes life
easier for integrators.
JMarc, I don't know how you are going to feel about this, but I still
don't understand why they aren't just distributing the bridge thing with
elyxer. Why insist that it be distributed with LyX, when (a) only elyxer
users will need it (still a quite tiny proportion of LyX users, I would
suppose) and (b) it is only needed on some small and as yet undetermined
proportion of XP machines? The argument that distributing it with LyX
saves an extra step makes no sense to me. If it is included in elyxer,
then there's no extra step. Besides any of this, there is another
option, namely, that the bridge code be included in the Windows
installer, which (again) is the only place it is needed. Modulo,
perhaps, the issues on OSX, which I have not yet fully understood.
Waiving that, if this problem only arises on some XP machines and not
others, one might even suspect that the issue is misconfiguration,
corrupted software, or who knows what, in which case it isn't needed at
all. But I will again say that it is more than a little surprising if
this issue only arises with elyxer. Why don't we see these same problems
with other converters? That is especially true of this problem with
spaces in pathnames. Why is only elyxer not getting the right info? If
it were a general Windows issue, then surely you would also see it with
every other converter. Is it an issue with python? elyxer being the only
one that is written therein? If so, then maybe the solution ought to be
to upgrade the python being distributed.
I just don't myself see that this is yet being thought about correctly.
rh
