Skip Menu |

This queue is for tickets about the Spreadsheet-XLSX CPAN distribution.

Report information
The Basics
Id: 83399
Status: open
Priority: 0/
Queue: Spreadsheet-XLSX

People
Owner: Nobody in particular
Requestors: nightmedia [...] gmail.com
Cc:
AdminCc:

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



Subject: Issue with parsing spreadsheets exported by Excel::Writer::XLSX
Date: Sun, 17 Feb 2013 14:18:40 -0800
To: bug-Spreadsheet-XLSX [...] rt.cpan.org
From: Gheorghe Chesler <nightmedia [...] gmail.com>
In the Spreadsheet::XLSX there is a section where the contained value is flagged as: elsif (/^<v/) { $flag = 1; } elsif (/^<\/v/) { $flag = 0; } The row exported by Excel::Writer::XLSX contains the data as a string, and looks like this: <sheetData><row r="1"><c r="A1" s="1" t="inlineStr"><is><t>Email</t></is></c></row> Since the flag does not get set because there is no <v> tag, the values are not seen, and Spreadsheet::XLSX returns an empty data set. I added after the lines above the following elsif (/^<t\W/) { $flag = 1; } elsif (/^<\/t>/) { $flag = 0; } I extended a bit the regular expression to avoid matching other tags that begin with t, as I do not know whether the <t> tag could also have params. With these changes the Excel file is parsed correctly. I am attaching the test file for reference. yours, Gheorghe
Download data.xlsx
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet 5k

Message body not shown because it is not plain text.

From: exnadler [...] gmail.com
I also had a problem with this module when parsing simple files created with Excel::Writer::XLSX. With optimization enabled in Excel::Writer::XLSX, this module would return an empty set. I have attached the file which I had trouble parsing. I applied the fix suggested in this bug and I was able to parse my file. It would be fantastic if this module was updated with this fix. Thank you! Eric Nadler
Subject: test.xlsx
Download test.xlsx
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet 5k

Message body not shown because it is not plain text.

RT-Send-CC: exnadler [...] gmail.com
Hi Eric, Could you please let me know if the TRIAL version I recently uploaded fixes your problem? Thanks, Mike On Mon Oct 19 20:17:13 2015, exnadler@gmail.com wrote: Show quoted text
> I also had a problem with this module when parsing simple files > created with Excel::Writer::XLSX. With optimization enabled in > Excel::Writer::XLSX, this module would return an empty set. > > I have attached the file which I had trouble parsing. > > I applied the fix suggested in this bug and I was able to parse my > file. > > It would be fantastic if this module was updated with this fix. > > Thank you! > Eric Nadler
RT-Send-CC: exnadler [...] gmail.com
Hi Eric, Could you please let me know if the TRIAL version I recently uploaded fixes your problem? Thanks, Mike On Mon Oct 19 20:17:13 2015, exnadler@gmail.com wrote: Show quoted text
> I also had a problem with this module when parsing simple files > created with Excel::Writer::XLSX. With optimization enabled in > Excel::Writer::XLSX, this module would return an empty set. > > I have attached the file which I had trouble parsing. > > I applied the fix suggested in this bug and I was able to parse my > file. > > It would be fantastic if this module was updated with this fix. > > Thank you! > Eric Nadler
From: exnadler [...] gmail.com
Hi Mike, I didn't see a TRIAL version anywhere, but I did try the new version 0.15 and it did not fix my problem. Thanks, Eric On Fri Oct 30 10:27:30 2015, MIKEB wrote: Show quoted text
> Hi Eric, > > Could you please let me know if the TRIAL version I recently uploaded > fixes your problem? > > Thanks, > Mike > > On Mon Oct 19 20:17:13 2015, exnadler@gmail.com wrote:
> > I also had a problem with this module when parsing simple files > > created with Excel::Writer::XLSX. With optimization enabled in > > Excel::Writer::XLSX, this module would return an empty set. > > > > I have attached the file which I had trouble parsing. > > > > I applied the fix suggested in this bug and I was able to parse my > > file. > > > > It would be fantastic if this module was updated with this fix. > > > > Thank you! > > Eric Nadler