See my comments in the text:
*/Steph/*
On 17/07/2011 00:39, Philip Nienhuis wrote:
Philip Nienhuis wrote:
Steph Bredenhann wrote:
Hi Philip
<snip>
octave-3.2.4:9> odsfinfo ('Protocol.ods')
warning: No support for OpenOffice.org .ods I/O
Aw, here's a message from odsopen ^^^^^^^^
error: matrix cannot be indexed with .
error: evaluating argument list element number 1
error: evaluating argument list element number 1
error: called from:
error: /usr/share/octave/packages/3.2/io-1.0.13/odsfinfo.m at line 87,
column 3
octave-3.2.4:9>
So as you can see, there are still errors reported.
Yep. Perhaps some bug in odsfinfo.m
Next try: do
ods = odsopen ('Protocol.ods', 0)
and report back.
If you do get a non-empty struct for ODS, do
odsclose (ods)
to close the connection.
(I didn't see messages from odsopen.m, a function called by odsfinfo.m
before line 87. I expect odsopen() would have complained if it couldn't
open your spreadsheet file.)
That's my wrong (it's a bit late), sorry.
odsopen() *did* complain (see above.)
First, update to io-1.0.14. The easiest is to download the io-1.0.14
pkg and just copy all m-files in its ./inst directory over the
identically named ones in io-1.0.13; the path was shown above:
>> error: /usr/share/octave/packages/3.2/io-1.0.13/
Done
Second, try with odfdom version 0.8.6 rather than 0.8.7. I think I
fixed a bug a while ago about odsopen's subfunc getodsinterfaces() not
properly recognizing or handling the version string of odfdom 0.8.7
Done, no difference
Third, you can try the jOpenDocument interface (it's just one jar file
to be added to the javaclasspath and it is also faster than odfdom
(but less flexible)).
Done
octave-3.2.4:5> javaclasspath
STATIC JAVA PATH
- empty -
DYNAMIC JAVA PATH
/usr/lib/java/odfdom.jar
/usr/lib/java/xercesImpl.jar
/usr/lib/java/jOpenDocument-1.2.jar
octave-3.2.4:6>
If none of these solutions work for you, we'll have to debug this more
or less in cooperation (as I have no 64 bit machine).
Now you going to test whether I am a novice?
You can start then by adding a "keyboard" statement just after L. 188
(after the line "odssupport = 0") in odsopen.m, and repeat what you
did (with odsfinfo). It'll trap in odsopen at the keyboard statement,
in debug mode (a sort of command line mode; you can quit with "dbquit").
odssupport = 0 is at Ln 163 in my code
I've added the statement:
octave-3.2.4:7> odsfinfo ('Protocol.ods')
error: structure has no member `POI'
error: evaluating argument list element number 1
error: evaluating argument list element number 1
error: called from:
error: /usr/share/octave/packages/3.2/io-1.0.13/odsopen.m at line 331,
column 3
error: /usr/share/octave/packages/3.2/io-1.0.13/odsopen.m at line 148,
column 19
error: /usr/share/octave/packages/3.2/io-1.0.13/odsfinfo.m at line 78,
column 6
octave-3.2.4:7>
Please report what value the variables
odsinterfaces
has (just type the name and copy/paste answer in mail)
octave-3.2.4:6> odsinterfaces
error: `odsinterfaces' undefined near line 6 column 1
octave-3.2.4:6>
(BTW it's after midnight here, tomorrow evening I'll pick up again)
Philip
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev