I was asking if there was a solution for this in the newsgroup, but it seems that there isn't.

In Germany, it is quite common to write moll chords instead of "Am" as just "a" and the others suchlike.

As we would like to enhance our songbook with lilypond, we would be able to have everything in an homogenous look.

It appears that Thomas Morgan has been working on a Patch in September 2009. According to Carl, " Thomas is continuing to work on it, with a new architecture. He has less time right now than he used to, so it's moving forward more slowly than it was, but it is moving forward. "

Here's a patch, originally provided by Thomas Morgan in 2009-09. It was meant as a temporary one-feature solution, since Thomas is/was working on a more general approach. I could successfully patch a "binary" installation of 2.13.16 (like several olders) on OSX 10.5 and guess it would work on every OS.

Hraban, this patch is incomplete, since `conditional-string-downcase' isn't defined; the following code should be added to prevent crashes:

(define (conditional-string-downcase str condition) (if condition (string-downcase str) str))

Cheers, Neil

There is a new version of the Patch: http://lists.gnu.org/archive/html/lilypond-devel/2010-05/msg00512.html

Patch was pushed. Thanks, Hraban!

I've never typed scores with chords, so i could not find a way to verify (chordNameLowercaseMinor = ##f ? how? where?)

Please be so kind and provide a minimal example --- how this feature may be used and, more or less, verified .)

Thanks!

ps. If someone else would "verify" it --- i wouldn't mind. But issue containing a tiny example is a good thing.

I think that James Bailey is working on verifying this issue. It needs to have a regression test added, and perhaps some documentation.

A file that demonstrates the functionality is available at

http://article.gmane.org/gmane.comp.gnu.lilypond.devel/29422/

but it's not yet formatted for a regression test.

For completeness, I'lll attach a Tiny example here, but we really shouldn't close the issue until the regtest is added.

I have pushed a regtest and updated the documentation.