public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Stefano Zacchiroli <zack-CfJEcLwHECWjKv3TNrM5DQ@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: preserving blockquote spaces when converting from docx
Date: Tue, 31 Oct 2017 08:52:15 +0100	[thread overview]
Message-ID: <20171031075215.dwxkum55skzs52d3@upsilon.cc> (raw)
In-Reply-To: <20171030170910.GC38507@protagoras>

On Mon, Oct 30, 2017 at 10:09:10AM -0700, John MACFARLANE wrote:
> You might try using nonbreaking spaces in the docx;
> pandoc should preserve those.

Thanks for your answer! As I understand that would indeed work, but
unfortunately I don't control the documents myself. Also, it would be
annoying to change those spaces into nbsp, which they conceptually
aren't, just to make pandoc preserve them.

Is there really no way to hook into pandoc *before* it decides to remove
them?

Alternatively, what would be a definition of the policy that pandoc uses
to decide those are blockquotes? If nothing else works, what I can do is
writing a docx filter that adds the nbsp automatically, but I need to be
sure that I do that only where pandoc will "see" blockquotes.

TIA,
Cheers.
-- 
Stefano Zacchiroli . zack-CfJEcLwHECWjKv3TNrM5DQ@public.gmane.org . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/20171031075215.dwxkum55skzs52d3%40upsilon.cc.
For more options, visit https://groups.google.com/d/optout.


      reply	other threads:[~2017-10-31  7:52 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
2017-10-31  7:52     ` Stefano Zacchiroli [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=20171031075215.dwxkum55skzs52d3@upsilon.cc \
    --to=zack-cfjeclwhecwjkv3tnrm5dq@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).