mirror of
https://github.com/jmcnamara/libxlsxwriter.git
synced 2026-05-15 14:15:54 -06:00
[GH-ISSUE #42] "Content is Unreadable" error when strings contain control characters #34
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#34
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 @sw1020 on GitHub (Dec 16, 2015).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/42
Issue with Content is Unreadable. Open and Repair
I am using libxlsxwriter to make a node addon.
I found : when I write the utf-8 string with some special characters , it will cause the problem
for exzample: <Buffer e5 9b be 14 e5 9b be>
pls help
@jmcnamara commented on GitHub (Dec 16, 2015):
The "Content is Unreadable. Open and Repair" error is Excel's standard warning for any validation error in the XML used for the components of the XLSX file. It doesn't really help to identify the problem.
You will need to submit a small working example that demonstrates the issue. See the Bug Reporting Guidelines.
Note, libxlsxwriter does work with UTF-8. There is an example in the docs/repo and there are several test cases that test it.
John
@sw1020 commented on GitHub (Dec 16, 2015):
sorry
the utf-8 string example (in hex): e5 9b be 14 e5 9b be
if i replace 0x14 to 0x20 ,it will work fine
@jmcnamara commented on GitHub (Dec 16, 2015):
The non-unicode character 0x14 is a control character. These aren't currently supported in libxlsxwriter.
I'll fix that in a later version but for now make sure that your strings don't contain control characters.
@jmcnamara commented on GitHub (Dec 16, 2015):
Here is an example program that demonstrates the issue:
And here is a working example with the control character replaced with a space:
@jmcnamara commented on GitHub (Dec 21, 2015):
Fixed in version 0.2.7 and the master HEAD on Github.
Thanks.