fix-date1904Attribute bool parsing possibility appointed on issue #649 #650
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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