#3017 Finger numbers and string numbers are placed wrongly when not using chordbraces

[Anonymous]

Originally created by: *anonymous

Originally created by: k-ohara5...@oco.net

When we mark notes inside a braced chord with fingering, string numbers, and stroke fingers,  LilyPond uses the "New_fingering_engraver".  This engraver sorts the notation according to note-heads by adding the note-head staff-position to the effective 'script-priority (which is the reason that the predefined script-priorities differ by large steps, typically 100).

When we mark notes outside a <>-braced chord, LilyPond uses the "New_fingering_engraver" for string numbers and stroke fingers, but the old "Fingering_engraver" for fingering.   The "Fingering_engraver" adjusts 'script-priority based on order of input, not note-position.

Having two different engravers arranging related items by different rules confuses the placement.   The attached image uses <>-braced chords before the double bar, no <>-braces after the double bar.

[Google Importer]

Originally posted by: mts...@gmail.com

Could we just eliminate the Fingering_engraver and Script_engraver?

[Google Importer]

Originally posted by: dak@gnu.org

Well, something would still have to do their work: per-moment-of-time fingerings and scripts are quite possible to come across using parallel music or per-chord post-events.