On Fri, 13 Oct 2000, James Allwright wrote:
> To me, "\n" would imply a linefeed character to be included directly
> in the PostScript - probably not what you want. The syntax recognized
> by yaps and abc2midi is a semi-colon.
>
> e.g. "G;Em"
That's nice! Only problem (for my logic) is that puts G over Em (makes
sense though thought of as some kind of newline) so if I wanna have these
chords (this is not abc-code, I leave out notes and write only chords
and barlines for this purpose):
Em7 A7
C6 Am7 | Dm7 G7 | C6 Am7 | Dm7 G7 |
I have to write
";C6" ";Am7" | ";Dm7" ";G7" | "Em7;C6" "A7;Am7" | ";Dm7" ";G7" |
so my logic would be to have the chord after ; as the alternative which
should be put on top. This off course gets even worse if you have three
alternatives at some spots. I guess it's too late to change that now? How
about [1] having a %% comment that let's you switch between the two ways
of thinking?
Another problem is that abc2ps gives me chords like Em7;C6 spelled out -
not nice. I can of course stick with one program.
Do you still have to have all formatting inside the .abc-file with yaps or
is it possible to have a [2] seperate format file like with abc2ps??
If [1] and [2] makes it's way into yaps I'll switch to that, and shut
up. If abc2ps implements a similar way of handeling multible chords I'll
stick with that and shut up.
This reminds me of what happened last time I brought this up: People
settled on the idea that some kind of fusion between existing brances of
abc source was needed before implementing anything new. And I heard
something about sourceforge. How is this going??? If we (you??) can figure
out a way of merging the features of the brances into one package this
might IMHO be the best thing that can happen to abc software right now...
--
Atte Andr� Jensen
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
