Reviewers: ,
Message:
please review
Description:
Make chord-naming robust against unsetting majorSevenSymbol
This will likely be changed anyway as soon as rewriting
chord-names is seriously tackled.
At least it might be a reminder to take care of the possibility
a user wants to unset
W dniu 22 października 2010 16:47 użytkownik Carl Sorensen <
c_soren...@byu.edu> napisał:
> On 10/22/10 5:08 AM, "Janek Warchoł" > wrote:
>
> > Hi,
> > I'm from Poland and we use here a different chord naming convention: the
> main
> > differe
On 10/22/10 5:08 AM, "Janek Warchoł"
wrote:
> Hi,
>
> I'm from Poland and we use here a different chord naming convention: the main
> difference is that minor chords are written with lowercase and major chords
> are written with uppercase. I'd like to ad
Hi,
I'm from Poland and we use here a different chord naming convention: the
main difference is that minor chords are written with lowercase and major
chords are written with uppercase. I'd like to add this to Lily.
I found .ly files with alternative note names (used in other lan
Original-Nachricht
> Datum: Sat, 24 Jan 2009 08:10:15 -0700
> Von: "Carl D. Sorensen"
>Not quite. I want to make a facility that makes it easy for everyone to
>create their favorite way, if one of the defaults isn't what is wanted. And
>dolmetsch.com just provides a list of t
On 1/24/09 4:02 AM, "Tao Cumplido" wrote:
> I never use fret diagrams so I don't know how this predefined exceptions work.
You can get a description of how the predefined fretboards work, including
the addition of new diagrams, by looking in the Notation Reference, Section
2.4.1 Common notati
s and I'd be happy to help out with expanding your
exceptions list.
Regards,
Tao
Original-Nachricht
> Datum: Fri, 23 Jan 2009 22:48:41 -0500
> Von: David Stocker
> An: "Carl D. Sorensen"
> CC: lilypond , lilypond-devel
> Betreff: Re: Chord
We currently have issues with the chord naming functions of LilyPond. If we
pass a \chordmode chord to the the ChordNames construct, we very seldom get
out what we put in (i.e. c:maj13 will give Cmaj7/9/add13). This is because
we currently try to do the chord naming algorithmically.
I'd li
I am fine with dropping this code.
On Mon, Aug 11, 2008 at 8:19 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> In responding to Trevor Daniels's review of NR 2.7 Chords, I came across the
> fact that the Banter chord naming code is broken -- it will not produce
> output
In responding to Trevor Daniels's review of NR 2.7 Chords, I came across the
fact that the Banter chord naming code is broken -- it will not produce
output for a simple c chord.
First question: Does anybody know when Banter chord naming quit working?
In searching the internet to see more
10 matches
Mail list logo
