lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] Issue 3314 in lilypond: powerChords: powerChordSymbol sh


From: lilypond
Subject: [Lilypond-auto] Issue 3314 in lilypond: powerChords: powerChordSymbol should be same size of other chords
Date: Sun, 14 Apr 2013 12:51:07 +0000

Status: Accepted
Owner: ----
Labels: Type-Enhancement

New issue 3314 by address@hidden: powerChords: powerChordSymbol should be same size of other chords
http://code.google.com/p/lilypond/issues/detail?id=3314

Bug report:
https://lists.gnu.org/archive/html/bug-lilypond/2013-04/msg00074.html

%% Snippet
\version "2.14.2"

newPowerChordSymbol = {
  <c g>-\markup { \super "5" }
}

chExceptions = #( append
  ( sequential-music-to-chord-exceptions newPowerChordSymbol #t)
  ignatzekExceptions)

music = \chordmode {c:7 c:1.5 c:sus4}

\new ChordNames \chordmode {
% the 5 is currently much bigger than the 7 or sus4
  \powerChords \music
% it should match the size of the other numbers
  \set chordNameExceptions = #chExceptions \music
}

%% End of snippet

Comment from Harm:

Currently `powerChordSymbol´ is defined in /ly/chord-modifiers.ly and
finally used with `powerChords´ from `/ly/property-init.ly´

`powerChordSymbol´ is defined:

powerChordSymbol = {
  <c g>-\markup { \normal-size-super "5" }
  <c g c'>1-\markup { \normal-size-super "5" }
}

resulting in a normal-sized "5", not like other numbers in chords.

Therefore it is not a bug (it is indeed the intended behaviour),
though, Greg requests to give the "5" the same, smaller size and he
provides a method how to do it.

BTW, Greg refers to 2.14.2, though, it's the same with 2.17.15.

I think it's a legitimate feature request.
And I lean to agree with him.


Attachments:
        powerChords-request.png  7.5 KB

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

reply via email to

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