2009/1/16, [email protected] <[email protected]>: > Send Gregorio-devel mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.gna.org/listinfo/gregorio-devel > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gregorio-devel digest..." > > > Today's Topics: > > 1. Re: proposed clarifications for gabc header fields (David Stone) > 2. Re: proposed clarifications for gabc header fields (Elie Roux) > 3. [task #6431] Dominican bars (Elie Roux) > 4. [bug #12863] wrong calculation of the vertical spaces for new > lines (Elie Roux) > 5. [task #6432] Variables in gabc (Elie Roux) > 6. [task #6433] Clarify and tidy the fields in the gabc header > (David Stone) > 7. Re: proposed clarifications for gabc header fields (Tracy Llenos) > 8. [bug #12865] improper height of score annotation when > vernacular added (Tracy Llenos) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 15 Jan 2009 16:06:22 +0000 > From: David Stone <[email protected]> > Subject: Re: [Gregorio-devel] proposed clarifications for gabc header > fields > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > > Here is an updated version of my previous suggestion. I have taken up > Elie's comments, and added `meter' for the Caecilia project. > > 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. > > 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 > 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'. > > 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'. > > 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. > > storage-place [=] > > For transcriptions direct from a manuscript, where the manuscript is > held; e.g. Biblioth?que 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). > > > -- > David Stone > > > > ------------------------------ > > Message: 2 > Date: Thu, 15 Jan 2009 17:26:39 +0100 > From: Elie Roux <[email protected]> > Subject: Re: [Gregorio-devel] proposed clarifications for gabc header > fields > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > David Stone a ?crit : >> Here is an updated version of my previous suggestion. I have taken up >> Elie's comments, and added `meter' for the Caecilia project. >> > > The only change that I think could make it more clear is that, now that > we have book and manuscript, we should make reference and storage-place > more explicitely refering to the manuscript, by replacing the with, for > example, manuscript-storage-place and manuscript-reference, all the rest > seems OK to me! > > Thank you for your work! > -- > Elie > > > > ------------------------------ > > Message: 3 > Date: Thu, 15 Jan 2009 21:36:10 +0100 > From: Elie Roux <[email protected]> > Subject: [Gregorio-devel] [task #6431] Dominican bars > To: Elie Roux <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain;charset=UTF-8 > > > URL: > <http://gna.org/task/?6431> > > Summary: Dominican bars > Project: Gregorio > Submitted by: eroux > Submitted on: jeudi 15.01.2009 ? 20:36 > Should Start On: jeudi 15.01.2009 ? 00:00 > Should be Finished on: jeudi 15.01.2009 ? 00:00 > Category: GregorioTeX global > Priority: 1 - Later > Status: Postponed > Privacy: Public > Percent Complete: 0% > Assigned to: None > Open/Closed: Open > Discussion Lock: Any > Effort: 0.00 > > _______________________________________________________ > > Details: > > Some dominican chant books have some special types of bars, it should be > possible to typeset them with gregorio. An example is joined. > > > > _______________________________________________________ > > File Attachments: > > > ------------------------------------------------------- > Date: jeudi 15.01.2009 ? 20:36 Name: virgulaeminor.jpg Size: 13 ko By: > eroux > > <http://gna.org/task/download.php?file_id=5184> > > _______________________________________________________ > > Reply to this item at: > > <http://gna.org/task/?6431> > > _______________________________________________ > Message post? via/par Gna! > http://gna.org/ > > > > > ------------------------------ > > Message: 4 > Date: Thu, 15 Jan 2009 21:39:35 +0100 > From: Elie Roux <[email protected]> > Subject: [Gregorio-devel] [bug #12863] wrong calculation of the > vertical spaces for new lines > To: Elie Roux <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain;charset=UTF-8 > > > URL: > <http://gna.org/bugs/?12863> > > Summary: wrong calculation of the vertical spaces for new > lines > Project: Gregorio > Submitted by: eroux > Submitted on: jeudi 15.01.2009 ? 20:39 > Category: None > Severity: 2 - Minor > Priority: 3 - Low > Status: None > Privacy: Public > Assigned to: eroux > Originator Email: > Open/Closed: Open > Discussion Lock: Any > Release: latest svn > Operating System: All > > _______________________________________________________ > > Details: > > Vertical spaces should be calculated in a better way: > > * bottom notes shouldn't be considered when they are 6 notes after the > first > note of a syllable, because we can consider that they're not above the text > anymore. > * vertical episemus under a bottom note should be considered. > > > > > _______________________________________________________ > > Reply to this item at: > > <http://gna.org/bugs/?12863> > > _______________________________________________ > Message post? via/par Gna! > http://gna.org/ > > > > > ------------------------------ > > Message: 5 > Date: Thu, 15 Jan 2009 21:54:58 +0100 > From: Elie Roux <[email protected]> > Subject: [Gregorio-devel] [task #6432] Variables in gabc > To: Elie Roux <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain;charset=UTF-8 > > > URL: > <http://gna.org/task/?6432> > > Summary: Variables in gabc > Project: Gregorio > Submitted by: eroux > Submitted on: jeudi 15.01.2009 ? 20:54 > Should Start On: jeudi 15.01.2009 ? 00:00 > Should be Finished on: jeudi 15.01.2009 ? 00:00 > Category: gabc syntax > Priority: 1 - Later > Status: Postponed > Privacy: Public > Percent Complete: 0% > Assigned to: None > Open/Closed: Open > Discussion Lock: Any > Effort: 0.00 > > _______________________________________________________ > > Details: > > Here is a mail received on the list: > > Also, I have one suggestion of a possible feature that could be very useful > if it were possible to accomplish. If at the beginning of a chant > transcription one could create a set of variables, such as > > V1 = chant string > V2 = different chant string > V3 = etc. > > This would allow one to simplify the transcription of repetitive pieces, > such > as hymns, which have the same music repeated with arious texts. This way, > one > could type several verses of the hymn with references to the variables > rather > than retyping them each time. For instance, > > ?(V1)ter(V2)na(V3) Chri(V4)sti(V5) m?(V6)ne(V7)ra,(V8) > Apostolorum gl?riam, > Laudes ferentes debitas, > L?tis can?mus mentibus. > 2. Ec(V1)cle(V2)si(V3)?(V4)rum(V5) pr?n(V6)ci(V7)pes,(V8) > Belli triumphales duces, > C?lestis aul? m?lites, > Et vera mundi l?mina. > > If this could be implemented, it would allow one to quickly set one text to > various melodies (which I need to do for my Antiphonarium project) without > retyping the melody each time. > > > > > _______________________________________________________ > > Reply to this item at: > > <http://gna.org/task/?6432> > > _______________________________________________ > Message post? via/par Gna! > http://gna.org/ > > > > > ------------------------------ > > Message: 6 > Date: Thu, 15 Jan 2009 21:56:55 +0100 > From: David Stone <[email protected]> > Subject: [Gregorio-devel] [task #6433] Clarify and tidy the fields in > the gabc header > To: David Stone <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain;charset=UTF-8 > > > 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/ > > > > > ------------------------------ > > Message: 7 > Date: Thu, 15 Jan 2009 18:45:51 -0600 > From: Tracy Llenos <[email protected]> > Subject: Re: [Gregorio-devel] proposed clarifications for gabc header > fields > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > On Jan 15, 2009, at 10:06 AM, David Stone wrote: >> Here is an updated version of my previous suggestion. I have taken up >> Elie's comments, and added `meter' for the Caecilia project. >> >> 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. >> >> translator [=] >> >> The name of the transcriber into gabc. >> >> translation-date [=] >> >> The date the gabc was written. > > Sorry for entering this discussion so late; I think everything as > you've written (with Elie's following clarifications) is good, except > for these fields. Can we consider possibly renaming them? If I (well, > a random user) were reading the header of a gabc file, and saw these > two fields, I'd think they referred to a -vernacular- translation -- > which, of course, might not even be in the given gabc file. Maybe > transcriber/transcription-date, or even gabc-translator/date, to make > it clear it refers to the translation to gabc notation, and not a > translation of the chant text into another language? > > -- > Tracy > > > > > ------------------------------ > > Message: 8 > Date: Fri, 16 Jan 2009 02:17:02 +0100 > From: Tracy Llenos <[email protected]> > Subject: [Gregorio-devel] [bug #12865] improper height of score > annotation when vernacular added > To: Tracy Llenos <[email protected]>, [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain;charset=UTF-8 > > > URL: > <http://gna.org/bugs/?12865> > > Summary: improper height of score annotation when > vernacular > added > Project: Gregorio > Submitted by: tllenos > Submitted on: Friday 01/16/2009 at 01:17 > Category: GregorioTeX global > Severity: 2 - Minor > Priority: 3 - Low > Status: None > Privacy: Public > Assigned to: None > Originator Email: > Open/Closed: Open > Discussion Lock: Any > Release: latest svn > Operating System: All > > _______________________________________________________ > > Details: > > >From someone on the users' mailing list: > > If you add a vernacular translation in the gabc file, then try to also add > some sort of annotation above the score's initial, the height is calculated > wrongly. This leads to an unsightly collision between the initial and the > annotation. > > This can be seen with the following gabc snippet: > > name: Gloria Patri; > %% > GL{?}[Glory be](c4g)ri(hg)a(gj) P?(j)tri,(j) et(j) F?(j)li(j)o,(j) (,) > > and adding something (e.g. the mode) above the initial in the tex wrapper > file: > > \setfirstlineaboveinitial{\small \textsc{\textbf{VII}}}{\small > \textsc{\textbf{VII}}} > > > > _______________________________________________________ > > File Attachments: > > > ------------------------------------------------------- > Date: Friday 01/16/2009 at 01:17 Name: gloriapatri.png Size: 25kB By: > tllenos > > <http://gna.org/bugs/download.php?file_id=5189> > > _______________________________________________________ > > Reply to this item at: > > <http://gna.org/bugs/?12865> > > _______________________________________________ > Message sent via/by Gna! > http://gna.org/ > > > > > ------------------------------ > > _______________________________________________ > Gregorio-devel mailing list > [email protected] > https://mail.gna.org/listinfo/gregorio-devel > > > End of Gregorio-devel Digest, Vol 12, Issue 13 > ********************************************** >
_______________________________________________ Gregorio-devel mailing list [email protected] https://mail.gna.org/listinfo/gregorio-devel
