Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small

[David Kastrup]

address@hidden writes:

> Comment #9 on issue 678 by Carl.D.Sorensen: Enhancement: Add option to
> make moll chords small
> http://code.google.com/p/lilypond/issues/detail?id=678
>
> I think that James Bailey is working on verifying this issue.  It
> needs to have a regression test added, and
> perhaps some documentation.

It is my opinion that an implementation needing to touch
define-context-properties.scm for every new chord naming scheme again is
a mistake.

A different (or tweaked) _naming_ scheme is something that should be
achievable with pure user-level code without requiring deep surgery.
Meddling with define-context-properties.scm or other code that is a part
of Lilypond may be needed _now_ to get there.  But it should be done in
a way that does not require reopening an issue whenever somebody needs a
new naming scheme for some piece of typography.

Nor should it be a global setting.

I attach a scan from a quite standard accordion score:

Scanned Document.pdf
Description: Adobe PDF document

You see that it is customary to use a standard piano chord naming scheme
for the harmonies _above_ the top staff, and a scheme with _upper case_
bass notes and _lower case_ chord names for the chord buttons in the
lower staff.

It would not do to just use textual markup here since textual markup is
not transposable.

-- 
David Kastrup