[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: Tue, 18 Jul 2017 16:10:43 -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 #73, bug #51203 (project octave):

I pushed the patch in comment #69 as well, thanks.

What shall we do with this bug report?
By the end of next week I'll be away for 3 weeks and until then I have little
time left to devote to Octave.

* If you think the unicode issues are solved we can at least adapt the title.

* Corrupted .xlsx:
That may have been caused (in part or completely) by the (lack of) unicode
conversion too, I hit that several times myself.

As to Infozip and "cd": I know the issue is real but rare, and chasing it down
has shown to be quite hard.

In the original bug report Andrey states that it is the COM interface that
gave him errors. probably that issue is not so much that the file is corrupt
but rather that is has the wrong extension, or contents => Excel stubbornly
creates .xlsx files even if the filename extension is .xls (an Excel bug if
you ask me).
That reminds me of the fact that the default file extension currently still is
.xls. But now that most people have MS-Office >= 2007 .xlsx is a better
default. So I just changed that:


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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