Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix-date1904Attribute bool parsing possibility appointed on issue #649 #650

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

eJJonatah
Copy link

@eJJonatah eJJonatah commented Aug 23, 2023

As demonstrated in the issue example, scheffer, from oracle using a database procedure to generating a .xlsx report sets the
attribute date1904 in tag workbookPr as a "true" literal value instead of "1" already known pattern. I tested other possibilities that can be seen in the file Test_Issue_649_Date1904_Parsings's internal xmls and found out that the only values recognized by
excel are "1" and "true", since any other possibility will not display dates correcly in the excel's interface.

I put pattern matching because i think its more readable than the equals operator but that can be easily edited to mantain the
project pattern.

Closes: #649

…rom xl/worbook.xml. The only two possible values that excel recognises are "true" and "1"

also, pattern matching is more readable than equals "==" aldo this can be easily changed if breaks the project pattern. ExcelDataReader#649 third solve suggestion
xl/workbook.xml > workbookPr > date1904 attribute
@eJJonatah eJJonatah changed the title fix-[XmlWorkbookReader]::date1904boolParsing appointed on issue #649 fix-date1904boolParsing appointed on issue #649 Aug 23, 2023
@eJJonatah eJJonatah changed the title fix-date1904boolParsing appointed on issue #649 fix-date1904Attribute bool parsing possibility appointed on issue #649 Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DateTime incoherent value
1 participant