Compiling a document to Microsoft Word (.docx) from Scrivener Release Candidate 3 creates an unusable document.
My Scrivener installation updated today: Version: 2.9.9.3 Beta (894377) 64-bit - 13 Apr 2020
Running on Microsoft Windows 10 Home
Using Microsoft Word (Microsoft Office 365) 16.0.12624.20382
I can reproduce this issue by:
Create a new blank project.
Type a few words into the document.
Compile to Microsoft Word (.docx) format.
The compile completes without complaint but upon attempting to open the Word doc I get this error message:
If I click Yes to still attempt to open the document I get this error message:
I am unable to attach the Word doc that compiling following the above steps created. You can download that Word doc from here: dropbox.com/s/d1y7xlijqttjv … .docx?dl=0
I believe this bug is newly introduced with Release Candidate 3 as I’m pretty certain the last time I used this feature was with Release Candidate 2. Definitely introduced during Release Candidate stage at any rate.
I can confirm the problem on compile but was able to open the file with only the first item selected on the menu. I then did a compile into .rtf with no problem. Not the best solution but usable in word. I do remember that here had been problems with compile into .docx. I am using Office 365 subscription so its up to date.
As a followup I was able to compile successfully into Word .doc and Open office .odt and open them in Office 365 with no errors.
One could say that compiling to RTF and opening in Word is actually the best solution, as Scrivener compiles to RTF—its default format—and then calls either the Aspose converters, or presumably on Windows if you have Word, Word itself to convert it to DOCX. So if you compile to RTF and open that in Word you get the best conversion.
I don’t know if this is available on Windows, but on the Mac you can specify what app you would like the compiled document to open in, in my case Nisus Writer Pro, but if you have Word, you could compile to RTF and specify to open automatically in Word. Just as quick if not quicker and save it from Word as a DOCX.
Word detects ‘unreadable content’ and will not open the generated document.
Preview in the Explorer window works,
You can open it so you can see the underlying code op Word, which is not very helpful.
Exporting to Word is one of most important functions of Scrivener to me. Please fix and offer a new RC soon.
Thank you, guys! This is a regression since RC2 most likely due to the new footnotes implementations. As a workaround compile to RTF and use Word to save it to DOCX.
Same problem here, but with a slightly difference error message. When compiling to docx: “We’re sorry. We can’t open because we found a problem with its contents.” Details: “The file is corrupt and cannot be opened.”
Given the option to try to “recover the contents of this document” reproduces the same “We’re sorry” msg. However, the “details” now state “Microsoft Office cannot open this file because some parts are missing or invalid.”
As with other posted, I’m able to compile to doc format.
