Bug 881523

Summary: xls2csv misinterprets the DATEMODE chunk
Product: [Fedora] Fedora EPEL Reporter: Msquared <142.bugzilla.redhat>
Component: catdocAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: adel.gadllah, pertusus, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-30 14:56:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to fix the problem
none
Patch for the specfile none

Description Msquared 2012-11-29 03:00:59 UTC
Created attachment 653930 [details]
Patch to fix the problem

Description of problem:
When parsing an XLS file, xls2csv interprets the presence of DATEMODE to determine the epoch for date storage.  The correct use of the DATEMODE chunk (when present) is to inspect the value and use that to determine the epoch for date storage.

Version-Release number of selected component (if applicable):
0.94.2-6.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Convert an XLS file produced with a recent version of MS Excel
2. Inspect the dates in the output CSV file
  
Actual results:
The dates are off by four years.

Expected results:
The dates are accurage.

Additional info:
Patch coming up!

Comment 1 Msquared 2012-11-29 03:06:26 UTC
Created attachment 653931 [details]
Patch for the specfile

Comment 2 Msquared 2012-11-29 03:19:12 UTC
Reference for my patch: https://www.openoffice.org/sc/excelfileformat.pdf

(see section 5.28 on page 154)

Comment 3 Robert Scheck 2015-04-13 20:51:24 UTC
I am not really sure how to verify that patch.

Comment 4 Ben Cotton 2020-11-05 16:53:22 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 5 Ben Cotton 2020-11-05 16:55:57 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 6 Ben Cotton 2020-11-30 14:56:29 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.