You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gabc/details.html
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ <h3 id="liquescences">Liquescentiae and <em>initio debilis</em> figures</h3>
93
93
<br/><em>Torculus</em> and <em>torculus initio debilis</em> : <code>fgf -fgf</code>
94
94
</div>
95
95
96
-
<p>For liquescentiae, three types exist, which are indicated by characters at the end of the neumes:</p>
96
+
<p>For liquescentiae, three types exist, which are indicated by a character at the end of the neume:</p>
97
97
<ul>
98
98
<li>diminutive liquescentiae, indicated by <code>~</code></li>
99
99
<li>increasing liquescentiae
@@ -108,17 +108,17 @@ <h3 id="liquescences">Liquescentiae and <em>initio debilis</em> figures</h3>
108
108
109
109
<h3id="signs">Rhythmic signs</h3>
110
110
111
-
<p>The <em>punctum mora</em> (dots after the note) are denoted by adding a period (<strong><code> . </code></strong>) after the note. When there are two dots after a neume, the character is simply doubled: (<strong><code> .. </code></strong>).</p>
111
+
<p>The <em>punctum mora</em> (dots after the note) are denoted by adding a period (<strong><code> . </code></strong>) after the note. When there are two dots after a neume, the character is simply doubled: (<strong><code> .. </code></strong>).</p>
112
112
113
113
<p>The vertical <em>episema</em> does not pose a problem; it is denoted by an apostrophe(<strong><code> ' </code></strong>) after the note. </p>
114
114
115
115
<p>Of course, the <em>punctum mora</em> and vertical <em>episema</em> can be present more than once in a neume, but only once per note.</p>
116
116
117
117
<p>For the horizontal episema, type an underscore (<strong><code> _ </code></strong>) after every note that is under an episema.</p>
118
118
119
-
<p>Rhythmic signs are notated after liquescentiae and other signs that determine the shape of the note. For example, a virga followed by a punctum mora is denoted <code>hv.</code> and not <code>h.v</code>, and a <em>torculus deminutus</em> followed by a <em>punctum mora</em> is denoted <strong><code> ghg~. </code></strong>.</p>
119
+
<p>Rhythmic signs are notated after liquescentiae and other signs that determine the shape of the note. For example, a virga followed by a punctum mora is denoted <code>hv.</code> and not <code>h.v</code>, and a <em>torculus deminutus</em> followed by a <em>punctum mora</em> is denoted <strong><code> ghg~. </code></strong>.</p>
120
120
121
-
<p>In some scores, there are sometimes two levels of horizontal episema: a short episema beneath a longer one. To put an horizontal episemus under a note, type <strong><code> _0 </code></strong>. This can be combined with a normal horizontal episemus.</p>
121
+
<p>In some scores, there are sometimes two levels of horizontal episema: a short episema beneath a longer one. To put an horizontal episema under a note, type <strong><code> _0 </code></strong>. This can be combined with a normal horizontal episemus.</p>
@@ -245,7 +245,7 @@ <h3 id="translation">Translation and text above notes</h3>
245
245
246
246
<p>To add a translation (or a second line of text), simply put it between square brackets in the syllable text. The text will be left-aligned with the text of the syllable, and won't go to the next line automatically. Thus it may require a bit of work to get the desired effect.</p>
247
247
248
-
<p>It is also possible to add text above notes in two ways: the first is to set the text at the syllable text level between <code><alt></code>markups (alt like <em>above lines text</em>). This text will be left-aligned with the first note of the syllable. It is also possible to typeset text entering <code>[alt:my text]</code> in the notes, which will align "my text" with the note following.</p>
248
+
<p>It is also possible to add text above notes in two ways: the first is to set the text at the syllable text level between <code><alt></code>markup tags (<code>alt</code> is short for <em>above lines text</em>). This text will be left-aligned with the first note of the syllable. It is also possible to typeset text entering <code>[alt:my text]</code> in the notes, which will align "my text" with the next note.</p>
<p>It is possible to insert verbatim code in gabc, this code will appear as it is in the <spanclass="tex">T<spanclass="epsilon">e</span>X</span> file. You can do this at several levels. First you can insert text between the <code><v></code> markups in the syllable text.</p>
268
+
<p>It is possible to insert verbatim code in gabc, this code will appear as it is in the <spanclass="tex">T<spanclass="epsilon">e</span>X</span> file. You can do this at several levels. First, you can insert text between the <code><v></code> markups in the syllable text.</p>
269
269
270
270
<p>Verbatim code can also be inserted at three levels in the notes:</p>
271
271
272
272
<ul>
273
-
<li>at note level, not modifying the glyph determination, with <code>[nv:\mycode]</code> after the note, remplacing<code>\mycode</code> with the code you want to insert</li>
273
+
<li>at note level, not modifying the glyph determination, with <code>[nv:\mycode]</code> after the note, replacing<code>\mycode</code> with the code you want to insert</li>
274
274
<li>at glyph level, forcing the glyph to stop but staying in the same element, with <code>[gv:\mycode]</code></li>
275
275
<li>at element level, forcing the element to stop and not automatically adding a neumatic space (which you may have to add by hand), with <code>[ev:\mycode]</code></li>
<p>The initial is automatically recognized by gregorio as the first letter. You can use the gabc attribute <code>initial-style</code> in the header to set its size. The values corespond to number of lines the intial takes up: <code>0</code> (there is not initial), <code>1</code> (the default), or <code>2</code> (the initial takes up two lines).</p>
354
+
<p>The initial is automatically recognized by gregorio as the first letter. You can use the gabc attribute <code>initial-style</code> in the header to set its size. The values corespond to number of lines the intial takes up: <code>0</code> (there is no initial), <code>1</code> (the default), or <code>2</code> (the initial takes up two lines).</p>
356
355
357
356
<p>Note that in the case of a syllable composed of one letter only, Gregorio<spanclass="tex">T<spanclass="epsilon">e</span>X</span> automatically adds a hyphen under the first notes. To disable this feature, use the command <code>\gresetemptyfirstsyllablehyphen{auto}</code>.</p>
358
357
359
358
<h3id="specialcharacters">Special characters</h3>
360
359
361
-
<p>It can happen that the texts of Gregorian chants contain unicode characters which are not easily accesible from the keyboard. Examples of this sort of characters used in Gregorian notation are <code>ý</code>, <code>ǽ</code>, <code>œ́</code>, the crossed R (℟ for <em>Response</em>), and the crossed V (℣ for <em>Versicle</em>). There is also the possibility of a non-unicode character such as the crossed A (for <em>Antiphon</em>).</p>
360
+
<p>It can happen that the texts of Gregorian chants contain unicode characters which are not easily accesible from the keyboard. Examples of this sort of character are <code>ý</code>, <code>ǽ</code>, <code>œ́</code>, the barred R (℟ for <em>Response</em>), and the barred V (℣ for <em>Versicle</em>). There is also the possibility of a non-unicode character such as the barred A (for <em>Antiphon</em>).</p>
362
361
363
-
<p>Gregorio will allow the use of any unicode character directly entered via your platform's character picker or a keyboard shortcut. In the case where it is not possible to insert special characters in one of these fashions, you can be use <code><sp></code> markup tags, for example <code><sp>R/</sp></code> for the crossed R, <code><sp>'ae</sp></code> for <em>ǽ</em>. This also works for the crossed A, even though it is not in the unicode table: <code><sp>A/</sp></code></p> Finally, you can make use of the <code><v></code> markup tags to enter a character using it's <spanclass="tex">T<spanclass="epsilon">e</span>X</span> code: <code><v>{\ae}</v></code> for <em>æ</em>.
362
+
<p>Gregorio will allow the use of any unicode character directly entered via your platform's character picker or a keyboard shortcut. In the case where it is not possible to insert special characters in either of these ways, you can be use <code><sp></code> markup tags, for example <code><sp>R/</sp></code> for the barred R, <code><sp>'ae</sp></code> for <em>ǽ</em>. This also works for the barred A, even though it is not in the unicode table: <code><sp>A/</sp></code></p> Finally, you can make use of the <code><v></code> markup tags to enter a character using it's <spanclass="tex">T<spanclass="epsilon">e</span>X</span> code: <code><v>{\ae}</v></code> for <em>æ</em>.
364
363
365
364
<h3id="textstyle">Text style</h3>
366
365
367
-
<p>Even though text is rarely styled in a chant score, we have made some markups to apply styles to the text: they are <code><i></code> for italic, <code><b></code> for bold, <code><u></code> for underline (does not work in Plain <spanclass="tex">T<spanclass="epsilon">e</span>X</span>), <code><c></code> for colored (specifically in <code>gregoriocolor</code>), and <code><sc></code> for small capitals.</p>
366
+
<p>Even though text is rarely styled in a chant score, gabc allows for some markup to apply styles to the text: they are <code><i></code> for italic, <code><b></code> for bold, <code><u></code> for underline (does not work in Plain <spanclass="tex">T<spanclass="epsilon">e</span>X</span>), <code><c></code> for colored (specifically in <code>gregoriocolor</code>), and <code><sc></code> for small capitals.</p>
Copy file name to clipboardExpand all lines: gregorio-history.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ <h1>History of the Gregorio project</h1>
55
55
56
56
<p>The Gregorio project was born in 2006 at <ahref="http://www.telecom-bretagne.eu" title="TELECOM Bretagne">TELECOM Bretagne</a>, a graduate engineering school in France. It was at first a student project of six months duration, supervised by <ahref="http://www.telecom-bretagne.eu/studies/msc/professors/haralambous/" >Mr Yannis Haralambous</a>, developer of <ahref="http://en.wikipedia.org/wiki/Omega_(TeX)" title="Wikipedia article about Omega">Omega</a>. When the project was done, Élie Roux decided to continue the project on his own and to develop it under GPL.</p>
57
57
58
-
<p>From the outset the goal of the project has been to create a graphical interface for the monks of the <ahref="http://www.barroux.org/" title="Site of the abbey">Abbey of Sainte Madeleine du Barroux</a> so that they could use a gregorian font. This font, <ahref="http://anatoletype.net/projects/gregoria" title="Presentation of the font Gregoria"><em>Gregoria</em></a>, is a professional font designed by Elena Albertoni, a typographer and graphic designer. Finally, due to licence issues, it was decided that the project would have its own font called <em>gregorio</em>.</p>
58
+
<p>From the outset the goal of the project has been to create a graphical interface for the monks of the <ahref="http://www.barroux.org/" title="Site of the abbey">Abbey of Sainte Madeleine du Barroux</a> so that they could use a gregorian font. This font, <ahref="http://anatoletype.net/projects/gregoria" title="Presentation of the font Gregoria"><em>Gregoria</em></a>, is a professional font designed by Elena Albertoni, a typographer and graphic designer. Due to licence issues, however, it was decided that the project would have its own font called <em>gregorio</em>.</p>
59
59
60
60
<p>At the end of the year 2006, a new developer, Olivier Berten, joined the project and created its Opus<spanclass="tex">T<spanclass="epsilon">e</span>X</span> component (deprecated since). By April 2007, Gregorio had reached a certain maturity and could start to be used, at least through its command line interface, as a preprocessor for Opus<spanclass="tex">T<spanclass="epsilon">e</span>X</span>. A <ahref="https://gna.org/projects/gregorio/" title="Page of the Gregorio project on Gna!">project page</a> was created at gna.org (now superceded by this site).</p>
Copy file name to clipboardExpand all lines: gregoriotex/details.html
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ <h1>Detailed information on Gregorio<span class="tex">T<span class="epsilon">e</
61
61
62
62
<h2>Best practices for creating an engraved score</h2>
63
63
64
-
<p>In order to produce a perfect result and avoid errors in placement, you may need to specify some changes in line breaks by hand. The following is the most effective and simple method:</p>
64
+
<p>In order to produce a better result and avoid errors in placement, you may need to specify some changes in line breaks by hand. The following is the most effective and simple method:</p>
65
65
66
66
<ul>
67
67
<li>produce a gabc file describing your score, without specifying any formatting</li>
@@ -177,7 +177,7 @@ <h3>Adding indications to the score</h3>
177
177
178
178
<p>To add indications above the initial letter, you can use the macro <code>\greannotation{}</code>. The argument is the text you wish to set there. To get multiple lines, simply call the command multiple times. Each call will add a new line to the bottom containing the new text.</p>
179
179
180
-
<p>By default new lines are alinged center with the existing content. If you want to adjust the horizontal alignment by hand, add the optional argument <code>[r]</code> or <code>[l]</code> for right and left alignment respectively: e.g. <code>\greannotation[r]{right aligned second line}</code></p>
180
+
<p>By default new lines are aligned center with the existing content. If you want a different horizontal alignment, add the optional argument <code>[r]</code> or <code>[l]</code> for right and left alignment respectively: e.g. <code>\greannotation[r]{right aligned second line}</code></p>
181
181
182
182
<p>To adjust the vertical placement of the annotations, you need to change <code>annotationraise</code> using <code>\grechangedim</code>: <code>\grechangedim{annotationraise}{1 mm}{scalable}</code>. Positive values will raise the annotations, negative values will lower them.</p>
183
183
@@ -189,7 +189,7 @@ <h3>Adding indications to the score</h3>
189
189
190
190
<h3>Modifying the spacing</h3>
191
191
192
-
<p>Gregorio defines a bunch of distances which control the spacing between the various elements of a score. These distances are defined in the file <code>gsp-default.tex</code>. If you want to create your own custom set of spacings, copy this file and rename it in <code>gsp-myspaces.tex</code>, change the values of the spaces and call <code>\greloadspaceconf{myspaces}</code>. <code>myspaces</code> is arbitrary, so you can replce it (in both the file name and the command argument) by whatever you want, thus allowing you to have several different spacing configurations that you can load as needed.</p>
192
+
<p>Gregorio defines a bunch of distances which control the spacing between the various elements of a score. These distances are defined in the file <code>gsp-default.tex</code>. If you want to create your own custom set of spacings, copy this file and rename it in <code>gsp-myspaces.tex</code>, change the values of the spaces and call <code>\greloadspaceconf{myspaces}</code>. <code>myspaces</code> is arbitrary, so you can replace it (in both the file name and the command argument) by whatever you want, thus allowing you to have several different spacing configurations that you can load as needed.</p>
193
193
194
194
<p>If you just need to change a few distances, then you can use the command <code>\grechangedim</code>. The available distances that can be changed are:
<p>A lot of useful things can be done with Gregorio<spanclass="tex">T<spanclass="epsilon">e</span>X</span>. For example:</p>
525
525
526
526
<ul>
527
-
<li><code>\gresetlines{invisible}</code>removes completely the staff lines.</li>
528
-
<li><code>\gresetclef{invisible}</code> removes the keys.</li>
529
-
<li><code>\gresetstaffthicknes{<i><integer></i>}</code> changes the thickness of the staff lines. The default value is the same as the staff size. You can only put integers here.</li>
527
+
<li><code>\gresetlines{invisible}</code> completely removes the staff lines.</li>
528
+
<li><code>\gresetclef{invisible}</code> removes the clefs.</li>
529
+
<li><code>\grechangestaffthicknes{<i><integer></i>}</code> changes the thickness of the staff lines. The default value is the same as the staff size. You can only put integers here.</li>
530
530
<li><code>\gresetgregoriofont[op]{parmesan}</code> uses the Dominican varian of the Parmesan font for the neumes.</li>
531
-
<li><code>\gresetbolshifts{disable}</code> slightly changes the beginning of line algorithm. <code>\greseteolshifts{enable}</code> restores the default spacing at the beginning of lines.</li>
531
+
<li><code>\gresetbolshifts{disable}</code> slightly changes the beginning of line algorithm. <code>\gresetbolshifts{enable}</code> restores the default spacing at the beginning of lines.</li>
532
532
<li><code>\gresetglyphstyle{mensural}</code>, <code>\gresetglyphstyle{hufnagel}</code> and <code>\gresetglyphstyle{medicaea}</code> change the style of some signs.</li>
533
533
<li><code>\gresetlinesbehindpunctumcavum{visible}</code> unhides the staff lines behind the punctum cavum (allowing one to see them in the middle).</li>
534
534
<li><code>\gresetlinesbehindalteration{invisible}</code> unhides the staff lines behind the alterations (allowing one to see them in the middle).</li>
0 commit comments