[Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues

[Philip Nienhuis]

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

@Markus

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
ago.


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:

  <http://savannah.gnu.org/bugs/?51203>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/