HTML causing unreadable content error message
See original GitHub issueWhen a HTML command is present in a template, opening the output document results in message: “Word found unreadable content in “template.docx”. Do you want to recover the contents of this document? If you trust the source of this document, click Yes.”
Tested using the HTML example from the README
Example:
const buffer = await createReport({
template: fs.readFileSync("template.docx")
});
fs.writeFileSync("output.docx", buffer);
Environment: docx-templates v4.6.4 Node v14.2.0 Mac OS X v11.4
Thank you
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
3 Ways to Fix the Found Unreadable Content Error in Word
Fix 1. Open and Repair · Open the Word software from the Start menu or open another Word file. · In Word, select...
Read more >How Do I Fix Unreadable Content in Word (Windows/ ...
Fix 2. Use Recover Text from Any File Function, You can use a text recovery converter from Microsoft Word to fix the unreadable...
Read more >Solved: the Found Unreadable Content Error in Word
Method 1. Click on the “File” tab, then tap the “Open” button, and click “Browse”. The file explorer window will pop up on...
Read more >Solved - MS Word Found An Unreadable Content Error
The main cause of Word Found Unreadable Content error is corruption and the severity level of this corruption will inevitably vary from file...
Read more >How Do I Fix Unreadable Content in Word?
What Is Unreadable Content in Word. The error may happen when your files get damaged or corrupted for some reasons, such as: 1....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fix released in v4.7.0. Should be on NPM shortly.
Got it. Thanks for reporting. Looks like I messed something up when fixing #217 . This should be working as intended again after 636db40f1f7a8cbb1d8f303d0f59fd69641ee837, which is currently on master and will be in the next release.