On Wed, 30 Jul 2003, Arent Storm wrote:
> * irregular compound meter: two ways of display
> 1) 3+2+2/8 displayed as is
> 2) (3+2+2)/8 displayed as 7/8
I think both should be displayed as:
3 + 2 + 2
8
If you want the semantics of 2), simply type:
M:7/8 % (3+2+2)/8
> *G: group; clarify (I still don't get its definition) or explicit allow any
> useage...
> *H:is (the only?) field that can contimue on the next line without
> repeat of the H: ?
I also don't know the details of these fields.
Can anyone comment?
> *w: to appendix
Good idea.
> * explicitly note which fields may be used in-tune.
There is a table which documents that.
> * ~ I always thought that ~ is used for a prall-trill by default.
> Hardly anybody will know what an Irish-roll is (is it eatable?)
I also do not know what a Irish roll is. But apparently, they are
the people that invented the ~ symbol.
> But as this will reraise previous discussions make a statement
> like 'programs should treat chord symbols quite liberately'
Good idea.
> * clefs:
> Is "K: Am transpose=-2 " illegal where
> "K: Am treble transpose=-2 " is not?
Both are legal. will try to make it clearer.
> state that all voices to be mentioned in the abc-body have to be declared in
> the header when using the [V:ID] syntax, where each ID will be referenced over
> and over.
Do others think this would be necessary?
> Reserve some unicode encoding scheme for future enhancements
> (forward compatibility) So characters like copyright signs, trademark
> or whatever may be used in the (near) future:
There is support for utf-8 encoding of strings
> *reserved characters
> Try to make clear where/why which characters is reserved.
> Even better: reserve characters in a specialized context.
> - global
> - within body
> - within header
> - within textstrings
> - within w: and/or W: lines
> reserved syntax would be a nice thing to have.
> Knowing which generic syntax might be used in the future will render software
> useable for a longer time.
If I'll have some time, I'll look into this suggestion.
> The draft suggests that %%staves is likely to be moved to a stylesheet.
What would be wrong with a piano tunebook starting
with the definition:
%%staves {LH RH}
V:LH bass m=d
....
tunes
....
Makes perfect sense to me.
> *special characters:
> why use = for a macron and/or stroke through
> - or _ is more logical
\- has already got a special meaning in lyrics lines!
> The oe ligature is missing (fine to me as there
> is a readable workaround for it).
I asked a couple of Frenchmen and they said they
could live without it.
> z-circumflex is not available in latin-extended-A
> (especially not as it typesetted here ;-)
Correct. It should be removed.
Groeten,
Irwin Oppenheim
[EMAIL PROTECTED]
~~~*
Chazzanut Online:
http://www.joods.nl/~chazzanut/
To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
