[abcusers] [ABCp] Alpha version uploaded
I've made some changes and some testing. Everything is far from being stable or even usable but for those that are interested I've uploaded the source on sourceforge.net: http://sourceforge.net/projects/abcp. I've included in the zip file the executable for re2c (as long as the source files) to allow an easy recompilation. I've only tested the compilation on Windows with mingw+msys (gcc) and lcc, simply call "config lcc" or "config mingw" before doing make to select the proper compilation option, on Win I plan to test the usual compilers (VC, BCC, Watcom and Digital Mars). In the zip file ("bin" directory) you will also find "abcp.exe" that simply shows the events that would have been called together with a packed version of the parsed fields. If you just want to see how the pieces of an ABC get recognized simply call "abcp file.abc". Any comment appreciated! R.D To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Parts
Neil Jennings wrote: Because the P: text appears above the staff, people have mis-used it to add comments which have nothing to do with parts. In the tune header, it can have a formula such as (AB)2(AC)3 In the body, it must be just a single letter HARMONY can play tunes according to the formula, including nested repeats. Neil Does this mean that my proposal is ok for you? If you have (like the standard says): % Header P:(AB)2C ... % Body P:A P:B It would work. But also it would work if you write: %Header P:(Intro Riff)2 Coda ... % Body P:Intro P:Riff ... As a general rule, my parser tries to accomodate as many synonyms as it can. A simple example is with decorations: !f! is equal to +f+ which is equal to +forte+. R.D To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Decoration J
I don't think it is defined in the official specification. - Original Message - From: "Remo D." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 23 October 2004 21:26 Subject: [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 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
Re: [abcusers] [ABCp] Parts
Because the P: text appears above the staff, people have mis-used it to add comments which have nothing to do with parts. In the tune header, it can have a formula such as (AB)2(AC)3 In the body, it must be just a single letter HARMONY can play tunes according to the formula, including nested repeats. Neil - Original Message - From: "Remo D." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: 23 October 2004 11:22 Subject: [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 To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html