Re: Collisions on OttavaBracket in the SVG output (BUG)

[Dan Eble]

On Feb 6, 2020, at 18:35, Paolo Prete <address@hidden> wrote:
> 
> (I re-post this here, because it's a bug and maybe you have an easy fix for
> it)

Paolo,

I'm not sure where you're re-posting from, but the expected forum for bug 
reports is https://lists.gnu.org/mailman/listinfo/bug-lilypond .  The audience 
is not the same as the development list, so I would recommend posting directly 
to the bug list if you need to report any bugs in the future.  I've forwarded 
this message for you.

Cheers.

> Hello,
> 
> please consider this snippet:
> 
> %%%%%%%
> {
> \override Staff.TextSpanner.bound-details.left.text = \markup { \small
> \bold "Rit." }
> \once \override Slur.outside-staff-priority = 100
> \once \override DynamicText.outside-staff-priority = 200
> \once \override TupletBracket.outside-staff-priority = 300
> \once \override Staff.OttavaBracket.outside-staff-priority = 400
> \once \override Staff.TextSpanner.outside-staff-priority = 500
> \once \override TextScript.outside-staff-priority = 600
> 
> \override TupletBracket.bracket-visibility = ##t
> \override TupletBracket.direction = #UP
> \tuplet 5/4 { \ottava #1 c'''8^>^\mf[(^\markup{ legato }\startTextSpan  e''
> f''' g''' e'''']} c''''4\stopTextSpan \ottava #0 c'')
> }
> %%%%%%%
> 
> On 2.19.83 the SVG output produces a collision on the OttavaBracket, which
> is not placed at the right outside-staff-priority order. The PDF output is
> ok. Is there a workaround/fix for this?
> 
> thanks