I have tried to convert my piece into word or rtf forms but it just never finishes - I have waited and waited but it just does not finish - when ever it hits 100% it just re-starts from 0 - and again, and again. Before the update I had no problems exporting/converting files. Any tips on what to do? Now it looks like I need to copy/paste to word… or does it just nowadays take hours and hours to do conversion?
Unless your project is unspeakably enormous, it’s hard to imagine a normal compile taking more than a few minutes. Usually it’s much less, especially for RTF. DOC and DOCX require more conversion, and Scrivener offers a few different options for export converters to handle that, so particularly with something like the Microsoft Word option you’ll have a longer compile time.
Since you’re getting this problem compiling just to RTF, try creating a sample blank project, typing some text in the document, and then compiling that to RTF. Does it work? If so, then it seems like the problem is specific to the other project, possibly some hidden formatting in a document or some mix of settings triggering a bug. Is the manuscript all text or do you have a lot of images in it?
Hi and thank you for your reply!
I tried that and same thing - conversion just never stops. With rtf it did do conversion but the file was corrupted when I tried to open it. Right now I cant get any book out on word/rtf formats.
You might take a look at the following thread…
https://forum.literatureandlatte.com/t/storyspace-hypertext/378/1
It sounds like you’re using Microsoft Office for the DOC/DOCX conversion, and when that is failing, it’s setting off a different issue loading documents in Word. The MS Office converter accesses Word’s libraries, and if the converter crashes or is aborted, that can be left in a messy state. If you reboot the computer, it should clear everything properly. Try that and then try loading the RTF file you compiled (without running another compile first). Does it open correctly in Word now?
My guess is that the converters may be misidentifying your version of Office, so Scrivener is defaulting to those converters but in fact they are not supported by your system. Office 365 uses a different API than 2007-2013 and isn’t supported, but the Doc2Any converters that handle the Microsoft Office conversion don’t distinguish properly between 2013 and 365. We’re trying to develop a workaround to fix this issue, but meanwhile you’ll need to switch to different converters. Even if you aren’t using Office 365, it seems that the converters aren’t working properly with the Word installation, so you’ll want to switch.
Go to Tools > Options… and click the Import/Export tab, then the “Export Converters…” button. Select “DOC” from the drop-down menu on the left. On the right, where I assume it says “Microsoft Office” now, select instead “RTF-Based”. Then change to the alternative converters for PDF and DOCX.
Once you’ve set each of the converters, click OK out of that window and then OK to close Options and try the compile again.