Disappointed in "Convert Multimarkdown to Rich Text" Compile option

If you have that impression, no wonder you’re confused! I’m at a loss as to how you got it though…

  • searches her own posts *

Perhaps you got that impression from this post:
[url]Scrivener should become subscription - #24 by Silverdragon]
If so, I’m sorry; that wasn’t the impression I wanted to give. What I wanted to say was:

  1. Having non-text documents in a Scrivener project isn’t important to me, as an individual. Most of my research clippings are in Evernote. Of the rest, I’ve got everything linked already except cover images and a composition mode backdrop that I almost never use (because I only use composition mode to check my answer to a forum post, or check the look of a Scrivener appearance theme I develop.) It’s not a call for “more iOS Scrivener-like”, just an acknowledgement this is a feature I personally don’t use much.
  2. In Mac Scrivener, there are often several ways to achieve the same result. If you choose to reduce duplication, that’s fine with me as well. Again, not “more iOS Scrivener-like”, just “if there’s any fat there, sure, cut it.”
  3. I’d like to see the Mac interface move more towards an obviously non-WYSIWYG paradigm. That doesn’t mean dumping rich text, nor does it mean “more like iOS Scrivener.” But as this thread proves, WYSIWYG is very low on my list of desired features—it’s something I put up with to have Scrivener. And I believe (perhaps wrongly) that less WYSIWYG appearance might lead to less confusion for new users. (This is based solely on my own experience of how difficult it was to break the WYSIWYG paradigm in my brain. When it dawned on me that I could use whatever font I wanted(!!!) to write with and Compile would make my output look professional nonetheless, it was as if I’d been let out of jail.)

So there you have it. My preferences aren’t on a spectrum between iOS Scrivener and Mac Scrivener. They’re off the main sequence. :smiley: Make of that what you will.