I exported a Google Document to RTF. I opened it in OpenOffice to confirm it was a normal file. (Yes, I do have a thing for open software. Sue me.) All apostrophes and " get the text ‘tlch’ attached. A copy-paste of a sample paragraph:
A man’tlchs deep voice was heard outside the door. “tlchThis is the best you can do?”tlch
I’m using a Samsung NC-10, Win XP Home 2002 SP3. I have mailed you the RTF.
When you say you opened it in OpenOffice, does that mean you observed the strange pattern there as well, or did it look fine in OOo, but weird in Scrivener?
I’d try using Save As from OOo to try and “clean” the RTF file. This can sometimes be beneficial when one product isn’t linking up well with another.
Amber, that’s exactly what I did to solve the problem (open in OpenOffice and resave). The thing is, OpenOffice recognized the RTF produced by Google Docs as valid RTF; it was able to open the Google Docs RTF and display it as normal text, with no error messages about converstion. That says to me that Scrivener (hugs it) may have a definition of valid RTF that is too narrow.
I saved the OpenOffice RTF in a separate file, so I still have the original RTF that Scrivener couldn’t read.
Just downloaded scrivener and imported an .rtf from google docs. I’m having this issue as well. Too bad I don’t have another word processor!
Well, fortunately OpenOffice.org is free. It’s a fairly large download, and a bit of a clunker, but in a pinch it can be a good thing to have around.
On the original matter: could you send a sample RTF to me at (support AT literatureandlatte DOT com)? Just some filler text that reproduces the error when you try to import it directly into Scrivener. Make sure it is the version that is messing up, not the cleaned up version. I’ll take a look at its coding and analyse it.
Scrivener’s RTF engine is a work in progress, and has been written completely from scratch. So it will have some growing pains. Despite being an openly documented specification, there are a lot of derivatives floating around out there.
This is will no doubt be addressed in the RTF fixes, but I’d be interested in your analysis of the rtf codes causing this issue AmberV.