public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'SBJ' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown to LaTeX: unwanted newlines around LaTeX environment
Date: Tue, 3 Oct 2017 13:43:32 -0700	[thread overview]
Message-ID: <20171003204332.GA14228@protagoras> (raw)
In-Reply-To: <8729b9a5-1aff-4d3a-a17f-06d8a63beefa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

The dev version of pandoc will not give you a blank line
in this case -- it knows that equation environments can
occur inline.

+++ 'SBJ' via pandoc-discuss [Oct 03 17 09:51 ]:
>   It appears that the Markdown reader, as a rule, treats any unknown
>   environment as block-level content (rather than inline). While this
>   seems to be the desired behaviour, it has side effects when the output
>   format is (newline-sensitive) LaTeX. This was previously reported here:
>     * [1]https://github.com/jgm/pandoc/issues/3309#issuecomment-284679731
>     * [2]https://groups.google.com/forum/#!searchin/pandoc-discuss/latex$
>       20environment|sort:relevance/pandoc-discuss/P3fV_0jw9-U/DUpSrWYxaAk
>       J
>
>   This affects users wanting to create LaTeX documents in a convenient
>   fashion by first writing a Markdown file containing occasional LaTeX
>   environments, then converting to LaTeX and feeding the resulting LaTeX
>   into a pdflatex workflow. The extra newlines produced in this process
>   affect the LaTeX parsing, leading to unwanted (and inconsistent)
>   vertical space in the final document (see simple example below).
>   Is there a way to make Pandoc omit the newlines?
>   $ cat test.md
>   Testing environment
>   \begin{equation}
>       i^2=-1
>   \end{equation}
>   for whitespace.
>   $ pandoc -f markdown -t latex -o test.tex test.md
>   $ cat test.tex
>   Testing environment
>   \begin{equation}
>       i^2=-1
>   \end{equation}
>   for whitespace.
>   $ pandoc --version
>   pandoc 1.19.2.4
>   Compiled with pandoc-types 1.17.0.5, texmath 0.9.4.2, skylighting
>   0.1.1.5
>   [...]
>
>   --
>   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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [4]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [5]https://groups.google.com/d/msgid/pandoc-discuss/8729b9a5-1aff-4d3a-
>   a17f-06d8a63beefa%40googlegroups.com.
>   For more options, visit [6]https://groups.google.com/d/optout.
>
>References
>
>   1. https://github.com/jgm/pandoc/issues/3309#issuecomment-284679731
>   2. https://groups.google.com/forum/#!searchin/pandoc-discuss/latex$20environment|sort:relevance/pandoc-discuss/P3fV_0jw9-U/DUpSrWYxaAkJ
>   3. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   4. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   5. https://groups.google.com/d/msgid/pandoc-discuss/8729b9a5-1aff-4d3a-a17f-06d8a63beefa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   6. https://groups.google.com/d/optout


  parent reply	other threads:[~2017-10-03 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 16:51 'SBJ' via pandoc-discuss
     [not found] ` <8729b9a5-1aff-4d3a-a17f-06d8a63beefa-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-03 20:43   ` John MACFARLANE [this message]
2017-10-04 12:35     ` 'SBJ' via pandoc-discuss
     [not found]       ` <bdbfaa4e-8889-4eec-9831-9901eb39e20f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-04 17:24         ` John MACFARLANE

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=20171003204332.GA14228@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).