[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: guitar chord diagrams
From: |
Carl D. Sorensen |
Subject: |
RE: guitar chord diagrams |
Date: |
Wed, 11 Feb 2004 08:49:42 -0700 |
Jose Luis,
I appreciate the input on features you'd like. As Han-Wen mentioned, it's
premature right now to speak about input syntax. I'll see if I can get
something out to the list as a markup that can be used right now, without even
creating a ChordDiagram context or a Chord_Diagram engraver. Then, once the
markup is working, we'll wrestle with the engraver, the context, and the input
syntax.
Carl Sorensen
-----Original Message-----
From: José Luis Cruz [mailto:address@hidden
Sent: Wednesday, February 11, 2004 7:32 AM
To: Carl D. Sorensen
Cc: address@hidden; address@hidden
Subject: Re: guitar chord diagrams
hi,
IMHO it will be fine if chord diagrams could (also?) be built just by telling
which fret/s is/are pressed on which string. Something like:
\chorddiagram #(5 . x . 6 . 6 . 5 . x) % Amaj7
\chorddiagram #(x . 4 . 7 . 4 . 5 . x) % C#-7(b6)
I would love that if there are no limitations of only using one fret per
string, so then would become possible to type scales patterns or arpeggios, or
something like that. That wouldn't be difficult; the only problem i see -and
isn't so big- is to decide an unified syntax for all the possibilities.
Both previous examples i put, i would like to add things to them like text
behind each string, or use a parenthesized circle on a particular fret (for
saying it's optional), and so on...
\chorddiagram #(x . 4_'C#' . 7_'b6' . 4_'\flat7' . 5_'\flat3' .
(4)_'5')
just ideas.. i don't know any about scheme, really...
very thanks Carl, for working on this.
José Luis