public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Patrick <ps19898989-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: v2.15 (Mac): Word to Tex conversion, /begin{quote} inserted far too often
Date: Tue, 2 Nov 2021 04:41:05 -0700 (PDT)	[thread overview]
Message-ID: <d5e31c5d-b3a8-43d9-bc86-d38f11429c6bn@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]

Hello,

Just upgraded pandoc to version 2.15. I convert MS Word documents to tex 
files via pandoc. First line of new paragraphs in my Word docs is normally 
indented (left indent 0.5in, 1.27cm — standard setting). Pandoc didn't 
previously treat these indents as quotes, now it does.

This is problematic, as there's quite a lot to edit in the .tex files 
post-conversion now. I *do* actually sometimes set longer quotations apart 
from rest of text by indenting (indent is 0.5 in/1.27cm both sides; 6pt 
spacing before the quote, 12pt spacing after). In previous versions, pandoc 
recognised that only these standalone quotes should have these nifty 
/begin{quote} /end{quote} tags around them, which worked perfectly for me.

I'll now likely have to downgrade to a previous version of pandoc.

-- 
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/d5e31c5d-b3a8-43d9-bc86-d38f11429c6bn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1579 bytes --]

             reply	other threads:[~2021-11-02 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 11:41 Patrick [this message]
     [not found] ` <d5e31c5d-b3a8-43d9-bc86-d38f11429c6bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-02 14:21   ` Patrick
2021-11-02 16:52   ` John MacFarlane
     [not found]     ` <m2tugulctv.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-11-02 16:58       ` John MacFarlane
     [not found]         ` <m2r1bylcjs.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-11-02 17:39           ` Patrick

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=d5e31c5d-b3a8-43d9-bc86-d38f11429c6bn@googlegroups.com \
    --to=ps19898989-re5jqeeqqe8avxtiumwx3w@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).