I can’t find any way to have two blockquotes separated by whitespace. I’d expect
> Quote 1
> Quote 2
to result in
Quote 1
Quote 2
like it does in the old renderer (and the one here, and the Commonmark spec), but the new desktop DEVONthink renderer turns them into a single blockquote.
Thanks for the bug report, we’ll check this. But as our parser merges the syntax and features of the most popular dialects, there might be of course subtle differences.
You could use a horizontal rule between them. Or use an HTML comment if you want nothing rendered.
> Important thing said…
<!-->
> Another import thing…
In a similar vein, I use a custom CSS for styling my markdown and float seems to be broken?
.rbox {
float: right;
margin: var(--box-margin);
padding: var(--box-padding);
}
The span remains left-aligned on the page.
Aside from that, I’m VERY pleased with the new release. Nice job, all!
There’s no issue with float. On what element are you using the rbox class? Class definitions aren’t part of the Markdown specification.
It’s impossible to help you with this unless you show us the complete document and CSS.
In any case, DT doesn’t care about float or anything else you do in your CSS – it’s the browser respectively WebKit that handles styling.
There’s no issue with
float. On what element are you using therboxclass?
I use the rbox class with a span. It’s always worked well before. Thanks!
Hmm. I hear what you are saying, but it does not align with what I see. And I respectfully point out that my browser or webkit has not changed since this morning (when things worked) and when I installed ver 4.3 (when things stopped working.)
I agree that CSS is not part of the markdown specification. But DEVONthink allows for a custom CSS to be referenced during the markdown rendering.
I allow that I may have some false assumptions. But it was working. The new DEVONthink 4.3 has a new rendering engine. And now my float ain’t floating.
I’ll add that the new render-er changes a bunch of other stuff..apparent font sizes and the like. I don’t care about any of that, it’s not surprising and I can make adjustments in the CSS. But if float don’t float then it’s not something I can work around.
Regarding the exact CSS and document file. Well, I could share something but it’s seems like overkill. Most everything else in the CSS is being rendered close-to-correctly so I was trying to focus attention on the one problem I’ve see thus far.
Okay, this may be a factor:
I habitually embed HTML (such as <span>) in my markdown to control the rendering in DEVONthink. It’s allowed me to do beautiful things. I’d attach a screenshot but now it doesn’t render correctly. However, before the update stuff could float and now it can’t.
Thanks again for any help.
Also, not part of the Markdown spec 
Switch Settings > Files > Markdown > Preview back to MultiMarkdown 6. Does your span work?
I just created an MD file with a span element containing a class attribute and it rendered perfectly fine.
You don’t know what I really did. As we do not know what you really did. One thing is clear: float did not change, nor is it in any way related to the renderer. But you do not give us a chance to figure out what might be the reason for your perceived problem. You do not even show us the problem. And float is a tricky beast, where a lot depends on the context in which it is used.
If you want a solution and not only express your discontent, please provide a (preferably short) example showing
The next release will fix this issue.
Aha! Did not realize that was an option, but should have guessed.
Thanks Jim, it’s working as expected.
I didn’t actually have any pain points with MM6 so this is okay. On my Mac. But I can’t find any way to change the render engine in DTTG. ??
Development has seen this thread so it may be something looked at for the future. And you can’t change the renderer in DEVONthink To Go at this time.
Not a problem! As a matter of fact thanks to your suggestion and your assertion that you had float working I was able to suss out the issue.
There is a subtle difference in how the new DEVONthink render-ers parse html elements in a markdown document compared to MM6. And I can work around it pretty easily.
Okay, the problem (?) seems to involve newlines between html elements. I’ve always used macros to insert these for me. (And they worked great!)
My old way (pre DT 4.3) was this:
<div class="title">Testing A</div>
<span class="rbox"><b>Links:</b><br>
This is not really a link
</span>
<span>This is a normal span.</span> <span class="rbox">And this is a floated span.</span>
Which now results in this:
(Notice that the “Links” are not floated to the right.)
But I’ve found that if I remove a couple of the newlines, as this:
<div class="title">Testing B</div>
<span class="rbox"><b>Links:</b><br>
This is not really a link
</span>
<span>This is a normal span.</span> <span class="rbox">And this is a floated span.</span>
Then the result is as expected:
Note that while I have almost 600 lines in my custom CSS, this was not part of the issue. It’s simply that the bespoke DEVONthink markdown renderer parses html elements a little bit different from the MM6 one.
Given that—to my knowledge, no expert—html elements are not even a part of the markdown spec, this is not unreasonable. And since the new behavior is deterministic, it can be accommodated.
Thanks very much to all of you with your help with this!
Thanks very much again!
While we’re talking Markdown, I’m delighted to report that the new renderer passes the Moby Dick test.
Sorry folks, I have another small issue with the new renderer.
It seems a markdown table MUST have a header row. It can be empty, but it has to be there for the table syntax to be recognized. (Surprised that this has not already been reported.) Demonstration:
Markdown doesn’t natively support headerless tables. MultiMarkdown did. Development would have to decide whether to implement this or not in DEVONthink Markdown.
You could hide it with a styling of…
th {
visibility:hidden;
}
or display:none;.
Thanks Jim.
I don’t need to hide the header because I can leave it empty. And I can modify my macro to include the empty header automatically. Since “headerless” tables are not part of the specification, I won’t even ask for it to be “fixed.”
Thanks again.
I actually had forgotten they were a MultiMarkdown feature so I was a little surprised too 