URL:
<http://gna.org/task/?6433>
Summary: Clarify and tidy the fields in the gabc header
Project: Gregorio
Submitted by: dfstone
Submitted on: Thursday 01/15/2009 at 20:56
Should Start On: Thursday 01/15/2009 at 00:00
Should be Finished on: Sunday 02/15/2009 at 00:00
Category: gabc syntax
Priority: 3 - Low
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: dfstone
Open/Closed: Open
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
Details:
This follows recent discussion on the gregorio-devel list.
It includes changes to the web documentation and also changes to what the
gregorio program accepts, as below.
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.
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.
initial-key [-]
[This is no longer needed, since the clef is in the notation proper.]
office-part [=]
The office-part is the category of chant, according to its liturgical role.
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'.
initial-style [-]
[This does not appear useful to me.]
mode [!=]
The mode of the piece. This should normally be a number 1-8, but may be any
text required for unusual cases. Note that this is not used for the text
above the initial, for which see the annotation field.
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;
meter [+]
For hymns and anything else with repetitive stanzas, the meter, the numbers
of syllables in each line of a stanza. For example, 8.8.8.8 for typical
Ambrosian-style hymns: 4 lines each of 8 syllables.
commentary [+]
This is intended for notes about the source of the text, such as
references to the Bible.
author [=]
The author of the piece, if known; of course, the author of most
traditional chant is not known.
arranger [+]
The name of a modern arranger, when a traditional chant melody has been
adapted for new words. This may be a corporate name, like `Solesmes'.
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'.
book [+]
For transcriptions from a modern book (such as Solesmes editions;
`modern' goes back at least to the 19th century revival), the name of the
book; e.g. `Liber Usualis'.
manuscript-reference [replaces 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. Note that this should be a reference
identifying the _piece_, not the manuscript as a whole; anything identifying
the manuscript as a whole should be put in the `manuscript' field.
manuscript-storage-place [replaces storage-place]
For transcriptions direct from a manuscript, where the manuscript is held;
e.g. Bibliotheque Nationale, Paris.
translator [=]
The name of the transcriber into gabc.
translation-date [=]
The date the gabc was written.
style [=]
The typographical style of the music. This is not yet supported, in that it
has no effect. Example: `editio vaticana', `editio medicea'.
virgula-position [=]
The position to be used for the virgula. This is not yet supported, in that
it has no effect. Example: `top', `bottom'.
software used [-]
[duplicate of software-used]
software-used [=]
The name of the software used to generate the gabc file. If you generate gabc
by hand, this field should not appear.
gabc-version [+]
The version of gabc notation used. At present the version should
always be 1.
lilypond-preamble [-]
opustex-preamble [-]
musixtex-preamble [-]
[These are not used and will be left undocumented or removed.]
gregoriotex-font [=]
The font used by gregoriotex (at present gregoriotex can use three fonts:
greciliae, gregorio, and parmesan).
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?6433>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Gregorio-devel mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-devel
