From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: preserving blockquote spaces when converting from docx
Date: Mon, 30 Oct 2017 10:09:10 -0700 [thread overview]
Message-ID: <20171030170910.GC38507@protagoras> (raw)
In-Reply-To: <5d590149-457b-4de3-b863-57f70366e6d9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You might try using nonbreaking spaces in the docx;
pandoc should preserve those.
next prev parent reply other threads:[~2017-10-30 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 14:39 Stefano Zacchiroli
[not found] ` <5d590149-457b-4de3-b863-57f70366e6d9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-30 17:09 ` John MACFARLANE [this message]
2017-10-31 7:52 ` Stefano Zacchiroli
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=20171030170910.GC38507@protagoras \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).