[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues
Date: Wed, 5 Jul 2017 17:46:11 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46

Follow-up Comment #60, bug #51203 (project octave):


As to other affected interfaces, I'll sort that out (again).
A notable example is UNO (invoking LibreOffice behind the scenes using a
Java-UNO bridge). LibreOffice invokes a built-in zip procedure to unzip/zip
.ods and .xlsx files, and it was with UNO that I first hit this bug some years

As to move to core:
I doubt if all of io (spreadsheet & XML) can be moved to core; I think only
XML and the OCT spreadsheet interface will do.
The COM and Java-based interfaces could/should probably be left behind in a
weeded-out io package. COM relies on Excel itself + the windows package so
that is obviously out-of-the-question (although COM is a "system library" in
GPL terms). Furthermore most octave devs don't care much for Java and if we
include Java-based interfaces we'd introduce new dependencies.

AFAICS most of the required preparatory work has already been done, I need to
polish and update it.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]