public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "kurt.pfeifle via pandoc-discuss"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Re-open #2889? Or create a new bug?
Date: Mon, 2 May 2016 08:36:08 -0700	[thread overview]
Message-ID: <20160502153607.GB43753@MacBook-Air-2.local> (raw)
In-Reply-To: <6f5f70b7-802d-4fcb-ba05-e211149c890a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

It seems to be a LaTeX issue, not a pandoc issue.

If you want, you could use pandoc to produce a LaTeX file,
reproduce the problem using pdflatex, and post to, say,
the tex stackexchange site to see if they have any
suggestions.


+++ kurt.pfeifle via pandoc-discuss [May 02 16 07:57 ]:
>   I don't know if (or how) I could re-open issue #2889, or wether I
>   should start a new issue.
>   However, I'm experiencing the same (I think) page-overflowing bug as in
>   issue #2889. In my case I've been using no images, no floats and no
>   tables (unlike the OP for issue #2889), only headlines so far without
>   any paragraph texts (since this/was is the early drafting of a longer
>   document).
>   Please have a look again. My last comment on (now closed) issue #2889
>   provides more details, including a link to a Gist containing a Markdown
>   example triggering the bug.
>   (This is in no way important to me because I guess the bug doesn't show
>   up once more text paragraphs are there, and I would know how to work
>   around it. However, the bug may show up un-expectedly at places where
>   the Markdown isn't as "extreme" as it is in my example. Or the real
>   reason for the bug being triggered by images, floats and tables on a
>   single page may have been wrongly assessed.)
>
>   --
>   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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/6f5f70b7-802d-4fcb-
>   ba05-e211149c890a%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/6f5f70b7-802d-4fcb-ba05-e211149c890a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
>   4. https://groups.google.com/d/optout


  parent reply	other threads:[~2016-05-02 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 14:57 kurt.pfeifle via pandoc-discuss
     [not found] ` <6f5f70b7-802d-4fcb-ba05-e211149c890a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-05-02 15:36   ` John MacFarlane [this message]
     [not found]     ` <20160502153607.GB43753-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2016-05-02 15:44       ` kurt.pfeifle via pandoc-discuss
2016-05-02 15:52   ` John Muccigrosso
2016-05-02 16:33   ` Joost Kremers
     [not found]     ` <87mvo8zafi.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2016-05-02 18:00       ` BP Jonsson
2016-05-03 10:27 ` Ulrike Fischer
     [not found]   ` <1m7ye3farembp.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2016-05-03 18:39     ` John MACFARLANE
     [not found]       ` <20160503183915.GB21146-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2016-05-05 18:30         ` BP Jonsson

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=20160502153607.GB43753@MacBook-Air-2.local \
    --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).