Saving as HTML doesn't save fenced code blocks properly
In the attached screenshot you can se a markdown file with a fenced code block which is properly converted to Github styled HTML on Marked's HTML view but the same correct HTML isn't used when saving to an HTML file.
Top left: original markdown
Top right: Marked showing the markdown fenced code block being correctly represented as HTML.
Bottom left: Wrong HTML stored by Marked when saving
Bottom right: The saved HTML file opened in Chrome.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Brett on 03 Jun, 2013 11:53 PM
May I have an exact copy of the relevant portion of that file and a quick screenshot of your Behavior settings? Thanks!
—
Sent from Mailbox for iPhone
2 Posted by Gabriel Ayuso on 03 Jun, 2013 11:59 PM
Thanks for the quick response.
I have attached the screenshot of the Behavior settings and the markdown
snippet.
Regards,
Gabriel Ayuso
Support Staff 3 Posted by Brett on 04 Jun, 2013 12:22 AM
I haven't been able to narrow it down yet, but I can definitely replicate the bug to some extent. It's even weirder on my end, though. I'll work to figure out why it's behaving differently on Save with that combination of settings.
-Brett
Support Staff 4 Posted by Brett on 04 Jun, 2013 05:20 PM
I can't for the life of me figure out where it is, but there's a gremlin in the markdown you posted. If I retype the code by hand for just the first block, everything works again.
Also note that there are two other issues:
-Brett
5 Posted by Gabriel Ayuso on 04 Jun, 2013 05:35 PM
Thank you for the advice.
Btw I took the liberty to test the export to DOCX of the beta version and
it worked great, except for tables (probably not implemented yet).
If you don't mind I'd like to keep using the beta. I'll provide feedback if
I find any issues or suggestions.
Regards,
Gabriel Ayuso
Support Staff 6 Posted by Brett on 04 Jun, 2013 05:38 PM
Please do keep testing, let me know what you run into.
DOCX export is shady at best. You get better results by exporting RTFD and pasting, or exporting HTML and importing, or exporting ODT, opening in OpenDoc and exporting DOCX. For some reason, going straight to DOCX has proven nearly impossible to get right.