Re-open #2889? Or create a new bug?

Re-open #2889? Or create a new bug?

[kurt.pfeifle via pandoc-discuss]

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

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 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/6f5f70b7-802d-4fcb-ba05-e211149c890a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Re-open #2889? Or create a new bug?

[John MacFarlane]

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

Re: Re-open #2889? Or create a new bug?

[kurt.pfeifle via pandoc-discuss]

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



On Monday, May 2, 2016 at 5:36:22 PM UTC+2, John MacFarlane wrote:
>
> 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. 
>

Ok, thanks -- will do.


-- 
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/ea9af09c-231f-42c9-83b0-a81fcf877344%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Re-open #2889? Or create a new bug?

[John Muccigrosso]

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

On Monday, May 2, 2016 at 10:57:22 AM UTC-4, kurt.p...-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org wrote:
>
> 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.)
>

I hit this too at some point, doing the same thing you are, I think, 
creating an outline. IIRC, the problem is that headings can't have a page 
break after them, so without paragraph text, you never get a break. 
Discussion is here 
<https://groups.google.com/d/msg/pandoc-discuss/vAfu7w2TfFU/pIbEmIrCBwAJ>.

-- 
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/97ba7ab4-c0be-46f8-bad3-997604b91a81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Re-open #2889? Or create a new bug?

[Joost Kremers]

On Mon, May 02 2016, kurt pfeifle via pandoc-discuss wrote:
> 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).

I'd say this is not the same bug, since the original bug is related to
longtable, which your document doesn't use.

In fact, the effect you're seeing is probably not even a LaTeX bug but a
result of the fact that headings aren't supposed to be at the bottom of
the page. (La)TeX enforces this by putting a heavy penalty on inserting
a page break right after a heading. Normally, this has the effect of
moving the heading to the next page, but in your case, the algorithm is
confused, because there's no text before the heading (which has no
penalty against inserting a page break), but rather another heading,
which comes with the same heavy penalty against breaking the page right
after it.

In effect you're creating a series of text elements that do not allow
any page breaks between them. The only way to deal with this is to put
them all on the same page, even if this means overflowing the page.

A workaround is to put a \newpage after each heading, or some dummy
text, or even just a hard space. This is not something Pandoc can fix,
and fixing it in (La)TeX might even be undesirable if it increases the
possibility of headings appearing at the bottom of a page.


-- 
Joost Kremers
Life has its moments

Re: Re-open #2889? Or create a new bug?

[BP Jonsson]

Den 2016-05-02 kl. 18:33, skrev Joost Kremers:
> A workaround is to put a \newpage after each heading, or some dummy
> text, or even just a hard space. This is not something Pandoc can fix,
> and fixing it in (La)TeX might even be undesirable if it increases the
> possibility of headings appearing at the bottom of a page.

It can be fixed with a simple pandoc filter (not to be run on the 
final document!)

It inserts a raw latex block containing the command 
`\pagebreak[2]` after every heading, without the need to hardcode 
them in the source.

\pagebreak[2] is what you want here. It 'suggests' a pagebreak 
with a not too low penalty, and does not insert any extra space

/bpj

````python
#!/usr/bin/env python

"""
heading-breaks.py

A pandoc filter which inserts a raw \pagebreak[2] after headings,
so that LaTeX breaks pages between headings in outlines.
"""

import pandocfilters as pf

pagebreak = pf.RawBlock( 'latex', '\\pagebreak[2]' )

def filter_func(key, val, fmt, meta):
     if 'Header' != key:
         return None
     return [pf.Header(*val),pagebreak]


if __name__ == "__main__":
     pf.toJSONFilter(filter_func)
````

Re: Re-open #2889? Or create a new bug?

[Ulrike Fischer]

Am Mon, 2 May 2016 07:57:22 -0700 (PDT) schrieb kurt.pfeifle via
pandoc-discuss:

> 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. 

There are lots of (different) ways to get overfull pages. One is to
assemble enough material without legal break point.

http://tex.stackexchange.com/a/57861/2388




-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

Re: Re-open #2889? Or create a new bug?

[John MACFARLANE]

You could always put

    <!-- TODO -->

under each heading.

+++ Ulrike Fischer [May 03 16 12:27 ]:
>Am Mon, 2 May 2016 07:57:22 -0700 (PDT) schrieb kurt.pfeifle via
>pandoc-discuss:
>
>> 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.
>
>There are lots of (different) ways to get overfull pages. One is to
>assemble enough material without legal break point.
>
>http://tex.stackexchange.com/a/57861/2388
>
>
>
>
>-- 
>Ulrike Fischer
>http://www.troubleshooting-tex.de/
>
>-- 
>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/1m7ye3farembp.dlg%40nililand.de.
>For more options, visit https://groups.google.com/d/optout.

Re: Re-open #2889? Or create a new bug?

[BP Jonsson]

Den 2016-05-03 kl. 20:39, skrev John MACFARLANE:
> You could always put
>
>     <!-- TODO -->
>
> under each heading.

That doesn't help since the HTML comments aren't echoed in any way 
in the LaTeX output!


     $ pandoc -w latex
     # This is a heading

     <!-- TODO -->

     # This is another heading

     <!-- TODO -->
     ^D
     \section{This is a heading}\label{this-is-a-heading}

     \section{This is another heading}\label{this-is-another-heading}

By contrast the filter I suggested does work well without the need 
to put any ad hoc content in the file, temporary or not.  I 
(programmatically) made a markdown file with 200 level one 
headings separated by two empty lines each, then produced PDFs 
with and without the filter using both xelatex and pdflatex. The 
results speak for themselves: without the filter you get a single 
page with only as many of the headings as fit into it. With the 
filter you get several pages with as many headings as fit into 
each, with a page break following. The contents of the markdown 
file were the same in both cases.

>
> +++ Ulrike Fischer [May 03 16 12:27 ]:
>> Am Mon, 2 May 2016 07:57:22 -0700 (PDT) schrieb kurt.pfeifle via
>> pandoc-discuss:
>>
>>> 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.
>>
>> There are lots of (different) ways to get overfull pages. One is to
>> assemble enough material without legal break point.
>>
>> http://tex.stackexchange.com/a/57861/2388
>>
>>
>>
>>
>> --
>> Ulrike Fischer
>> http://www.troubleshooting-tex.de/
>>
>> --
>> 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/1m7ye3farembp.dlg%40nililand.de.
>>
>> For more options, visit https://groups.google.com/d/optout.
>