I’d much prefer to see bold and italics in Scrivener even when in MMD, to be converted properly to bold and italics as a first stage of MMD output. Scrivener already has an option to replace italics by underline when exporting. Is it, or would it be, possible to regain a bit of “wysiwyginess” I describe?
Apologies if you have already been using this, but have you tried Text>Convert>Bold and Italics to multimarkdown syntax? It’s pretty much a one way process, but would let you preserve your WYSIWYGness to the very last moment.
Thanks for the pointer, I was not using that. Looks good, but one-wayness is, of course, a handicap. I probably should file it as a feature request, to do the conversion during export.
Sorry to disappoint, but this still isn’t a feature in compile. Do feel free to lobby for it in the wish list forum, and produce an argument for getting around the problem where rich text lets you be ultra-sloppy with formatting, and produce combinations of formatting that end up not getting parsed as a result. This is the main reason why the feature has never been implemented. It is too easy to accidentally mark spaces with formatting, and that will create bare punctuation marks in the final output. The one-way tool is there so you can quickly fix imported stuff and proof it right there on the spot.
Example:
...laboris nisi ut aliquip ex ea commodo consequat.** _Duis _aute irure dolor in** reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
The only way this feature could be reliable is if a writer never imported any text at all, and everything they did in the editor was meticulously performed and with MMD in mind. Rich text allows much more latitude (like ten italicised paragraphs marked with a single range, not ten), so the formatter would have to be keenly aware of all this and perform every formatting gesture flawlessly for there to be no glitching in the final product.
Sure – that’s why it can be a checkbox. Every checkbox we apply carries certain ramifications and risks. Someone using the feature in MMD would probably be aware of it. I’d leave the risks to the actual user, perhaps with a note/link to help.