David Stone a écrit : > Here are my proposed descriptions of header fields, written such that > (if judged acceptable) they can be pasted into the gregorio web pages. > I have followed the existing web pages and examples as far as > possible. > > The purpose of suggesting these clarifications and changes is (i) to > make the header fields more useful for those searching for chants in > web sites such as the Caecilia one mentioned; and (ii) to make it > possible by enhancements to gregorio to make the header fields > available for titling in the backend. >
Hello, first thank you for this mail! > It would be ridiculous to set myself up as an expert in chant > classification; I hope others will correct anything silly I have > suggested. > > I have marked the type of change to each (compared to gregorio 0.9.2): > [-] remove this field; [+] new field ; [=] no real change, just > clarification; [!=] changed meaning of field. > > number-of-voices [=] > > The number-of-voices is the number of voices for a polyphonic piece. > Successive voices are separated by a line containing "--" in the gabc > notation. > > name [=] > > This is the name of the piece, in almost all cases the incipit, the > first few words. In the case of the mass ordinary, the form as `Kyrie > X Alme Pater' or `Sanctus XI' is recommended where appropriate. > Ok > license [=] > > Thw license is the copyright license of the gabc, as chosen by the person > named in the translator field. It is only a brief description, such > as `public domain', `CC-by-sa'; a separate text file will be necessary > for the complete legal license. > Ok. > initial-key [-] > > [This is no longer needed, since the clef is in the notation proper.] > Ok, it's true that it's confusing. > office-part [=] > > The office-part is the category of chant, according to its liturgical > rôle. Examples are: antiphona, hymnus, responsorium brevium, > responsorium prolixum, introitus, graduale, tractus, offertorium, > communio, kyrie, gloria, credo, sanctus, benedictus, agnus dei. > > occasion [+] > > The occasion is the liturgical occasion. For example, `Dominica II > Adventus', `Commune doctorum', `Feria secunda'. > Ok. > initial-style [-] > > [This does not appear useful to me.] > It's not, it should be handled in TeX, not in gabc. > mode [!=] > > The mode of the piece. This should normally be a number 1-8, but may > be any text required for unusual cases. > I think we should separate the mode number from the annotation linked to the mode... For example in the case of a score without an annotation, we should be able to know the mode. So I think it would be better to have the mode in the gabc header, even if it would not be printed, and the annotation, that would be printed. > anotation [!=] > > [Spelling to be corrected to `annotation'.] > > The annotation is the text to appear above the initial letter. > Usually this is an abbreviation of the office-part in the upper line, > and an indication of the mode (and differentia for antiphons) in the > lower. Either one or two annotation fields may be used; if two are > used, the first is the upper line, the second the lower. Example: > > annotation:Ad Magnif.; > annotation:VIII G; > Ok. > commentary [+] > > This is intended for notes about the source of the text, such as > references to the Bible. > Ok. > author [=] > > The author of the piece, if known; of course, the author of most > traditional chant is not known. It may be used for the name of a > modern arranger, when a traditional chant melody has been adapted for > new words. > > date [!=] > > The date of composition, or the date of earliest attestation. With > most traditional chant, this will only be approximate; e.g. `XI c.' > for eleventh century. > > manuscript [=] > > For transcriptions direct from a manuscript, the text normally used to > identify the manuscript, for example `Montpellier H.159'. For > transcriptions from a modern book, the name of the book; e.g. `Liber > Usualis'. > Ok. I would also add something like "book", to indicate in which (modern) book the score appears, like an old Solesmes book or something... I would also add an arranger field, which would be for example "Solesmes"... > reference [=] > > A unique reference for the piece, according to some well-known system. > For example, the reference beginning `cao' in the Cantus database of > office chants. If the reference is unclear as to which system it > uses, it should be prefixed by the name of the system. > > [...] > > > The following do not seem to be really metadata, and I do not know how > they should be used: > > software used > software-used > It would be the software used to generate gabc. If you generate gabc by hand, this field should not appear. I would also add a field "gabc-version" containing the version of the gabc notation used in the score, after all we never know, it may evolve in the future. With this field we would add backward compatibility. > lilypond-preamble > opustex-preamble > musixtex-preamble > These ones are never used, the could be removed or, at least, be undocummented. > gregoriotex-font > This one is the font used by gregorio (gregorio can use three fonts). What do you think about my suggestions? Thanks! -- Elie _______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
