Skip Menu |

This queue is for tickets about the OpenOffice-OODoc CPAN distribution.

Report information
The Basics
Id: 57330
Status: rejected
Priority: 0/
Queue: OpenOffice-OODoc

People
Owner: Nobody in particular
Requestors: GNUSTAVO [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: getTableText misses some cells unless I call normalizeSheet
Hi, I'm using OpenOffice::OODoc version 2.236 (which isn't available in the 'Broken in' field) and Perl 5.10.0. If you run the attached script (table.pl) passing to it the name of the attached spreadsheet (table.ods) you will notice that before normalization the getTableText routine gets 10 cells for the first row and only 9 for the second. After normalization it gets 10 cells for each. The cell it doesn't get is the F2. Note that column F cells have a validation allowing just a list of values. I guess this has something to do with the problem. I read the normalizeSheet documentation but I confess that I didn't understand if it's just an optimization or if it's required to guarantee the correct access to the table.
Subject: table.ods
Download table.ods
application/vnd.oasis.opendocument.spreadsheet 8.4k

Message body not shown because it is not plain text.

Subject: table.pl
#!/usr/bin/perl use strict; use warnings; use OpenOffice::OODoc; use Data::Dumper; my $file = shift or die; my $ods = odfDocument(file => $file, part => 'content') or die "Cannot open file $file\n"; printf "%d, %d, %d\n", $ods->getTableSize(0), scalar($ods->getTableRows(0)); print "Before normalization:\n"; foreach my $row (($ods->getTableText(0))[0,1]) { print scalar @$row, ': ', Dumper($row); } $ods->normalizeSheet(0, 2, 10); print "\nAfter normalization:\n"; foreach my $row (($ods->getTableText(0))[0,1]) { print scalar @$row, ': ', Dumper($row); }
Le Dim 09 Mai 2010 19:53:45, GNUSTAVO a écrit : Show quoted text
> Hi, I'm using OpenOffice::OODoc version 2.236 (which isn't available in > the 'Broken in' field) and Perl 5.10.0.
What do you mean about "OpenOffice::OODoc version 2.236" ? This version doesn't exist yet. The latest version is 2.124.
While the documentation doesn't repeat that for *each* table-related method, table normalization is generally required as soon as a spreadsheet contains two or more contiguous and identical objects (like the D2, E2 and F2 cells in the provided example). It's not a bug; it's a known functional limitation of the API.
Subject: Re: [rt.cpan.org #57330] getTableText misses some cells unless I call normalizeSheet
Date: Mon, 10 May 2010 08:27:27 -0300
To: bug-OpenOffice-OODoc [...] rt.cpan.org
From: Gustavo Leite de Mendonça Chaves <gnustavo [...] cpan.org>
On Mon, May 10, 2010 at 6:05 AM, Jean-Marie Gouarné via RT < bug-OpenOffice-OODoc@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=57330 > > > Le Dim 09 Mai 2010 19:53:45, GNUSTAVO a écrit :
> > Hi, I'm using OpenOffice::OODoc version 2.236 (which isn't available in > > the 'Broken in' field) and Perl 5.10.0.
> > What do you mean about "OpenOffice::OODoc version 2.236" ? > > This version doesn't exist yet. The latest version is 2.124. >
Hmmm... I don't know. I was working at home in my Ubuntu 9.04 machine and I used the command 'pmvers OpenOffice::OODoc' to look up the version. I probably did something wrong. Sorry. Gustavo.
Subject: Re: [rt.cpan.org #57330] getTableText misses some cells unless I call normalizeSheet
Date: Mon, 10 May 2010 08:28:10 -0300
To: bug-OpenOffice-OODoc [...] rt.cpan.org
From: Gustavo Leite de Mendonça Chaves <gnustavo [...] cpan.org>
On Mon, May 10, 2010 at 6:30 AM, Jean-Marie Gouarné via RT < bug-OpenOffice-OODoc@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=57330 > > > While the documentation doesn't repeat that for *each* table-related > method, table normalization is generally required as soon as a > spreadsheet contains two or more contiguous and identical objects (like > the D2, E2 and F2 cells in the provided example). > > It's not a bug; it's a known functional limitation of the API. >
OK, then. Thank you very much. Gustavo.