Brett on 22 Sep, 2020 02:48 PM
Assuming you have MultiMarkdown selected as your processor, this is
quite likely due to a recent change in the way Bear formats the preview
it sends to Marked. I have the developer inserting his own metadata
comment in the markdown text to let me know it's coming from Bear, and
that's likely breaking the rest of the metadata (by adding a newline
before it). I'll have to work with the dev to resolve this.
I'll do some testing to confirm my suspicion, but that's the most likely
explanation. We didn't expect anyone to be using MultiMarkdown metadata
I'm having a probably related problem using Bear in Fountain mode. Marked2 is clearly picking up some header info from Bear and then messing up the YAML-like header material that starts every Fountain file.
Two front pages for comparison attached.
Otherwise, Marked2 is doing a pretty good job with Fountain format.
Brett on 28 Sep, 2020 05:43 PM
Another unexpected case, writing Fountain in Bear. I'm currently working on a method for Bear to declare it's the source without using metadata, but it's going to take me at least a week to get it implemented, and Bear will have to update as well, so there's no immediate solution. It will be fixed soon, though.