[Octave-bug-tracker] [bug #62169] [octave forge](io) xlsread fails using UNO interface to process sheets with comma in name

[Philip Nienhuis]

Update of bug #62169 (project octave):

                  Status:               Confirmed => Ready For Test         

    _______________________________________________________

Follow-up Comment #2:

Fixing this bug became a bit complicated because LibreOffice seems to have
changed its Java-UNO bridge so that on Linux I now get 
"CE> IO error"
messages and on Windows loading spreadsheet files doesn't work at all anymore.
 IOW I got quite a bit distracted along the way.
A provisional fix is pushed here:
http://hg.code.sf.net/p/octave/io/rev/4673fea74b8e

Working on this bug got me wondering why you didn't encounter it on _"Linux
(Ubuntu 20.04.4), Octave 6.4, encoding utf-8, neither io version 2.6.3 nor
2.6."_ - the code that had to be fixed was clearly wrong (as long as commas in
sheet names are concerned).

Anyway, AFAICS on Linux this bug seems fixed. I have to wait until I get home
(abroad now) before I can test on my Windows 10 desktop machine where older
LibreOffice and Java releases are installed.

Please test the fixes: get  __UNO_spsh2oct__.m and __UNO_getusedrange__.m
-nomarkup+  from the repo:
http://hg.code.sf.net/p/octave/io/file/4673fea74b8e/inst/private/
...replace them with the ones in your Octave installation, try again, and
report back.
To find where the files reside, in Octave do:
cd (strrep (which ("xls2oct"), "xls2oct.m", "private"))

I still have to run a few other checks as regards this bug before this report
can be closed.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62169>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/