AmberV wrote:That said, the word processor research that I performed for the section you quoted did show Pages to have a less than adequate handling of RTF standards. So you are right to point that out. Where I think you err is in your implication that this is somehow the fault of Scrivener. Actually, it produces very standard RTFs. It is up to the word processor to handle these standards, and the fact of the matter is, Apple has demonstrated their lack of interest in doing so, not only with the basic RTF support package available to Cocoa developers, but with their flagship page layout program as well.
I just finished a big project, and I would have liked to be able to just export from Scrivener to Pages. But I couldn't, and I had to first export to Word, then save the document as a DOC file, and finally open it in Pages. I use Pages because it's the cheapest option to get a decent page layout, real printer-grade font features, and produce decent PDFs. I know that it's not Scrivener's fault that Pages does not support a more robust RTF. Yet, this is another case in which pointing fingers doesn't really solve the user's problem. DT does not support Pages yet, and when you ask the developers, they blame it on Apple.
This is not a criticism to Keith, or to Scrivener. But I think that it's okay to discuss the little imperfections of something you love dearly.
When it comes to writing, I wouldn't change Scrivener for anything; but, it would be nice to go directly from Scrivener to Pages. Meanwhile, MS Word (that ugly monster) is able to produce documents perfectly readable by Pages.