tag:support.markedapp.com,2011-09-11:/discussions/problems/162456-doc-and-docx-do-not-have-working-html-linksMarked: Discussion 2021-06-23T17:06:48Ztag:support.markedapp.com,2011-09-11:Comment/491323372021-04-08T18:58:44Z2021-04-08T18:58:44Zdoc and docx do not have working html links<div><p>To put it bluntly, Marked's DOCX export is insufficient in many ways.<br>
It's always been on my list to rebuild the whole engine, but somehow I<br>
have not gotten around to it in the last decade.</p>
<p>Links don't work, images are hit and miss, document styles aren't<br>
preserved... Marked is great at PDFs, but Word documents are a bit of a<br>
hack. I would note that exporting to RTF does give you working links in<br>
Pages, though I don't know how Word handles RTF files.</p>
<p>In short, my humblest apologies, this is a long-known issue.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/491323372021-04-08T19:22:34Z2021-04-08T19:22:35Zdoc and docx do not have working html links<div><p>This works:</p>
<p>Export to RTF —> open RTF in Nissus Writer —> export to Docx</p>
<p>I don’t do this so often that it’s a major hardship.</p>
<p>Tj</p></div>Timothy J. Luomatag:support.markedapp.com,2011-09-11:Comment/491323372021-04-08T19:41:26Z2021-04-08T19:41:26Zdoc and docx do not have working html links<div><p>That's an embarrassing amount of work. Hopefully I'll figure out the<br>
missing pieces sooner than later.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/491323372021-04-08T22:05:02Z2021-04-08T22:05:02Zdoc and docx do not have working html links<div><p>Don’t sweat it too much… Turns out that pandoc can do MD->DOCX so I can use that for now.</p></div>Timothy J. Luomatag:support.markedapp.com,2011-09-11:Comment/491323372021-04-08T22:12:18Z2021-04-08T22:12:18Zdoc and docx do not have working html links<div><p>Yeah, I was actually considering embedding pandoc for that purpose. It's<br>
powerful from the command line, but a pain to try to put a good GUI on.<br>
But a good reference DOCX will give you great results.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/491323372021-06-23T14:25:24Z2021-06-23T14:25:24Zdoc and docx do not have working html links<div><p>You may already know this, but just in case:</p>
<p>I installed <a href="https://brettterpstra.com/projects/markdown-service-tools/">https://brettterpstra.com/projects/markdown-service-tools/</a> on my M1 Mac mini, and when I tried to run one, it said that I had to install multimarkdown.</p>
<p>But it was already installed.</p>
<p>However, it was installed at <code>/opt/homebrew/bin/multimarkdown</code> instead of <code>/usr/local/bin/multimarkdown</code> and I assume that was why it was not spotted.</p>
<p>I made a link from the <code>brew</code> one to <code>/usr/local/bin</code> and MST seemed happy enough to use it.</p>
<p>FYI</p>
<p>Tj</p></div>Timothy J. Luomatag:support.markedapp.com,2011-09-11:Comment/491323372021-06-23T17:06:47Z2021-06-23T17:06:47Zdoc and docx do not have working html links<div><p>Yeah, brew on M1 installs everything to /opt/homebrew. I always thought<br>
it was safe to hardcode /usr/local because WHY WOULD THAT EVER CHANGE?<br>
So I've been updating my own scripts to use <code>brew --prefix</code> but it's<br>
harder with stuff like Services that have no guarantee that brew is<br>
installed. I'll add some logic for that, I guess.</p>
<p>FYI, I symlinked /opt/homebrew/bin to /usr/local/bin. /usr/local is<br>
supposed to be for x86 builds now, but I haven't suffered any<br>
consequences from doing so, yet... at least all of my scripts with<br>
hardcoded paths aren't complaining.</p>
<p>-Brett</p></div>Brett