Hello, Jack Campin wrote: (...) relating to the Tune Finder. The problem is that a typical pair of alternate > titles from that collection is: > T:Appone mulieri super mammas bufonem, ut ablactet eum, et moriatur mulier, sitque >bufo grossus de lacte > (...) This might be worth doing for other instances where people have encoded > entire collections - if the first entry is of the form > X:0 > T:Skye Collection > (...) And if somebody enters "Skye Collection" as a search > string that'll most likely be what they want to happen.
noplisnot! If there is a need of searching the tunefinder for the source or book a tune is taken from it would be reasonable to ask for the S: and the B: fields to be included in the tunefinder. Please do not change the way of writing a abc header to bend it to the needs of an peripheral application. The abc format gives advice where to store such info. It will not make things better to establish some primitive dialectinstead. B:book yes yes archive B:O'Neills S:source yes S:collected in Brittany Maybe it would be a reasonable effort to give some detail information for these fields in the comentary section of the standard. To me B: is the print from which I transcribed and/or a book in which this tune can be found in a similar version (I use "B:from:" to indicate the first and "B:also in:" for the second). S:is the source in the scientific meaning - the manuscript or even the person who carried the tradition. In the Z: field I store info about the transcriber to abc by the way I do not know about te exact use of the "F:" field, can someone show me. Maybe this would be a better place to store the information in question. To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
