On 20/10/10 2:46 PM, "Les Mikesell" <lesmikesell@xxxxxxxxx> wrote:
> On 10/20/2010 3:49 PM, Kahlil Hodgson wrote:
>> On 10/19/2010 09:13 AM, Les Mikesell wrote:
>> ...
>>> I haven't had much luck with
>>> perl-Spreadsheet-ParseExcel (and find it odd that yum prefers the .32
>>> version from epel over .57 from rpmforge anyway). Is the current CPAN
>>> version better?
>> ...
>>> Needs to deal with both xls and xlsx formats, the odd characters that
>>> are confused with quotes even after csv conversion, numbers with $'s and
>>> commas embedded, excel's date formatting nonsense, etc.
>>
>> Looking at the changelog, version .57 of perl-Spreadsheet-ParseExcel
>> fixes some of the above issues. Not clear from the above whether you
>> have tried it or not. The developers would probably be very interested
>> in any examples that break the parser.
>
> I just went as far as seeing it wouldn't take .xlsx (2007+ default
> format). It does look like the rpmforge .57 version will accept the
> .xls format file, although I think it seems slower than loading excel
> and doing a 'save as' to get the csv. For numbers, cell->unformatted()
> would give a real number instead of having to yank the commas out of the
> csv or $cell->value() versions, but dates don't look like what sql wants
> either way.
Les,
You might want to look at Spreadsheet::XLSX:
http://search.cpan.org/~dmow/Spreadsheet-XLSX-0.13-withoutworldwriteables/li
b/Spreadsheet/XLSX.pm
It can read XLSX files from a quick read of the CPAN page.
--
Gary L. Greene, Jr.
IT Operations
Minerva Networks, Inc.
Cell: (650) 704-6633
Office: (408) 240-1239
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
