Menu

#347 document that ragged-bottom = #t overrides ragged-last-bottom

Invalid
nobody
None
abandoned
Documentation
2015-08-21
2007-04-08
Anonymous
No

Originally created by: *anonymous

Originally created by: gpermus@gmail.com

%% ragged-last-bottom=##f doesn't work if ragged-bottom is set to true

\version "2.11.21"
\paper{
  ragged-right=##t
  ragged-bottom=##t
  ragged-last-bottom=##f
}
\score{
  \new Staff{
    \unfoldRepeats { \repeat volta 18 { c' d' e' f' \break} }
  }
}

Discussion

  • Google Importer

    Google Importer - 2008-11-15

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

    This is the same behaviour as we use for ragged-right and ragged-last, and it seems
    sane to me (although I guess it isn't documented: if ragged-bottom is true, then it
    overrides ragged-last-bottom). Is there a compelling reason to support a
    configuration where we want to space the last page (or line) nicely while all the
    previous pages (or lines) are ragged?

     
  • Google Importer

    Google Importer - 2008-11-15

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

    This arose from a really nasty page turn.  The score (for 2 violas) is 4 pages, with only one rest.  The page-use
    is:
    - 60% of a page
    - 50% of a page  (ending with a 4-bar rest for one viola)
    - 100%
    - 100%

    The last page would look slightly better if it were spread evenly, but the second page looks ridiculous when it
    was spread.  That said, this is a highly unusual occurance, and I won't object if we just update the docs with
    this info and close the issue.

     
  • Google Importer

    Google Importer - 2008-11-15

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

    Mao, I forgot I was logged in to google as a different user.  This is Graham; the account is my throw-away
    massively-spammed account.

     
  • Google Importer

    Google Importer - 2008-11-16

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

    Ragged is currently used in 2 ways: to determine the page breaking (what looks good
    normally might look bad with ragged spacing) and for actually laying out the systems.
    What if we put in some functionality to separate these uses and allowed better tuning
    for the part that doesn't affect page breaking? This is much nicer because things are
    tricky if we want to enhance the page-breaking effects of ragged.

     
  • Google Importer

    Google Importer - 2008-11-16

    Originally posted by: lemzw...@googlemail.com

    Can you give an example where `ragged page breaking' gives a different appearance?  I
    can't imagine a situation where page breaking depends on raggedness and not on the
    available vertical (stretchable?) space.

     
  • Google Importer

    Google Importer - 2008-11-17

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

    In ragged spacing, we refuse to compress springs and we don't penalize the last page
    for bad layout. AFAICR, these are the only differences and they apply to both
    vertical and horizontal spacing.

     
  • Google Importer

    Google Importer - 2015-08-11

    Originally posted by: dak@gnu.org

    Issue 347: document that ragged-bottom = #t overrides ragged-last-bottom

    http://codereview.appspot.com/257280043

    Summary: document that ragged-bottom = #t overrides ragged-last-bottom
    Owner: dak@gnu.org
    Labels: -Type-Defect -Priority-Medium Type-Documentation Patch-new
    Status: Started

     
  • Google Importer

    Google Importer - 2015-08-11

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

    Passes make, make check and a full make doc.

    Labels: -Patch-new Patch-review

     
  • Google Importer

    Google Importer - 2015-08-11

    Originally posted by: dak@gnu.org

    (No comment was entered for this change.)

    Labels: -Patch-review Patch-abandoned
    Owner: ---
    Status: Accepted

     
  • Google Importer

    Google Importer - 2015-08-21

    Originally posted by: tdanielsmusic

    The patch was abandoned after it was realised that the change could not unambiguously be considered an improvement.  In fact the current wording is correct and actually succinctly covers the point of this issue, although the meaning is rather subtle.  There was no support for elaborating it.

    Closing the issue as invalid.

    Status: Invalid