On the matter of importing text, that’s a silly bug that is potentially a side-effect of there being a missing setting. There should be a checkbox and font selection control in the Sharing: Import options tab which allows one to have recognised plain-text file formats imported using an alternate font from the defaults. All other aspects of one’s default formatting settings would be used. So it’s currently acting like that option is set, but since there is actually no font selector, it seems to fall back to some system level font. It’s a nice setting if you want a fancier font for rich text, but generally import source code or other stuff that would benefit from a fixed-width font, as plain-text.
As you note, you can just select the batch of imported files and hit
Ctrl+0 to reset the formatting, so the issue at least has an efficient workaround, and one that is commonly used after a batch import anyway, no matter the workflow.
Well, if you’re not actually intending to use Scrivener to write Markdown, then you shouldn’t be importing Markdown files. I’m a little confused at this point though, since you mentioned wanting to test the new Markdown features in v3. If you get rid of all the Markdown, what are you testing?
At any rate—to provide advice for what you’re trying to do specifically: just use MultiMarkdown or Pandoc to convert your Markdown files to .odt or .docx respectively. Nothing is going to convert Markdown to high quality formatted text better than these tools. We do have some very (I stress very) basic conversion via the
File ▸ Import ▸ Import and Split... menu command, but that command is more interesting for how it can convert Markdown heading structure to outline hierarchy, in my opinion.
And in case you are wondering, that’s not something you would lose by using Pandoc to make .docx files, of course, since it will be building an outline into the heading stylesheet, which can also be parsed into outline structure in v3 via this same command.
In my particular case I’m dealing with 40+ separate md files, which I will need to convert to odt and merge together into a single file. Yes, Pandoc can do it via cli, but I wanted to see what Scrivener could do and if I could maybe finish my current writing project in it.
Yeah, so it sounds to me like overall the confusion is that Scrivener’s Markdown support is designed for actual Markdown users, those who want to write with it from start to finish, who don’t consider any of the aspects of plain-text to be downsides, and want to use the high quality conversion options provided by these tools upon compilation.
There are shades of grey in here though, and you can read a bit about them in the user manual, under §21.4, Markdown and Scrivener. On the other end of the spectrum, one can in some cases produce and use Markdown conversion without knowing a thing about Markdown. I.e. your styles and some simple formatting can be converted to Markdown.