|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #53459] [octave forge] (io) 2.4.10 function xlsread, results in unexpected error reading Excel (xlsx) file |
Date: | Thu, 12 Apr 2018 16:04:58 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 |
Follow-up Comment #21, bug #53459 (project octave): @Werner: Thanks for testing, I'll look into the new <<Testcase3.xlsx>> file. >From what you write in comment #19 it looks to be due to unicode issues; that is a weakness in octave itself rather than the io package. But we'll see. I just fixed writing new sheets to your original 500V_SHORT.xlsx file; turned out I had most of the bookkeeping right, but I never had hit xlsx files with chartsheets and pivottables etc. (although I regularly use those at work - but I don't quite need let alone invoke Octave to analyze hours spent on projects by my colleagues). In the end it only required minor fixes. Another issue is that writing data into existing files screws up xl/calcChain.xml; I have no idea why, maybe I'll look into that later. Oh and I'll try pushing all the new fixes to sourceforge again; it's grown into a nice stack of csets right now :-) _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?53459> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |