On Jun 7, 9:22 pm, "pythonwin pythonwin" <pythonwin...@gmail.com>
wrote:
> image.py
> 1KDownload
The problem is not related to "Protection". The simple no-protection
image.py from the examples directory of the pyExcelerator distribution
has the same problem:
[Windows XP Pro SP 2, Python 2.5.1, OOo Calc 2.1, Gnumeric 1.7.6,
Excel 2003]
1. The output XLS file is displayed correctly by Excel but not by OOo
and Gnumeric.
2. After opening by Excel and saving a copy: the Excel-saved file is
displayed correctly by OOo and Gnumeric.
Looks like Excel is tolerating aberration(s) but OOo and Gnumeric
aren't.
TO DO:
* Report problem to OOo and Gnumeric
* Examine dumps of the 2 XLS files to determine the _essential_
difference(s)
* Read Microsoft & OOo docs
* Examine source code of OOo and Gnumeric
* Determine minimal set of sufficient changes to pyExcelerator and
xlwt [same code; I haven't touched it]
* Python 2.5 issues four deprecation warnings (passing a float to a H-
format (unsigned 16-bit integer) item in struct.pack) -- should
determine whether to round down / up / nearest and then pass as int
Looks like a job for one or more cold wet Sunday afternoons to me ...
any volunteers with a critical need and/or a surfeit of cold wet
Sunday afternoons?
Cheers,
John