lilypond-devel
[Top][All Lists]
Advanced

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

Re: Issue 3128: add Haydn-style turns to Feta (issue 340660043 by addres


From: lilypond
Subject: Re: Issue 3128: add Haydn-style turns to Feta (issue 340660043 by address@hidden)
Date: Tue, 10 Apr 2018 10:20:17 -0700

On 2018/04/10 09:47:31, Lukas-Fabian Moser wrote:
This is gorgeous! Thanks very much!

Is the \haydnturn supposed to be symmetrical w.r.t. the stem? To me it
looks as
if it weighs slightly more on the left, but maybe I'm wrong? (And I'm
also not
sure if this would be a problem if I were right.)

The symbol is 100% symmetrical as I tested with the following code:

\markup \fill-line {
  \fontsize #20 \overlay {
    \rotate #180 \with-color #red \musicglyph "scripts.haydnturn"
    \musicglyph "scripts.haydnturn"
  }
}

But maybe it’s not well-balanced nethertheless?

(The Henle score that prompted me to ask in the first place - Haydn
Symphony Nr.
13 in Haydn, Werke, Reihe I, Band 3, ed. Braun/Gerlach - has a less
curly
version of the \haydnturn, but I like your design better.)

Yes, I don’t like the Henle (1972) version as well. I copied the fact
that it’s less bold than the turn and mordent but I made it a little but
more curly and centered the stem vertically (Henle makes the upper half
of the stem longer than the lower).

As for the \slashturn: I think the lenght of the stem is okay. But I
started to
wonder if the \slashturn should really be as "thick" at its waist as
the usual
\turn. Maybe there is a slight disbalance between the two parts (turn
vs.
slash).

You’re right. \turn and \reverseturn are 10% thicker at the very center
than at the “outer” thick parts. Making the \slashturn 4% thinner
instead looks good to me.

Maybe that’s also the reason for imbalance in the \haydnturn. Same
thickness instead of 10% thicker might look better.

I’ll make a patch set for slimmer center parts and attach the resulting
PDF to the sourceforge issue.


https://codereview.appspot.com/340660043/

reply via email to

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