|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues |
Date: | Tue, 4 Jul 2017 14:25:53 -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 #54, bug #51203 (project octave): @Andrey and Markus: Good detective work, thanks. It sounds very convincing to me - I've always wondered why it is on systems with a fast HD / SSD that we see this bug; your explanation fits this observation perfectly: such systems finished the actual write operations before infozip itself is ready. I am not prepared (yet) to just apply your patch for the OCT interface: * All io pkg spreadsheet interfaces that rely on zip need a similar patch. * There's also UNO (AFAIK relying on gzip) that has similar issues. As I have a hard time believing that issues with zip / infozip are limited to the io package I'd suggest to bring this (= replacing infozip and/or fixing unpack.m) up in the maintainers ML. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?51203> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |