Uwe Stöhr wrote:
TechTonics wrote:
Joost's version of LyX1.4.2 created a subset of Python2.4.3
and installed it in a sub-directory of LyX even though I had
system-wide Python2.4.3 installed and in Windows Path.
This is then a bug. Python should only be installed when it isn't
already on the system. This bug is not in my installer.
The LyX local subset Python failed to run the script, TeXFiles.py,
and as a result "Tex Information" failed to populate.
#!/usr/bin/env python -tt
# -*- coding: iso-8859-15 -*-
Your script edits the ^15 to a 1, and is a workaround for the
script to produce content for "Tex Information".
This is a known bug of LyX 1.4.2. The encoding of the python files is
now fixed and I used the fixed versions for the installer release.
SH: System Python ran that script without any fixing, so that
means Joost's local Python installed directory isn't fully
functional. Because you can modify the script so that the
shortcoming is not apparent is a workaround not a fix, IMO.
Anyway, I saw that your installer installs and uses python*
but apparently deletes these files later without giving the
impression that a local lyx python sub-dir fully works.
Thanks for the hint. But it is listed in the changelog. The readmes
don't cover minor problems of LyX, only general ones.
But I think for new users, including a lyx.ico in Resources ...
There should be a "lyx.ico" in LyX's bin directory. The missing icon
will hopefully be fixed for the next LyX release.
Yes, I found lydia.ico in the bin directory, I don't know how
I could have missed it. The Joost version does install with an
icon so he must have found a fix... anyway a small matter.
I like your python treatment.
You wouldn't happen to know if SET LC_ALL=en_EN from
lyx.bat could have any impact on .eps image conversion?
Thank you,
Stephen
