Menu

#3341 formatting bug after a few pages

Verified
nobody
Defect
2014-02-20
2013-05-01
Anonymous
No

Originally created by: *anonymous

Originally created by: Elu...@gmail.com
Originally owned by: k-ohara5...@oco.net

Werner Lemberg has reported strange differences in formatting from page 6 to 9 (p. 10 being the same as the 1-5)

here is the code:
\version "2.16.0"

\paper {
  ragged-bottom = ##t
}

music = \relative c' { \repeat unfold 20 c2 }

\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music
\pageBreak
\music

this behavior can be followed back to 2.15.19 (2.15.10 doesn't compile)

Discussion

  • Google Importer

    Google Importer - 2013-05-23

    Originally posted by: dak@gnu.org

    It's probably worth noting that with print-page-number = ##f and tagline = ##f the relevant output remains quite the same even though the unformatted material on each page is then indeed identical.  So the strange formatting does not seem related to page number metrics or similar minuscule differences.

     
  • Google Importer

    Google Importer - 2013-05-23

    Originally posted by: dak@gnu.org

    Ok, tripling the number of pages does not change the number of strange pages, and they still occur at the end with the exception of the very last page.

    Here is my theory: when the remaining material is no longer sufficient for filling a whole page, LilyPond starts stretching it because she thinks it will be prettier to get the pages filled.  That she has no chance doing so because a \pageBreak occurs before that, and that she has no need to do so because we have ragged-bottom set does not occur to her apparently.

     
  • Google Importer

    Google Importer - 2013-11-13

    Originally posted by: k-ohara5...@oco.net

    http://codereview.appspot.com/24100045/

    Labels: Patch-new
    Owner: k-ohara5...@oco.net
    Status: Started

     
  • Google Importer

    Google Importer - 2013-11-14

    Originally posted by: pkx1...@gmail.com

    Patchy the autobot says: passes make, make check and a full make doc.

    Labels: -Patch-new Patch-review

     
  • Google Importer

    Google Importer - 2013-11-16

    Originally posted by: pkx1...@gmail.com

    Patch on countdown for Nov 19th - 06:00 GMT

    Labels: -Patch-review Patch-countdown

     
  • Google Importer

    Google Importer - 2013-11-19

    Originally posted by: pkx1...@gmail.com

    Patch counted down - please push

    Labels: -Patch-countdown Patch-push

     
  • Google Importer

    Google Importer - 2013-11-19

    Originally posted by: k-ohara5...@oco.net

    (No comment was entered for this change.)

    Labels: -Patch-push Fixed_2_19_0
    Status: Fixed

     
  • Google Importer

    Google Importer - 2013-12-10

    Originally posted by: k-ohara5...@oco.net

    Best to have the page-breaking fixes appear in the same release.
    two commits
    [r7024311679e68b26f72d595eb3ced0e7179690c0]
    [rf3e5179c49f83c1ec4c69e58581331fa07a41777]

    Labels: Backport_2_18_1

     
  • Google Importer

    Google Importer - 2014-01-06

    Originally posted by: Elu...@gmail.com

    (No comment was entered for this change.)

    Status: Verified

     
  • Google Importer

    Google Importer - 2014-02-16

    Originally posted by: dak@gnu.org

    Pushed to stable/2.18 as
    commit [rf940442ecf0e5485c24ea3bf3d6b1ad660703f6a]
    Author: Keith OHara <k-ohara5a5a@oco.net>
    Date:   Tue Nov 19 16:46:40 2013 -0800

        pge-breaking: do not try to fill ragged-pages; issue 3341

    commit [r9658a9f294603f4918bef6a76441f1f38ed73511]
    Author: Keith OHara <k-ohara5a5a@oco.net>
    Date:   Wed Nov 13 13:47:28 2013 -0800

        page-breaking: keep the degree of stretching in Line_details; issue 3341
       
        The prioritization of cache_line_details() needs this information
        to recognize the best configurations.

    Labels: -Backport_2_18_1 Fixed_2_18_1
    Status: Fixed

     
  • Google Importer

    Google Importer - 2014-02-20

    Originally posted by: Elu...@gmail.com

    (No comment was entered for this change.)

    Status: Verified

     
MongoDB Logo MongoDB