Typos and other small changes

gabc/details.html

@@ -93,7 +93,7 @@ <h3 id="liquescences">Liquescentiae and <em>initio debilis</em> figures</h3>
 <br /><em>Torculus</em> and <em>torculus initio debilis</em>&nbsp;: <code>fgf -fgf</code>
 </div>
 
-<p>For liquescentiae, three types exist, which are indicated by characters at the end of the neumes:</p>
+<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
@@ -108,17 +108,17 @@ <h3 id="liquescences">Liquescentiae and <em>initio debilis</em> figures</h3>
 
 <h3 id="signs">Rhythmic signs</h3>
 
-<p>The <em>punctum mora</em> (dots after the note) are denoted by adding a period (<strong><code>&nbsp;.&nbsp;</code></strong>) after the note. When there are two dots after a neume, the character is simply doubled: (<strong><code>&nbsp;..&nbsp;</code></strong>) .</p>
+<p>The <em>punctum mora</em> (dots after the note) are denoted by adding a period (<strong><code>&nbsp;.&nbsp;</code></strong>) after the note. When there are two dots after a neume, the character is simply doubled: (<strong><code>&nbsp;..&nbsp;</code></strong>).</p>
 
 <p>The vertical <em>episema</em> does not pose a problem; it is denoted by an apostrophe(<strong><code>&nbsp;'&nbsp;</code></strong>) after the note. </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>&nbsp;_&nbsp;</code></strong>) after every note that is under an episema.</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>&nbsp;ghg~.&nbsp;</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>&nbsp;ghg~.&nbsp;</code></strong>.</p>
 
-<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>&nbsp;_0&nbsp;</code></strong>. This can be combined with a normal horizontal episemus.</p>
+<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>&nbsp;_0&nbsp;</code></strong>. This can be combined with a normal horizontal episemus.</p>
 
 <div class="legende">
 <img src="../illus/allsigns.png" title="" alt="" />
@@ -245,7 +245,7 @@ <h3 id="translation">Translation and text above notes</h3>
 
 <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>
 
-<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>&lt;alt&gt;</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>
+<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>&lt;alt&gt;</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/translationalt.png" alt="">
@@ -261,16 +261,16 @@ <h3 id="choral">Choral signs</h3>
 
 <h3 id="comments">Comments</h3>
 
-<p>After the character <code>%</code>, all the characters of the line will be ignored.</p>
+<p>All the characters on a line after a <code>%</code> will be ignored.</p>
 
 <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>&lt;v&gt;</code> markups in the syllable text.</p>
+<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>&lt;v&gt;</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, remplacing <code>\mycode</code> with the code you want to insert</li>
+<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>

gabc/index.html

@@ -214,8 +214,7 @@ <h3 id="header">Header</h3>
 <dd><a name="mode">mode</a></dd>
 <dt>The mode of the piece.  This should
 normally be an arabic number between 1 and 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 <a href="#annotation">annotation field</a>.</dt>
+cases.  Note that this will only appear above the initial if the <a href="#annotation">annotation field</a> is not provided.</dt>
 
 <dd><a name="initial-style">initial-style</a></dd>
 <dt>The style of the initial letter.  0 means no initial letter, 1 a
@@ -339,7 +338,7 @@ <h2 id="text">Text</h2>
 <p>When there is no character under a separation bar, we proceed the same way, but with a space instead of text:</p>
 
 <div class="commandline">
-<code>su(iji)\ae,(i) (;) in(e)</code>
+<code>su(iji)<sp>ae</sp>,(i) (;) in(e)</code>
 </div>
 
 <h3 id="textcentering">Text centering</h3>
@@ -352,23 +351,23 @@ <h3 id="textcentering">Text centering</h3>
 
 <h3 id="initial">Initial determination</h3>
 
-<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>
+<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>
 
 <p>Note that in the case of a syllable composed of one letter only, Gregorio<span class="tex">T<span class="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>
 
 <h3 id="specialcharacters">Special characters</h3>
 
-<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>
+<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>
 
-<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>&lt;sp&gt;</code> markup tags, for example <code>&lt;sp&gt;R/&lt;/sp&gt;</code> for the crossed R, <code>&lt;sp&gt;'ae&lt;/sp&gt;</code> for <em>ǽ</em>.  This also works for the crossed A, even though it is not in the unicode table: <code>&lt;sp&gt;A/&lt;/sp&gt;</code></p>  Finally, you can make use of the <code>&lt;v&gt;</code> markup tags to enter a character using it's <span class="tex">T<span class="epsilon">e</span>X</span> code: <code>&lt;v&gt;{\ae}&lt;/v&gt;</code> for <em>æ</em>.
+<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>&lt;sp&gt;</code> markup tags, for example <code>&lt;sp&gt;R/&lt;/sp&gt;</code> for the barred R, <code>&lt;sp&gt;'ae&lt;/sp&gt;</code> for <em>ǽ</em>.  This also works for the barred A, even though it is not in the unicode table: <code>&lt;sp&gt;A/&lt;/sp&gt;</code></p>  Finally, you can make use of the <code>&lt;v&gt;</code> markup tags to enter a character using it's <span class="tex">T<span class="epsilon">e</span>X</span> code: <code>&lt;v&gt;{\ae}&lt;/v&gt;</code> for <em>æ</em>.
 
 <h3 id="textstyle">Text style</h3>
 
-<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>&lt;i&gt;</code> for italic, <code>&lt;b&gt;</code> for bold, <code>&lt;u&gt;</code> for underline (does not work in Plain <span class="tex">T<span class="epsilon">e</span>X</span>), <code>&lt;c&gt;</code> for colored (specifically in <code>gregoriocolor</code>), and <code>&lt;sc&gt;</code> for small capitals.</p>
+<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>&lt;i&gt;</code> for italic, <code>&lt;b&gt;</code> for bold, <code>&lt;u&gt;</code> for underline (does not work in Plain <span class="tex">T<span class="epsilon">e</span>X</span>), <code>&lt;c&gt;</code> for colored (specifically in <code>gregoriocolor</code>), and <code>&lt;sc&gt;</code> for small capitals.</p>
 
 <p>For example: <code>&lt;i&gt;Ps.&lt;/i&gt;(::)</code></p>
 
-<p>You have now read the basics of the gabc notation, you can go on the <a href="details">details page</a> if you want to know more!</p>
+<p>You have now read the basics of the gabc notation, you can go on the <a href="details.html">details page</a> if you want to know more!</p>
 
 <!-- footer -->
     </div>

gregorio-history.html

@@ -55,7 +55,7 @@ <h1>History of the Gregorio project</h1>
 
 <p>The Gregorio project was born in 2006 at <a href="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 <a href="http://www.telecom-bretagne.eu/studies/msc/professors/haralambous/" >Mr Yannis Haralambous</a>, developer of <a href="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>
 
-<p>From the outset the goal of the project has been to create a graphical interface for the monks of the <a href="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, <a href="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>
+<p>From the outset the goal of the project has been to create a graphical interface for the monks of the <a href="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, <a href="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>
 
 <p>At the end of the year 2006, a new developer, Olivier Berten, joined the project and created its Opus<span class="tex">T<span class="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<span class="tex">T<span class="epsilon">e</span>X</span>. A <a href="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>
 

gregoriotex/details.html

@@ -61,7 +61,7 @@ <h1>Detailed information on Gregorio<span class="tex">T<span class="epsilon">e</
 
 <h2>Best practices for creating an engraved score</h2>
 
-<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>
+<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>
 
 <ul>
 <li>produce a gabc file describing your score, without specifying any formatting</li>
@@ -177,7 +177,7 @@ <h3>Adding indications to the score</h3>
 
 <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>
 
-<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>
+<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>
 
 <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>
 
@@ -189,7 +189,7 @@ <h3>Adding indications to the score</h3>
 
 <h3>Modifying the spacing</h3>
 
-<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>
+<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>
 
 <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:
 
@@ -524,11 +524,11 @@ <h3>Other useful things</h3>
 <p>A lot of useful things can be done with Gregorio<span class="tex">T<span class="epsilon">e</span>X</span>. For example:</p>
 
 <ul>
-<li><code>\gresetlines{invisible}</code> removes completely the staff lines.</li>
-<li><code>\gresetclef{invisible}</code> removes the keys.</li>
-<li><code>\gresetstaffthicknes{<i>&lt;integer&gt;</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>
+<li><code>\gresetlines{invisible}</code> completely removes the staff lines.</li>
+<li><code>\gresetclef{invisible}</code> removes the clefs.</li>
+<li><code>\grechangestaffthicknes{<i>&lt;integer&gt;</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>
 <li><code>\gresetgregoriofont[op]{parmesan}</code> uses the Dominican varian of the Parmesan font for the neumes.</li>
-<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>
+<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>
 <li><code>\gresetglyphstyle{mensural}</code>, <code>\gresetglyphstyle{hufnagel}</code> and <code>\gresetglyphstyle{medicaea}</code> change the style of some signs.</li>
 <li><code>\gresetlinesbehindpunctumcavum{visible}</code> unhides the staff lines behind the punctum cavum (allowing one to see them in the middle).</li>
 <li><code>\gresetlinesbehindalteration{invisible}</code> unhides the staff lines behind the alterations (allowing one to see them in the middle).</li>