[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1219 in lilypond: Broken tie may become a too small dot
From: |
lilypond |
Subject: |
Issue 1219 in lilypond: Broken tie may become a too small dot |
Date: |
Sat, 14 Aug 2010 15:09:24 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1219 by brownian.box: Broken tie may become a too small dot
http://code.google.com/p/lilypond/issues/detail?id=1219
Yes! --- this may be duplicate of issue 840.
Here is no time signature, however, and no accidentals in chords.
I've attached a sample source file to reproduce --- sorry, it is really
more eloquent than a minimal example.
And an image --- a crop of a real score.
Please take a look --- there should be a tie in basso.
Set to "medium", but actually i would rather set priority to high because
this defect is TOO HARD to catch --- one could need to inspect score as if
it was "clicked" (or even typed) with Finale, sorry.
Again, please do not mind these *bytes of samples --- i promise i will
attach only tiny examples!-)
I just wanted to show that this defect is _really_ embarrassing... Yes,
there _is_ a workaround (and for issue 840? --- not tested), but the main
problem is to catch the case...
Attachments:
test.ly 1.1 KB
test.png 16.5 KB
- Issue 1219 in lilypond: Broken tie may become a too small dot,
lilypond <=