On Fri 23 Nov 2001 at 11:24PM +0000, Jack Campin wrote: > > > The extra 'per file definition fields' seems like quite a major > > extension to ABC to me, I don't think we have anything quite like > > that at the moment, and I'm not convinced about the need to add it > > for this. > > They're in the 1.6 standard for other header fields: > > : Most of > : the information fields are for use within a tune header but in > : addition some may be used in the tune body, or elsewhere in the > : tune file. Those which are allowed elsewhere can be used to set > : up a default for the whole or part of a file. For example, in > : exactly the same way that tunebooks are organised, a file might > : start with M:6/8 and R:Jigs, followed by some jigs, followed by > : M:4/4 and R:Reels, followed by some reels. Tunes within each > : section then inherit the M: and R: fields automatically, although > : they can be overridden inside a tune header. > > My proposal was modelled on that.
This is not a widely implemented feature of the abc standard and I would personally like it to become deprecated. My reasoning is that if you have global fields, you can't treat a single abc tune as something that can be edited out of its source file (which you might do if you wanted to print off just one tune from a collection). James Allwright To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
