|
From: | John W. Eaton |
Subject: | [Octave-bug-tracker] [bug #51203] xlswrite(...'com') output results in a corrupted .xlsx / unicode issues |
Date: | Fri, 14 Jul 2017 16:58:49 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #66, bug #51203 (project octave): I tried using the script in comment #65 and didn't see a problem. I'm using io 2.4.7 on a Windows system with a build of dev Octave (Octave hg id 5296657cde44) but I'm not sure what mxe-octave version. It was built around the beginning of May. My approach to debugging this problem would be to simplify the xlswrite function to the point where it just does the minimum to demonstrate the problem. Exactly what is xlswrite doing in this case? _______________________________________________________ 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] |