Export Only to RTF Files

Scrivener Scrivener for Windows
1

Has anyone else had a problem exporting text files to html or to anything but rtf’s?

I am running 1.0.2 on Windows 7 Ultimate and I can’t get any text file to export other than to an rtf file no matter what option I choose from the dropdown menu in the export command. The exception is that a folder will export as an html file but any text files under the folder will export only as an rtf file. Any ideas on what may be going wrong?

2

This has been working for me (bug regarding duplicate naming of sections aside). Do you have any of the meta-data checkboxes selected? I tried as .doc and .pdf; both worked.

3

I’ve done a little more testing. Here is what I’ve found so far. If I export the text files from the Scrivener Tutorial they will export properly to pdf, html, etc. Also, if I create a new text file in the program it seems to export properly. However, if I import a text file – up to this point I had only been using imported files – it seems it will only export as an rtf file. I’ll continue to test other variables.

4

Ah ha, that I can confirm. I created a .docx file, dropped it in the Binder, and exported it with a bunch of nodes I’d created in Scrivener. The outliner items native to the program exported in PDF; the one I dropped in from the desktop exported in RTF.

Hmm.

5

Strange one. I tried copy and pasting the RTF code itself using a plain-text editor, from a file created in Scrivener into the one I had imported, and this made no impact; so it wasn’t the result of having once been bloating with Word’s RTF code. So I created two nodes in an outline; one in Scrivener and one dropped in from Word, and found this discrepancy in the XML of the .scrivx file:

                            <MetaData>
                                <IncludeInCompile>Yes</IncludeInCompile>
                                <FileExtension>rtf</FileExtension>
                                <NotesTextSelection>0,0</NotesTextSelection>
                            </MetaData>

...vs...

                            <MetaData>
                                <IncludeInCompile>Yes</IncludeInCompile>
                                <NotesTextSelection>0,0</NotesTextSelection>
                            </MetaData>

I tried removing the FileExtension element, but that is coming from some place else, for it always pops back up after opening and closing the project.

6

Yes, it seems to only matter whether the document was created in Scrivener or not. If I copy the text from an imported file into a text file created in Scivener it will export just fine.

7

If you split an imported document, the document that keeps the same name remains exportable only in rtf. The new document created for the second part of the split, however, is exportable as other than rtf.

I’m not sure what to make of this other than it seems to confirm that a text file has to be created in Scrivener in order for it to be exportable to something other than rtf.

8

Yes, splitting is essentially making a new file. It’s just handling all of the copy, paste, and meta-data settings for you.

9

So, Amber, would you consider this a bug? Should I report it on the bug hunt forum?

10

This is a bug, but there is no need to create a new topic for the issue. We’ve already got it in the bug tracker with this thread URL for source material. Thanks for helping to track it down!