Re: [abcusers] [ABCp] Line continuation
Hudson Lacerda wrote: It seems that you coded a line continuation similar to those of bash or C That's what I did. Continuation gets reported (a T_CONTINUE event) and the scanner stays in the same state. [V:1] abcde \ [V:2] ABCDE \ [V:1] cdedc [V:2] CDEDC is equivalent to: [V:1] abcde cdedc [V:2] ABCDE CDEDC but not to: [V:1] abcde [V:2] ABCDE [V:1] etc. That's difficult! Neither the 1.6 nor the 2.0 draft mentioned it! :( Do you mean that continuations should be treated as continuation within a voice? I hope not, it really would be difficult to handle. I hope many others will provide their comments about this issue so to reach a consesus on this topic. I intended to solve the issue treating ABC | def |\ M:1/4 gab |] as if it was: ABC | def | [M:1/4] \ gab |] but your example would prevent me to do so! Another case (rare, though) is when the meter is changed very often. That one works good for me, every single element in your example get recognized properly. R:D To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] [ABCp] Parts
Most of the examples I've examined (thanks again folks!) use a single uppercase letter for denoting each part. P:A in a tune means this is the part 'A' and P:ABACAB at the beginning means, if I understood it correctly, play part A, then B, then C This is what the standards suggest but in one of the Barfly examples, parts are denoted with a more complex syntax: P:Coda for example. I'd like to support it but what should be the exact syntax? My proposal is the following: Each part name MUST begin with a upper case letter and may continue ONLY with lowercase letters and numbers P:AB- play part A then B P:OvertureCoda - play part Overture then part Coda P:OVERTURE CODA - play part O then V, then E, ... P:intro - ERROR Spaces and dots may separate part names. How Barfly behaves? Any other suggestion? R:D To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Line continuation
On 23 Oct 2004, at 09:36, Remo D. wrote: Hudson Lacerda wrote: It seems that you coded a line continuation similar to those of bash or C That's what I did. Continuation gets reported (a T_CONTINUE event) and the scanner stays in the same state. That's correct. We have had long discussions on this subject previously, and the overall conclusion was that the continuation symbol should simply mean continued on the next line. The alternative, where it would mean continued on the next line of the same type was rejected because it leads to too many ambiguous and un-intuitive constructs. [V:1] abcde \ [V:2] ABCDE \ [V:1] cdedc [V:2] CDEDC is equivalent to: [V:1] abcde cdedc [V:2] ABCDE CDEDC but not to: [V:1] abcde [V:2] ABCDE [V:1] etc. That's difficult! Neither the 1.6 nor the 2.0 draft mentioned it! :( Do you mean that continuations should be treated as continuation within a voice? I hope not, it really would be difficult to handle. No, don't go that way! I hope many others will provide their comments about this issue so to reach a consesus on this topic. I intended to solve the issue treating ABC | def |\ M:1/4 gab |] as if it was: ABC | def | [M:1/4] \ gab |] That's fine. It is important to deal with this construct as it was specifically mentioned in earlier standards (before [inline fields] were introduced it was the only way to specify a key or metre change in mid-line), and there are many tunes on the net which incorporate it. Phil Taylor To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
[abcusers] [ABCp] Decoration J
I still have to fix parts and continuations with the latest suggestion but there's something else that I can do very quickly: can anyone tell me what the decoration J is? Tnx. R.D To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Decoration J
Remo D. asks: | I still have to fix parts and continuations with the latest suggestion | but there's something else that I can do very quickly: can anyone tell | me what the decoration J is? In abc2ps, it produces the short diagonal line to the lower left of a note head that means a slide up to the note. It could be useful to have a way to get the other slide symbols. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Line continuation
Remo D. wrote: Hudson Lacerda wrote: It seems that you coded a line continuation similar to those of bash or C That's what I did. Continuation gets reported (a T_CONTINUE event) and the scanner stays in the same state. [V:1] abcde \ [V:2] ABCDE \ [V:1] cdedc [V:2] CDEDC is equivalent to: [V:1] abcde cdedc [V:2] ABCDE CDEDC but not to: [V:1] abcde [V:2] ABCDE [V:1] etc. That's difficult! Neither the 1.6 nor the 2.0 draft mentioned it! :( Do you mean that continuations should be treated as continuation within a voice? I hope not, it really would be difficult to handle. I hope many others will provide their comments about this issue so to reach a consesus on this topic. After send my message, I had a look at the standards and really there are no thing like that my sample! :(( Currently, I know it works as I described, with abcm2ps. I do not want cause any controversies or difficulties concerning the language or it implementations -- especially because ABC already has too many different `flavors' mutually incompatibles. I mentioned that case because I find very useful to control the formatation of the score after write the notes using `\' and `!'. I'd like someone could suggest another way to control the measures to be printed in a same line without need to translate excerpts of code. (That could be simple with 1voice, but is not good for polyphonic music.) Maybe another special character could be used for that purpose (continuation of music system in printed scores). (Suggestion for the new standard?) Best regards. Hudson To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
