[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5174 Entire \

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5174 Entire \tempo marking should avoid excessive printing commands
Date: Fri, 24 Aug 2018 15:49:18 -0000

[issues:#5174] Entire \tempo marking should avoid excessive printing commands

Status: Fixed
Labels: Fixed_2_21_0
Created: Tue Aug 15, 2017 11:10 PM UTC by Étienne Beaulé
Last Updated: Thu Sep 07, 2017 03:14 PM UTC
Owner: Étienne Beaulé

Currently, separate components of the tempo tag are held in different <text tags, each with a <tspan without attributes. This is wasteful, and can make text ugly. KCC.cropped.svg shows how this fragmentation causes a bad result (ignoring issue [#3778] with \override Score.MetronomeMark.vertical-skylines = #'()). The text is separated into 5 text blocks, whereas only 2 are necessary (before/after note).

There are a few issues at play here:

I can't seem to find where the issue is occuring for points 2 & 3, but by specifying the position of each component (and problems in concatenating them, the spacing is off and the syntax messier.

Making these changes manually in the example, there were 10 units of space between the indication and metronome mark, and with an odd cause in Lilypond's text handling.

Sent from because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Testlilyissues-auto mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]