Laura wrote:

>>>>>> "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:.)

An M: field in the header (i.e. before the K:) is mandatory, I think.
However, it's actually not that but the N: in the tune which foxes BarFly.

>And as far as needing a barline where there isn't an end of a measure,
>I'm sure that's a bug in barfly.

Well, not strictly a bug since I designed it that way, but with the
advantage of hindsight I know that I shouldn't have.

>
>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?
>

Perhaps the breve and longa should go in the standard.  Certainly the
breve should, as it's sometimes used even in modern music.  In the
meantime we're stuck with a8-a8, or even a4-a4-a4-a4.

Phil Taylor


To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html

Reply via email to