From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: docx -> md and escaped quote marks
Date: Tue, 03 Sep 2019 14:48:40 -0700 [thread overview]
Message-ID: <yh480k7e6poxtz.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <810a995a-8a38-53e6-39cc-acb2c122b5c4-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
Pandoc tries to convert accurately. So if they're straight quotes
in docx, they turn into straight quotes in markdown (and they're
escaped to make sure they're interpreted that way.)
Postprocessing the output is probably your best approach.
Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
> Another converting-from-docx question.
>
> Some Word files don't have smart (curly) quotes -- especially those first typed into GDocs -- and when I convert into markdown via pandoc have all their single and double quotes escaped. I've tried +/-smart on input and output but haven't figured out how to let it not escape them...
>
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/810a995a-8a38-53e6-39cc-acb2c122b5c4%40reagle.org.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/yh480k7e6poxtz.fsf%40johnmacfarlane.net.
prev parent reply other threads:[~2019-09-03 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 18:49 Joseph Reagle
[not found] ` <810a995a-8a38-53e6-39cc-acb2c122b5c4-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-03 21:48 ` John MacFarlane [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yh480k7e6poxtz.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).