public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: chris.s.forster-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Pandoc Markdown: Avoid New Paragraph After Blockquotes?
Date: Thu, 19 Feb 2015 07:13:13 -0800 (PST)	[thread overview]
Message-ID: <ca77cf85-4f80-4388-ba68-54f89c6e9995@googlegroups.com> (raw)
In-Reply-To: <878uj5bzrh.fsf-4GNroTWusrE@public.gmane.org>


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

Hi, and sorry to resurrect an old thread but this seems a pretty important 
issue to me. In lieu of a fix for this in Pandoc (which seems unlikely, for 
understandable reasons) could you please explain how to use that latex 
preamble code -- I just get an error when I try, with the whole lot copied 
into the default pandoc template and using xelatex (which I have to because 
of the languages I need to use):

! You can't use `\spacefactor' in vertical mode.
\@->\spacefactor
                 \@m {}
l.249 \end{quote}

Unfortunately I'm a shameless straight-to-pdf user, with very little 
knowledge of Latex!


On Thursday, 20 November 2014 16:30:12 UTC, Jesse Rosenthal wrote:
>
>
> Hi Chris, 
>
> Chris Forster <chris.s...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>
> > Just looking for folks thoughts on this question: Is there an obvious 
> way 
> > to use a blockquote without starting a new paragraph immediately after 
> it? 
> > Here is my example. 
>
> I brought this question up a couple of years back: 
>
> https://groups.google.com/forum/#!topic/pandoc-discuss/OL_7b8EW0q4 
>
> The issue is basically that a pandoc paragraph is a collection of 
> inlines, so there's no good way for another block to go inside of 
> it. And there wouldn't be a good representation of it in html, etc. 
>
> There are two things you can do for LaTeX: 
>
>   1. Add something to your LaTeX preamble to take care of this. Here's 
>      what I have, more or less, in my personal macro package: 
>
>      ~~~ 
>      \newcommand{\gobblepars}{% 
>         \@ifnextchar\par% 
>             {\expandafter\gobblepars\@gobble}% 
>             {}} 
>
>      \newcommand{\forcepar}{\par} 
>
>      \newcommand*{\HungryQuotes}{% 
>         \AfterEndEnvironment{quote}{\expandafter\gobblepars}% 
>      } 
>      ~~~ 
>
>      And then I just put `\HungryQuotes` in the preamble to take care of 
> it. 
>
>
>
>   2. Run a script on the LaTeX output to remove the blank lines: 
>
>      ~~~ 
>      pandoc -s -S --template=article paper2.text -t latex | \ 
>      python2 -c "import sys; print 
> sys.stdin.read().replace('\\\end{quote}\n\n', 
> '\\\end{quote}\n').replace('\n\n\\\begin{quote}', '\n\\\begin{quote}')" 
>      ~~~ 
>
>      or the like. 
>
> The first option requires less intervention and allows you to go 
> straight to pdf. The second option produces cleaner tex files if you 
> want them. 
>
> Hope this helps, 
> Jesse 
>
>
>
>

-- 
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/ca77cf85-4f80-4388-ba68-54f89c6e9995%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2015-02-19 15:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 16:13 Chris Forster
     [not found] ` <a363e1bd-5346-4dd1-ac62-b3514fbd4ca9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-20 16:30   ` Jesse Rosenthal
     [not found]     ` <878uj5bzrh.fsf-4GNroTWusrE@public.gmane.org>
2014-11-21 21:58       ` Chris Forster
     [not found]         ` <9a4b3a78-908e-40e5-aaf9-9b415d91a432-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-11-21 22:33           ` Daniel Staal
2015-02-19 15:13       ` david.pw.smith-Re5JQEeQqe8AvxtiuMwx3w [this message]
     [not found]         ` <ca77cf85-4f80-4388-ba68-54f89c6e9995-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-19 15:27           ` Jesse Rosenthal

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=ca77cf85-4f80-4388-ba68-54f89c6e9995@googlegroups.com \
    --to=david.pw.smith-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=chris.s.forster-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).