Now I’ll get this out of the way first of all – my request goes beyond what Apple’s RTF support accomodates. I’ve read your statements you don’t want to rewrite your own RTF parser and understand root canal work without anaesthetic is vastly preferable. Nevertheless you have implemented RTF stream manipulations to support annotations / footnotes etc and so I throw this out in delusional hope.
Premise A: Scrivener lives for outlines. The binder is where that goodness allows writers to structure and restructure their work. This is a critical workflow issue.
Premise B: RTF support outlines. Word, Mellel and most others have outlining features that are pretty essential to get the most out of them.
Conclusion: Allow hierarchical levels in Scrivener to be exported to RTF.
Boring details: From at least V1.7 of the RTF spec, there is a command to enable outline levels to be embedded in elements:
Therefore Scrivener can output at least the first 8 levels to RTF. For Import you can read that then add the subsequent part to a folder / subfolder item.
Caveats: I’ve never had to actually write an RTF parser
p.s. I have V1.7 and V1.9 of the RTF specs extracted from their ridiculous .EXE containers if anyone want them.