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

[Philip Nienhuis]

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

Markus,
No i'm not at all opposed to fixing io for the time being. But it'll have to
be fixed for all affected interfaces, not just OCT.
Later this week I'll look into that.
FYI, fixing OF packages ahead of core releases while keeping backward
compatibility is merely business-as-usual :-)

Some other background that may be relevant:
At OctConf 2017 I spoke with JWE about moving spreadsheet + XML I/O to core
Octave (an old wish of him, see 
http://octave.1599824.n4.nabble.com/Spreadsheet-support-in-core-Octave-instead-of-io-package-tt4666947.html#a4666955
and
https://lists.gnu.org/archive/html/octave-maintainers/2015-05/msg00074.html).

At OctConf 2017 I hoped it could happen around (last) June. Well it now looks
like that'll be a bit later... :-)

One thing I've been preparing for a.o. that move to core, is eliminating
duplicate code. We now have various xls....m functions doing similar things as
ods....m counterparts; some time ago I've combined them and made the one just
a wrapper for the other. In the mean time io package and core development have
continued so this needs to be merged. I think any patches for tackling zip
functions would need to be adapted to the merged functions.


    _______________________________________________________

Reply to this item at:

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

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