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 immediate
past, -- the slur fix from Jo
On Wed, 21 Apr 2010 20:37:52 -0400, Boris Shingarov wrote:
not closer to having reasonable trouble-free page layout, but starting
> to look at page overfill/underfill problems which are very deeply
> rooted in the nature of pure-height estimation.
I meant Bug 1061 in particular.
_
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1061 by shingarov: Pure-height inaccuracy very large when skyline
significantly non-rectangular
http://code.google.com/p/lilypond/issues/detail?id=1061
When the skylines are significantly non-rectangular, the inaccurac
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.
I think "beauty" in this sense is of the practical variety,
I became aware of the Essay rewrite through the bug list and had a quick
read-through of the new text. I agree it's an improvement over the old one, but
would like to point out three minor matters.
Typo: In the penultimate paragraph of _1.3 Automated engraving - Getting things
right_, please re
Comment #5 on issue 1000 by percival.music.ca: send texi2html patches
upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
I really, really doubt that anybody is going to volunteer.
*shrug*
Our texi2html init file is a complete mess, but it's no worse than any
other part of
ou
Comment #4 on issue 1000 by markpolesky: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
I'd prefer this to be done sooner than later, but I'm not
the one for the job. It looks like the final texi2html
release is imminent* and we don't want to miss it. W
Updates:
Labels: Maintainability
Comment #3 on issue 1000 by percival.music.ca: send texi2html patches
upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
One of us definitely needs to be involved. Throwing the entire init file
at them
without explanations would be cr
Updates:
Status: Verified
Comment #2 on issue 1037 by brownian.box: links to old manuals
http://code.google.com/p/lilypond/issues/detail?id=1037
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, or beca
Updates:
Status: Verified
Comment #10 on issue 1058 by brownian.box: Frequent Errors should be moved
from Usage to Learning
http://code.google.com/p/lilypond/issues/detail?id=1058
(No comment was entered for this change.)
--
You received this message because you are listed in the own
Updates:
Status: Verified
Comment #4 on issue 659 by brownian.box: alternative segno symbol
http://code.google.com/p/lilypond/issues/detail?id=659
Verified by running a regtest:
http://codereview.appspot.com/181144/patch/19001/20003
I wouldn't say that i know how it should be looking
Updates:
Status: Verified
Comment #2 on issue 348 by brownian.box: \unfoldRepeats { blah music } is
different from { blah {music} }!
http://code.google.com/p/lilypond/issues/detail?id=348
(No comment was entered for this change.)
--
You received this message because you are listed i
Comment #2 on issue 1000 by markpolesky: send texi2html patches upstream
http://code.google.com/p/lilypond/issues/detail?id=1000
Is it just a matter of asking the texi2html guys to look
over the lilypond-texi2html.init file or does one of us
need to get involved and explain some of texi2html bug
13 matches
Mail list logo
