mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #203] Problem with number formats #167
Labels
No labels
awaiting user feedback
bug
cmake
cmake
docs
feature request
in progress
long term
medium term
medium term
pull-request
question
question
ready to close
short term
under investigation
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/libxlsxwriter#167
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Alzathar on GitHub (Oct 29, 2018).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/203
Originally assigned to: @jmcnamara on GitHub.
libxlsxwriter: RELEASE_0.8.3
OS: Window 10 x64
IDE: MSVC15 x64
This problem is similar tothe issue #151 but with these number formats:
00.00.000.000The problem is related to the functions
lxw_hash_key_existsandlxw_insert_hash_element. The following snippet is the result of the generatednumformatin thexl/styles.xmlfile.I would expect this:
If I force the value of
has_elementto false in the code , I gave the good format in the XLSX. Of course, a new numFmt is generated everytime. The result is then this:You can reproduce this bug with the following code:
Note: The reported XML contents above do not come from the following code. However, you can see a similar error in the generated
numFmtstag with the following code at the end of this issue.Generated
numformatin thexl/styles.xmlfile from the code above.@jmcnamara commented on GitHub (Oct 29, 2018):
Thanks. That looks like a bug. I'll look into it.
Mainly for my reference, here is a simplified version of your code that reproduces it:
Output:
@jmcnamara commented on GitHub (Oct 30, 2018):
I've pushed a preliminary fix for this issue to the gh203 branch: https://github.com/jmcnamara/libxlsxwriter/tree/gh203
@jmcnamara commented on GitHub (Nov 10, 2018):
Fixed in version 0.8.4.
Thanks for the report.
@Alzathar commented on GitHub (Nov 21, 2018):
I did not have the chance to say "Thank you" for this fix!