[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR updates: was: polychords: a working solution
From: |
Thomas Morley |
Subject: |
Re: LSR updates: was: polychords: a working solution |
Date: |
Sat, 25 Feb 2012 02:30:57 +0100 |
Hi,
2012/2/19 Thomas Morley <address@hidden>:
> use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.ly
> I simply added added lowercase? To the definition of
> my-chord-name->pop-markup
> Of course lowercase? Is of no use here. A better fix would be more invasive.
I made some additions. Now \set chordNameLowercaseMinor = ##t and \set
chordNoteNamer = #note-name->german-markup is possible.
Shall I integrate it or use the simple fix?
Cheers,
Harm
use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords-rev-01.ly
Description: Text Data
- Re: LSR updates: was: polychords: a working solution, (continued)
- Message not available
- Re: LSR updates: was: polychords: a working solution, David Nalesnik, 2012/02/26
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/27
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/25
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/25
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/25
- Re: LSR updates: was: polychords: a working solution, David Kastrup, 2012/02/23
- Re: LSR updates: was: polychords: a working solution,
Thomas Morley <=
- Re: LSR updates: was: polychords: a working solution, David Kastrup, 2012/02/25
- Re: LSR updates: was: polychords: a working solution, Thomas Morley, 2012/02/19