-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathdetails.html
383 lines (272 loc) · 26.1 KB
/
details.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<!--
Gregorio web site.
Copyright (C) 2007-2015 The Gregorio project
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
-->
<title>Gregorio project website</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta name="description" content="Free software for typesetting Gregorian chant" lang="en">
<meta name="keywords" content="Gregorian chant, gregorio, gabc, gregoriotex" lang="en">
<meta name="author" content="The Gregorio project">
<link rel="shortcut icon" href="../illus/fav.ico">
<link rel="icon" href="../illus/fav.ico">
<link rel="stylesheet" href="../style.css" type="text/css" title="default">
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
<script type="text/javascript" src="../gregorio-menu.js"></script>
<script>
var context = 'gregorio';
var title = 'Gregorio project website'
</script>
</head>
<body>
<div id="ban">
<img src="../illus/harpedroite.png" title="" class="hd" alt="" />
<a id="haut" name="haut"></a>
<div id="banniere">
</div>
</div>
<script>write_gre_menu();</script>
<div class="flux">
<!-- IE patch-->
<div class="text">
<!-- End of header -->
<!-- header -->
<script>
context = 'gabc';
title = 'GABC Notation';
</script>
<h1>GABC Notation</h1>
<div class="toc">
<h1>Table of contents</h1>
<h2><a href="#advancednotation">Advanced notation</a></h2>
<h3><a href="#liquescences">Liquescentiae and <em>initio debilis</em> figures</a></h3>
<h3><a href="#signs">Rhythm signs</a></h3>
<h3><a href="#alterations">Flats and naturals</a></h3>
<h3><a href="#spaces">Spaces</a></h3>
<h3><a href="#determination">Determination of the neume according to the sequence of notes</a></h3>
<h3><a href="#repetitions">Optional characters and repetitions</a></h3>
<h2><a href="#advanceddetails">Advanced details</a></h2>
<h3><a href="#podatus">The podatus</a></h3>
<h3><a href="#accents">Empty notes and accents</a></h3>
<h3><a href="#polyphony">Polyphony</a></h3>
<h3><a href="#endofline">Ends of line</a></h3>
<h3><a href="#custos">Custos</a></h3>
<h3><a href="#translation">Translation</a></h3>
<h3><a href="#alt">Text above notes</a></h3>
<h3><a href="#choral">Choral signs</a></h3>
<h3><a href="#comments">Comments</a></h3>
<h3><a href="#elision">Elision</a></h3>
<h3><a href="#verbatim">Insert code (for advanced users)</a></h3>
<h3><a href="#braces">Braces above notes</a></h3>
<h2><a href="#conclusion">Conclusion and extensions</a></h2>
<h2><a href="#example">Complete example</a></h2>
</div>
<h2 id="advancednotation">Advanced notation</h2>
<h3 id="liquescences">Liquescentiae and <em>initio debilis</em> figures</h3>
<p>The notation of an <em>initio debilis</em> is simple: you simply add a hyphen (<strong><code> - </code></strong>) before the note to be affected.</p>
<div class="legende">
<img src="../illus/initiodebilis.png" title="" alt="" />
<br /><em>Torculus</em> and <em>torculus initio debilis</em>
</div>
<p>For liquescentiae, three types exist, which are indicated by a character at the end of the neume:</p>
<ul>
<li>diminutive liquescentiae, indicated by <code>~</code></li>
<li>increasing liquescentiae
<ul>
<li>ascending indicated by <code><</code></li>
<li>descending indicated by <code>></code></li>
</ul>
</li>
</ul>
<p>Liquescentiae are indicated after other characters that determine the note.</p>
<h3 id="signs">Rhythmic signs</h3>
<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>
<p>The vertical <em>episema</em> (also called the <em>ictus</em>) is denoted by an apostrophe (<strong><code> ' </code></strong>) after the note. Gregorio will place the episema above or below the note according to the context, however you can force its position with<strong><code> '0 </code></strong>(for always below) and<strong><code> '1 </code></strong>(for always above).</p>
<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>
<p>For the horizontal episema, type an underscore (<strong><code> _ </code></strong>) after every note that is under an episema. Like the vertical episema, Gregorio will place the horizontal episema above or below the note according to the context, but you can force its position with<strong><code> _0 </code></strong>(for always below) and<strong><code> _1 </code></strong>(for always above).</p>
<p>By default, horizontal episemas on adjacent notes will automatically be bridged (joined together). The command <code>\gresethepisema{break}</code> will prevent this behavior, while <code>\gresethepisema{bridge}</code> restore it. To prevent Gregorio from attempting to bridge two episema in just a single glyph, you can use<strong><code> _2 </code></strong>.</p>
<p>In some cases you may want the episema to be slightly shorter than normal. This can be accomplished with <strong><code> _3</code></strong>, <strong><code> _4</code></strong>, and <strong><code> _5 </code></strong>corresponding to the short episema being aligned to the left, center, and right of the note respectively. These short episema can be combined with the normal ones (placing two horisontal episema on the same note), so long as the direction for the longer one is specified and they are not on the same side of the note. You can also prevent them from bridging to adjacent notes that also have episema with<strong><code> 2</code></strong>, allowing up to three numbers to be appended to<strong><code> _</code></strong>.</p>
<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>
<div class="legende">
<img src="../illus/allsigns.png" title="" alt="" />
<br />The different signs
</div>
<h3 id="alterations">Alterations</h3>
<p>Two letters have been chosen to represent the flat and the natural: <code>x</code> <code>y</code>. As these signs take the space of a note, we notate them like a note, for example, <code>ix</code> for a flat on the staff position represented by <code>i</code>.</p>
<p>Note that you can also type a sharp in gabc, with the character <code>#</code>.</p>
<div class="legende">
<img src="../illus/alterations.png" title="" alt="" />
<br />The alterations
</div>
<h3 id="spaces">Spaces</h3>
<p>Spaces are very important in Gregorian chant. When monks transposed scores from ancient neumes into square notation, the equivalence was not exact, and some ancient figures have been translated by a larger space between two notes of a neume. Although this phenomenon is quite rare, it exists, and it is necessary to take it into consideration in order to preserve every detail of a work.</p>
<p>Five spaces are used in Gregorian chant:</p>
<ul>
<li><strong>neumatic cut</strong>: within a neume, the neumatic elements are separated by this space, which is the smallest space;</li>
<li><strong>large neumatic cut</strong>: this is the space described in the paragraph above; it is used in the same way as the neumatic cut, but the space is larger;</li>
<li><strong>glyph space</strong>: this is equivalent to the size of a punctum and serves to mediate between the <em>puncta inclinata</em> of a climacus whose range is greater than a third</li>
<li><strong>syllabic space</strong>: the space between two neumes corresponding to two syllables of the same word</li>
<li><strong>word space</strong>: the space between two words. This space is more difficult: it is the space between both the letters and the notes of two different words. This space is also the one between words and separation bars.</li>
</ul>
<p>The neumatic cut is denoted by a slash (<strong><code> / </code></strong>), and the larger neumatic space, more rare, by two slashes (<strong><code> // </code></strong>). A glyph space is indicated by a normal space. Syllabic and word spaces are automatically calculated by the software, according to the text, and this poses no difficulty. The glyph space is automatically included when there is a climacus with an interval of a third or greater.</p>
<p>While the above standard spaces should suffice for most scores, there are occasions where it is necessary to fine tune the spacing even further. For this purpose the half-space (<code>/0</code>) and the ability to arbitrarily scale the neumatic cut (<code>/[<i>factor</i>]</code>) are provided. The scaling factor for this last one can even be negative, allowing you to overlap the horizontal position of notes.</p>
<p>Besides these spaces, gabc recognizes two ways of saying "no space here". The first is the exclamation point (<code>!</code>) which means there should be no connection between the notes and the second is the "at" symbol (<code>@</code>) which connects the two notes together. This latter process is referred to as fusion and allows you to create neumes which would not otherwise be possible (especially useful for neumes with 5 or more notes).</p>
<div class="legende">
<img src="../illus/spaces.png" title="" alt="" />
<br />Examples of spaces
</div>
<p>Note that for practical reasons, a space (<code>/</code> <i>etc.</i>) can be set unbreakable if you precede it with the exclamation point (<code>!</code>).</p>
<h3 id="determination">Determination of the neume according to the sequence of notes</h3>
<p>Regarding notation, we should say first that it is not useful to specify a <em>virga</em> in a neume, as linking bars between notes will be automatically added when necessary. Except for <em>virga</em> (which can be a glyph inside another neume), <em>bivirga</em> or <em>trivirga</em> neumes, there is no place for entering a <code>v</code> when you type the sequence of notes of a neume.</p>
<p>To any sequence of notes and spaces corresponds one and only one written form. The only exception is the sequence of three or more ascending notes. To determine the written form to use in this case, we must introduce a character to prevent linking between two notes. This character is <code>!</code> . It allows us to have a complete equivalence between our notation and the written form. But be aware that this #dicates a space of zero width: it is the only "space" that can be found within a glyph.</p>
<div class="legende">
<img src="../illus/pointdexclamation.png" title="" alt="" />
<br />Effects of <code>!</code> on glyph determination
</div>
<h3 id="repetitions">Optional characters and repetitions</h3>
<p>For neumes that repeat the same note several times, it is possible to achieve faster notation. For example, for the <em>bivirga</em> two <code>v</code> are added after the note, and for the <em>tristropha</em> three <code>s</code>. The result will be the same if each detail is written: <code>hs/hs/hs</code> = <code>hsss</code>.</p>
<div class="legende">
<img src="../illus/bistrophatristropha.png" title="" alt="" />
<br /><em>bistropha</em> and <em>tristropha</em>
</div>
<h2 id="advanceddetails">Advanced details</h2>
<h3 id="podatus">The podatus</h3>
<p>The <em>podatus</em> poses a difficulty for square notation in general, because there are seven ways of denoting it in ancient notation, and much fewer in square notation. In the Solesmes hymnary of 1983, two new notations were introduced: the <em>pesquassus</em> and the <em>podatus initio debilis</em>. The first is written using an o after the first note, as it is an <em>oriscus</em>, and the second is written logically with a - before the first note.</p>
<p>A new written form of the podatus is also proposed here. It could be used to distinguish <em>pes quadratus</em> of the old notation that is currently transcribed in the same way that the light <em>pes</em> and the <em>pes</em> with episema are. In this new written form of the podatus, the second note is located to the right of the bar that links the two notes, and not to the left. These <em>pes quadratus</em> are notated by adding a <code> q </code> between the two notes.</p>
<div class="legende">
<img src="../illus/q1.png" alt=""/>
<br /><em>Pes quadratum</em> and <em>Pes quilisma quadratum</em>
</div>
<h3 id="accents">Empty notes and accents</h3>
<p>As the empty notes and accents are quite rare, the notation to get them is not very intuitive, but is still simple: simply add the following signs after your note:</p>
<ul>
<li>punctum cavum (also works with a punctum inclinatum and punctum inclinatum auctus): r</li>
<li>linea punctum: R</li>
<li>linea punctum cavum: r0</li>
<li>accentus: r1</li>
<li>reversed accentus: r2</li>
<li>circulus: r3</li>
<li>semi-circulus: r4</li>
<li>reversed semi-circulus: r5</li>
</ul>
<div class="legende">
<img src="../illus/empty-accents.png" alt=""/>
<br /><em>Empty notes and accents</em>
</div>
<h3 id="polyphony">Polyphony</h3>
<p>The goal of the notation presented here is to represent Gregorian chant, and thus songs in only one voice. However, the first polyphonic pieces were written in square notation, even if the current notation is slightly different, so it seemed important to consider the case of people who would want to write polyphonic scores in square notation.</p>
<p>Sadly the typography of polyphony on several levels of staffs is way more difficult than the normal typography, and it's not yet possible (with Gregorio or any other serious gregorian software of which we are aware). Gregorio does support a simple notation for simple polyphony on one staff line. This is possible in gabc when putting the first note of a vertically aligned group between curly brackets:</p>
<div class="legende">
<img src="../illus/polyphony.png" alt=""/>
<br />Simple polyphonic notation
</div>
<p>As a result of the difficulty in rendering polyphony typographically, there are a few quirks with the above notation that users should be aware of:</p>
<ul>
<li>The notes in curly braces must go first.</li>
<li>You can alternate notes in curly braces and notes outside them in the same syllable, but the curly braces are effectively a zero-width space (<code>!</code>) between the notes on either side of them. If using this alternating pattern, you will need to manually space between the various groups of notes in the same syllable.</li>
<li>The notes in curly braces are ignored for spacing purposes; only the notes outside the curly braces count. This means if they are wider than the notes outside curly braces which immediately follow, then they may run into the next element. You'll need to add manual spaces outside the curly braces to prevent this.</li>
<li>No attempt is made to avoid collisions between the two voices. It is the users responsibility to introduce manual spacing to avoid said collisions.</li>
<li>At the end of the line the automatic custos will be set based on the first note in the next syllable, even if it is inside curly braces.</li>
</ul>
<p>Since polyphony is so rare in Gregorian chant, improving the behavior of Gregorio in this area is extremely low on the list of priorities for the developers. If you find yourself using this feature and want improvements, then you are most likely going to have to make them yourself (see <a href="https://github.com/gregorio-project/gregorio/blob/master/CONTRIBUTING.md">the contributing guide</a> for how to get started).</p>
<h3 id="endofline">End of line</h3>
<p>The end of line is automatically determined by the Gregorio<span class="tex">T<span class="epsilon">e</span>X</span>. However, under some circumstances it can be useful for you to specify it because it improves the rendering. To force an end of line at the end of a syllable put <code>z</code> inside parentheses after the notes. If you want your line to end without being justified, use <code>Z</code> instead.</p>
<p>You can also prevent a line break from occurring within a group of syllables by using the “no line break area” tags (<code><nlba></nlba></code>). The opening tag should be placed before the lyrics at the start of the group and the closing tag after the lyrics at the end of the group: <code><nlba>these(g) words(g) will(h) not(h) be(g) split</nlba>(g)</code> </p>
<h3 id="custos">Custos</h3>
<p>By default the custos (an indication of the first note on the next line) is automatically generated at each line ending within a score, whether that line ending be automatic or manually determined. By setting <code>\greseteolcustos{manual}</code> those custos are turned off. Further, the behavior at a manual line break (<code>z</code> or <code>Z</code>) can be specified on a case-by-case basis. Adding a <code>+</code> will force the custos to appear at that line break while adding a <code>-</code> will suppress it at that particular line break.</p>
<p>In some cases, it may be necessary to typeset a custos inside a line. This is the case of a clef change, for example. In this particular case, simply type <code>z0</code> before the clef change to get it; its height will be calculated automatically.</p>
<div class="legende">
<img src="../illus/clef-change.png" alt="">
</div>
<p>In other cases where a manual custos is required (such as at the end of a score where there is no next note for the automatic calculation), you can input it manually with <code>g+</code>, replacing <code>g</code> with the height you want.</p>
<h3 id="translation">Translation</h3>
<p>To add a translation (or a second line of text), simply put it between square brackets in the syllable text. By default the text will be left-aligned with the text of the syllable, but you can force it to center below the syllable with <code>\gresettranslationcentering{center}</code>. In either case, the translation won't go to the next line automatically. Thus it may require a bit of work to get the desired effect.</p>
<p>It is also possible to span the centering of a translation over several syllables. To do this you enter the translation as normal on the syllabe which you want to start the centering span and enter <code>[/]</code> as the translation for the syllable which ends the centering span. If you do this, the multi-syllable translation will be centered over the span of syllables regardless of the setting for translation centering for an individual syllable.</p>
<div class="legende">
<img src="../illus/translation.png" alt="">
</div>
<h3 id="alt">Text above notes</h3>
<p>There are two ways to add text above notes: 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>
<div class="legende">
<img src="../illus/alt.png" alt="">
</div>
<h3 id="choral">Choral signs</h3>
<p>It is possible to produce choral signs in gabc. To do so add <code>[cs:t]</code> after the note for which you want the sign, replacing <code>t</code> with the sign you desire.</p>
<div class="legende">
<img src="../illus/choralsign.png" alt="">
</div>
<h3 id="comments">Comments</h3>
<p>All the characters on a line after a <code>%</code> will be ignored.</p>
<h3 id="elision">Elision</h3>
<p>Starting from version 4.1, syllable text in <code><e></code> markup is considered as an elision: a syllable without any associated notes which is quickly sung as part of an adjacent syllable. This text will be output in its own style (<code>elisionstyle</code>, italic and small by default), and will be ignored by vowel finding algorithm. For example <code>cla<e>ra</e>(gh)</code> gives:</p>
<div class="legende">
<img src="../illus/elision.png" alt="">
</div>
<h3 id="verbatim">Insert code (for advanced users)</h3>
<p>It is possible to insert verbatim code in gabc, this code will appear as it is in the <span class="tex">T<span class="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>
<p>Verbatim code can also be inserted at three levels in the notes:</p>
<ul>
<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>
<li>at glyph level, forcing the glyph to stop but staying in the same element, with <code>[gv:\mycode]</code></li>
<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>
</ul>
<p>Note that macros can be defined. Let's take an example: add this in your header:</p>
<div class="commandline">
<code>def-m1:\mycode;</code>
</div>
<p>You can now call this macro in your notes using the notation <code>[nm1]</code>, <code>[gm1]</code> or <code>[em1]</code>. You can define 10 macros this way (from 0 to 9).</p>
<h3 id="braces">Braces above notes</h3>
<p>You can create braces above notes in two ways. The following syntax will create a brace of fixed width: <code>[ob:1;6mm]</code> where</p>
<ul>
<li><code>o</code> represents position of the brace. <code>o</code> is over the staff, <code>u</code> is under the staff.</li>
<li><code>b</code> represents the shape of the brace: a round brace (<code>b</code>), a curly brace (<code>cb</code>) or a curly brace with accent (<code>cba</code>). Only the round brace (<code>b</code>) works with the understaff position (<code>u</code>).</li>
<li><code>1</code> is the attachment point of the brace: the left side (1) or the right side (0) of the note immediately before the brace code</li>
<li><code>6mm</code> is the length of the brace </li>
</ul>
<p>On the other hand you can also use a syntax which allows you to specify the left (<code>[ob:0{]</code>) and right (<code>[ob:0}]</code>) extents of the brace in the notes. This syntax recognizes all possible values for position (<code>o</code> or <code>u</code>), shape (<code>b</code>, <code>cb</code>, or <code>cba</code>), and attachment point (<code>0</code> or <code>1</code>) of the brace as the fixed width brace. Additionally, while the position and shape needs to be the same for both ends of the brace, you need not specify the same attachment point for the right and left extents (<i>e.g.</i> you can start the brace on the left side of one note and end it on the right side of another).</p>
<p>When using the dynamically sized braces, you will need to compile your document twice in order to get the braces to be the right size. The first will draw the brace at its minimal size (about the width of a punctum), but will also calculate the correct positions for the start and end points and store that information for the subsequent run. The second pass will make use of the stored information to draw the brace at the correct width. Note that in order for this to work, there can be no changes to the score between the two passes.</p>
<p>By default braces are rendered using MetaPost. This allows the line weight to remain more consistent when braces are stretched. You can also render the braces using score font (the behavior in versions 3.0.3 and earlier) by calling <code>\gresetbracerendering{font}</code>.
<div class="legende">
<img src="../illus/ob.png" alt="">
</div>
<h2 id="conclusion">Conclusion and extensions</h2>
<p>Some very advanced features of gabc are documented in GregorioRef-###.pdf (where ### is the version number), please take a look if you cannot find what you need.</p>
<p>If some aspects have been overlooked or if a new written form should appear, many ASCII characters have not yet been used in our notation and remain available, for example, the letters <em>n, p, t</em> and <em>u</em>, both upper- and lower-case.</p>
<p>If you think gabc lacks a feature or see a bug, please report on <a href="https://github.com/gregorio-project/gregorio/issues" title="">the issue tracker</a>.</p>
<p>The representation of ancient notation is currently in development. Please see GregorioNabcRef-###.pdf (where ### is the version number) for an explanation of the notation as it has been implemented thus far.</p>
<h2 id="example">A complete example</h2>
<div class="legende">
<img src="../illus/complet.png" alt=""/>
</div>
<div class="commandline">
<code>name: Populus Sion;</code><br />
<code>%%</code><br />
<code>(c3) Pó(eh/hi)pu(h)lus(h) Si(hi)on,(hgh.) *(;) ec(hihi)ce(e.) Dó(e.f!gwh/hi)mi(h)nus(h) vé(hi)ni(ig/ih)et(h.) (,)</code><br /><br />
<code>ad(IV./hig)sal(fe~)ván(ghg)das(fg) gen(e_f_e_)tes(e.) :(:) et(e) au(eh)dí(h/hi)tam(i) fá(kjki)ci(i)et(i) Dó(ij)</code><br /><br />
<code>mi(ihi)nus(IV./hiHF) (,) gló(h!i'j)ri(ji!KVJI)am(ij~) vo(j.i!jwk)cis(ji) su(i_j_i_)æ,(i.) (;) in(e) læ(e)tí(e!f'h)ti(h)a(hi!JVji)</code><br /><br />
<code>cor(gh!ijI'H)dis(ihhf!gwh) ves(e_f_e_)tri.(e) <i>Ps.</i>(::) Qui(ehg) re(hi)gis(i) I(i)sra(i)el,(ik) in(j)tén(ji~)de(ij..) :*(:)</code><br /><br />
<code>qui(ig) de(hi)dú(i)cis(i) vel(i)ut(i!jwk) o(i')vem(h) Jo(hhh)seph.(fe..) (::) Gló(ehg)ri(hi)a(i) Pa(i)tri.(i) (:)</code><br /><br />
<code>E(i)u(i!jwk)o(i)u(h) a(hhh)e(fe..) (::)</code>
</div>
<!-- footer -->
</div>
<div class="bottom">
</div>
<script>initialize_menu();</script>
</body>
</html>