>>>>> "Phil" == Phil Taylor <[EMAIL PROTECTED]> writes:
Phil> (You'll have to move the K: field to the end of the header
Phil> where it belongs, and also put a bar line at the end of each
Phil> line, otherwise BarFly will display it all on one line.)
>>
>> I don't think there are fields after the K: field that aren't
>> allowable in the body of the tune. (OK, the standard doesn't say that
>> about N, but I think it should about some note field, and I think it
>> does about T:, M:, and L:.)
Phil> An M: field in the header (i.e. before the K:) is mandatory,
Phil> I think.
I don't see that in my copy of the standard. abc2ps defaults to 4/4,
I think, if there isn't an M: field at all. Is that wrong?
Phil> However, it's actually not that but the N: in the tune which
Phil> foxes BarFly.
Yes, that's a change I'd like to see in the standard. Either N: or
some other text field should be allowed in the body, so that notes
that actually apply to a particular note or lyric can be entered _in
situ_. abc2ps does the right thing already. abc2midi complains, but
wouldn't do anything about the N: field wherever it was.
>>
>> I agree about the multiple ways of displaying a17, but what about a16?
>> If I want to transport ABC from a program that knows what a longa
>> looks like to one that doesn't, how should I do that?
>>
Phil> Perhaps the breve and longa should go in the standard. Certainly the
Phil> breve should, as it's sometimes used even in modern music. In the
Phil> meantime we're stuck with a8-a8, or even a4-a4-a4-a4.
So you think a program that does handle longas should be able to parse
a4-a4-a4-a4 as a16?
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
