----- Original Message ----- From: "Phil Taylor" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 22, 2003 6:21 PM Subject: Re: [abcusers] multivoice & linecontinuation
> Arent Storm wrote: > > >Where it comes to to line continuation in multivoice and/or > >in-line lyrics things can get (unneccessarily) complicated. > >IMO line continuation should be allowed only for single voice. > >For instance, the nicely text-layed-out multivoice canzonetta.abc > >from the 2.0 standard would become unreadable with > >line continuation used. > > Yes, I'm inclined to agree. The only exception should be > where there is some limitation on line length (e.g. the tune > is going to be emailed), then continuation should only be > used to continue on the following line. I'd much prefer the ! for those (rare?) cases that you'd want to override the algoritmical linebreaks, and forget about linecontinuation at all, but I'm afraid that I'll be standing on many toes... > >Also, when using abc to store complex scores, I think that > >human readablity is of very small importance, if at all; it > >will be uncomprehensable anyway. > > Not all multivoice scores are impossible to read. Jack Campin > has some beautifully-constructed abcs of tunes in two or three > voices. Not impossible, but in general there will be very little need for it, I guess that sight-readers of ABC will haveno need for it, so it'll be more otr less pointless to try. > >The 3 different approaches of writing down multivoice I dislike. > >I would very much prefer one approach the: voice by voice Sight readers will be thus allowed to read their part as easy as they're used to. > >V1: > >abc|abc|abc|abc > >def|def|def:| > >V2: > >Abc|Abc|Abc|Abc > >Def|Def|Def:| > > > >over > > > >[V1]:abc|abc|abc|abc| > >[V2]:Abc|Abc|Abc|Abc| > >[V1]:def|def|def:| > >[V2]:Def|Def|Def:| Would there be abc-sight-reading conductors? > >and (least) > > > >V1: > >abc|abc|abc|abc| > >V2: > >Abc|Abc|Abc|Abc| > >V1: > >def|def|def:| > >V2: > >Def|Def|Def:| compatible but useless IMO > I'd prefer them in the order 2,3,1. > > >The first is what MusiCAD is exporting, while importing all three. > >As said before - in multivoice scores - human readability > >won't have to be/should not be/cannot be a major issue. > > BarFly won't be able to display the output from MusiCAD, then. Why > not give your users the option of all three? If MusiCAD prints > music it must know where the line ends should come, so options > 2 and 3 should be possible. Its not impossible, only requires a major rewrite of the abc-writing module I'll be (trying) to comply to the upcoming standard though, but as long as option 1 actually is in the standard I'm complying already... Arent To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
