Exporting an Outline to a Word Doc that Uses Word's Bullets instead of bullet characters
Hey Brett and friends,
Thanks, as always for Marked and your awesome support and help for it. One of the things I do most frequently in plain text/markdown is make an outline. But sadly, in this unpleasant corporate world we live in, sending people plain text outlines doesn't fly. And regrettably, Outlook strips leading whitespace when i paste my outline into the body of an email, resulting in a compacted list. When I have used Marked to export a markdown outline to a Word docx file, I get the correct outline structure, but the bullets are just characters indented correctly, rather than using Word's native bulleted or numbered lists. This makes editing the outline in word a little weird. I have found that Pandoc's export to docx results in the correct use of word's bulleted list. I added Pandoc as a custom processor (configuration screenshot included just in case I did something dumb), but I don't think Marked uses the custom processor in the way that I'm thinking it does on export to a different file, yes? I could just use Pandoc from the command line, but exporting directly from Marked is usually much easier for me.
Is there a way to either:
1. Have Marked's docx export use Word's native bullet list functionality, or
2. Have a way to use Pandoc's export engine rather than Marked's for certain files, within Marked?
Appreciate the help, and I understand if this just is how it is.
Cheers,
Connor
Screen_Shot_2016-01-26_at_12.32.14_PM.png
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 26 Jan, 2016 09:08 PM
Once I finish the current RTF rewrite, yes, lists will export using
actual Word elements. Coming soon.
The custom processor feature only allows you to return HTML, so while
you can use Pandoc, it's not feasible as an export option. One thing you
can do, though, is to fork within a custom processor to return HTML and
write out an export file at the same time. This, of course, has the
complication of writing the export file every time the document
refreshes, but on the bright side you'd have a very up-to-date exported
document…
Here's an example of this type of script:
http://brettterpstra.com/2014/07/22/custom-export-options-for-marked-2/
-Brett
2 Posted by connor on 26 Jan, 2016 09:14 PM
Sounds great, I'll look forward to it! I'll also take a look at doing it in the custom processor.
Thanks so much!
Connor