- **status**: Fixed --> Verified
---
** [issues:#3692] Fingering collision with accidentals**
**Status:** Verified
**Labels:** Fixed_2_21_0
**Created:** Sat Nov 30, 2013 09:17 AM UTC by Anonymous
**Last Updated:** Sun Sep 16, 2018 02:16 PM UTC
**Owner:** Torsten Hämmerle
**Attachments:**
-
[fingering.preview.png](https://sourceforge.net/p/testlilyissues/issues/3692/attachment/fingering.preview.png)
(4.6 kB; image/png)
http://codereview.appspot.com/341470043
*Originally created by:* *anonymous
*Originally created by:*
[[email protected]](http://code.google.com/u/101609726059656965678/)
Fingerings do not take accidentals into account, and fingerings align over the
first note inout of a chord, rather than centering over the whole chord.
\version "2.17.96"
\{
<e'' f'' cis'''>1 ^1^2^5
\}
From Keith Ohara:
"Unfortunately this is a different bug -- or two -- so it will
not be fixed at the same time as collisions between Fingerings.
\(1\) LilyPond has never looked at Accidentals when placing Fingering;
until recently that caused only small overlaps with sharps because
the Fingering did not previously fit so close to the chord.
\(2\) Fingering on a chord as a whole should center over the main column
of note-heads; instead it centers over the first-input note.
So, you can do the same as we did when using version 2.12: rearrange
the order of pitches in the chord so a main-column note comes first.
\{ <f'' e'' cis'''>1 ^1^2^5 \}
\*\*\*\*\*\*\*\*\*\*\*
From Janek :
This is similar to issues
[https://code.google.com/p/lilypond/issues/detail?id=2245](#2245)
[https://code.google.com/p/lilypond/issues/detail?id=2451](#2451)
[https://code.google.com/p/lilypond/issues/detail?id=2452](#2452)
and i believe to solve it in a general way we would have to teach
lilypond about different kinds of extents - see:
[http://lists.gnu.org/archive/html/lilypond-devel/2012-06/msg00230.html](http://lists.gnu.org/archive/html/lilypond-devel/2012-06/msg00230.html)
[https://code.google.com/p/lilypond/issues/detail?id=3239](#3239) \(sorry, that
issue got pretty messy\).
Currently the work i started on this is waiting until 2.18.0 is out...
What about leaving it for now and attacking this together after 2.18?
\*\*\*\*\*\*\*\*\*\*\*\*
Possibly a Known Issue in NR 1.7.1 would be in order.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list._______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
