Comment #8 on issue 1061 by shingarov: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
I have created Bug 1062 for discussion of the regression caused by 879043.
These are
two different issues; after fixin
Status: Accepted
Owner: shingarov
Labels: Type-Defect Regression Priority-High
New issue 1062 by shingarov: Pure-height of a system only takes staves into
account, but not other objects
http://code.google.com/p/lilypond/issues/detail?id=1062
In patch 879043 fixing bug 1053, when estimating th
Updates:
Owner: shingarov
Comment #7 on issue 1061 by shingarov: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
(No comment was entered for this change.)
--
You received this message because you are
Updates:
Status: Fixed
Comment #7 on issue 1053 by shingarov: Severe overestimation of line height
for significantly non-rectangular systems
http://code.google.com/p/lilypond/issues/detail?id=1053
(No comment was entered for this change.)
--
You received this message because you are
On Thu, 22 Apr 2010 13:39:35 -0700, Joe Neeman wrote:
Never mind, I just did that hunk manually and pushed.
Then, I am marking bug 1053 as fixed.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lily
Comment #6 on issue 1061 by joeneeman: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
I'm not sure what the question is...
A column is a Grob of type Paper_column. There are 2 paper columns for each
momen
Comment #5 on issue 1061 by shingarov: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
Always been confused by this (when deciding what to pass as "start"
and "end" for
example):
What's the difference betw
Comment #4 on issue 1061 by joeneeman: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
Fortunately, the begin/rest distinction is very simple: a grob belongs to
the
beginning of a line if, and only if, it b
Comment #3 on issue 1061 by shingarov: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
Regarding lyric descenders, this is not really a problem
with pure height estimation; rather, it is a problem in
approxi
Comment #2 on issue 1061 by Vialena.Parvy: Pure-height inaccuracy very
large when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
factor out axis-group-interface.cc:231-265 into a
separate function and to modify it so that it uses
begin_of_line_e
Comment #1 on issue 1061 by joeneeman: Pure-height inaccuracy very large
when skyline significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
I only get the attached output when the patch for Issue 1053 is applied. I
think this
points to a problem in System::pa
I was talking about barlines and staff lines (well, mostly barlines that print
out
way too thin by default at some smaller score sizes in Finale). Such thin
lines
are certainly for squinting. And those only get worse when you photocopy, so
to start in the middle of a piece for a rehearsal, s
Updates:
Status: Verified
Comment #7 on issue 906 by brownian.box: gs fails in jail mode unless run
separately with sudo (error 32512)
http://code.google.com/p/lilypond/issues/detail?id=906
(No comment was entered for this change.)
--
You received this message because you are listed
"Boris Shingarov" writes:
> What makes me really depressed about the situation with pure-height,
> is that we have fixed a number of "reasonable" bugs in this area
> (intersystem begin/rest, overridden stem length, deprecated space,
> padding of markup -- these are the ones that I did in the imme
the code
\version "2.13.18"
\layout {
\context {
\Staff
\override StringNumber #'stencil = ##f
} }
{ 8 }
produces the error: cannot align on self: empty element
however, the pdf is produced correctly.
adding
\override StringNumber #'self-alignment-X = ##f
turns this error off.
s
Jonathan Wilkes writes:
> Hi Alexander, On your point about technical restrictions: I would
> just say that by the time a musician becomes a professional he/she has
> read thousands of scores with rounded notes, non-pointy angles, heavy
> dynamics font, etc.
[...]
> playing music, which I
16 matches
Mail list logo
