[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 243 in project lilypond
From: |
codesite-noreply |
Subject: |
Issue 243 in project lilypond |
Date: |
Thu, 18 Jan 2007 12:20:36 -0800 |
Issue 243: really weird line breaks
http://code.google.com/p/lilypond/issues/detail?id=243
Comment #6 by joeneeman:
OK, if you don't want to maximise the shortest line then you can disregard my
second
point.
The problem is this: when we space a justified line, we assign it a penalty
based on
how much force is required to stretch or compress it into position. When we
aren't
justifying the lines, this force will always be zero. But we need to assign some
penalty anyway, to reflect the fact that an almost-full line is better than an
empty
line.
The current method bases the penalty on the amount of force that would be
required to
stretch the line to its full width. You want to change the penalty so that it is
based on the amount of space to the right of the line. These can be quite
different
when two lines have springs of different lengths and stiffness.
Anyway, I've made the change in my working copy and it gives the results you
want.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 243 in project lilypond, codesite-noreply, 2007/01/17
- Issue 243 in project lilypond, codesite-noreply, 2007/01/17
- Issue 243 in project lilypond, codesite-noreply, 2007/01/18
- Issue 243 in project lilypond, codesite-noreply, 2007/01/18
- Issue 243 in project lilypond, codesite-noreply, 2007/01/18
- Issue 243 in project lilypond, codesite-noreply, 2007/01/18
- Issue 243 in project lilypond,
codesite-noreply <=
- Issue 243 in project lilypond, codesite-noreply, 2007/01/31
- Issue 243 in project lilypond, codesite-noreply, 2007/01/31