#823 Enhancement: reimplement ligature brackets using a more appropriate interface

[Anonymous]

Originally created by: *anonymous

Originally created by: v.villenave
Originally owned by: v.villenave

% So far, ligature brackets are printed (mis)using the
% tuplet-bracket-interface instead of the line-spanner-interface.
% This prevents ligatures from being printed after a line break:

\version "2.13.3"

\paper{ ragged-right=##t }
\relative c' {
c2 \[d2 \break
e2\] e2
}

[Google Importer]

Originally posted by: v.villenave

Neil added a comment on the bug list:
"
Now that I've taken a closer look at the code, I can see why ligature
brackets use the tuplet bracket infrastructure: it allows them to take
advantage of the code which calculates the correct slope when spanning
a beam or encompassing noteheads; this is something that's missing
from line spanners, which default to horizontal unless the user tweaks
'Y directly.
"

Summary: Enhancement: reimplement ligature brackets using a more appropriate interface

[Simon Albrecht]

Issue [#3037] fixed the problem with line breaks, so is there any remaining reason why this would be considered necessary? It doesn’t seem like the functionality of tuplet brackets is serving ligature brackets badly, and why reinvent the wheel?