[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import fro
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import from xlsx named ranges ending in numbers |
Date: |
Tue, 15 Oct 2024 15:49:50 -0400 (EDT) |
Update of bug #66288 (group octave):
Status: Confirmed => In Progress
_______________________________________________________
Follow-up Comment #7:
OK thanks for answering to comment #4.
In the mean time I already have a fix along the lines of "best fix" in comment
#4 but until November I lack time for rigorous testing with all interfaces.
As to Excel docs and names, the reality is somewhat more relaxed than you
described. The largest column "number" in Excel is "XFD" (corresponding to
real column number 16384) and it turns out a Named range "XFD1" indeed isn't
accepted but "XFE1" is - at least with my Excel2016.
I have no idea (yet) how Apache POI, LibreOffice and related SW handle this.
About the list of named ranges in the file pointer - yes as soon as you enter
a Named range range, xls2oct.m or oct2xls.m will get the list of Named ranges
and add it to the xls pointer. So my reasoning when I first analyzed this bug
report was "why not do that right away when opening the file", to save
execution when invoking Named ranges. As it stands the execution flow in those
parts of the code could be more efficient :-) if not more robust as well.
I'm unsure what you mean to say in your last paragraph in comment #4; but as
regards scope, AFAICS in the expanded files and in the ECMA docs, each Named
range can explicitly refer to one worksheet only.
I noted that Excel seems to maintain stale Named ranges, apparently pointing
to deleted worksheets or so, I haven't investigated further. You'll recognize
them by the '!REF#' entries in the range columns of the list of Named ranges
in the xls pointer. Weeding out those could also make the whole show more
robust, that is, at the Octave side - I have no intentions to "fix" such an
.xlsx workbook.
Status => "In progress"
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66288>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, anonymous, 2024/10/03
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/04
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/04
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, anonymous, 2024/10/04
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/05
- [Octave-bug-tracker] [bug #66288] Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/06
- [Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/07
- [Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import from xlsx named ranges ending in numbers, Philip Nienhuis, 2024/10/15
- [Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import from xlsx named ranges ending in numbers, anonymous, 2024/10/15
- [Octave-bug-tracker] [bug #66288] [octave forge](io) Fails to import from xlsx named ranges ending in numbers,
Philip Nienhuis <=