Merge pull request #112 from igneus/special-characters-clarification

Special characters: don't suggest that `<sp>'y</sp>` should work by default

Author: rpspringuel

gabc/details.html

@@ -331,7 +331,7 @@ <h3 id="braces">Braces above notes</h3>
 
 <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 it's 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>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>.
 

gabc/index.html

@@ -494,9 +494,11 @@ <h3 id="initial">Initial determination</h3>
 
 <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 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>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>, the barred R (℟ for <em>Response</em>), and the barred V (℣ for <em>Versicle</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 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>.
+<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 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>  The <code>\gresetspecial{spcode}{replacewith}</code> command can be used to define additional special characters, e.g. <code>\gresetspecial{'y}{ý}</code> allows entering <em>ý</em> as <code>&lt;sp&gt;'y&lt;/sp&gt;</code></p>
+
+<p>Finally, you can make use of the <code>&lt;v&gt;</code> markup tags to enter a character using its <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>
 
 <h3 id="textstyle">Text style</h3>
 

tutorial/tutorial-gabc-01.html

@@ -97,7 +97,7 @@ <h2>Exaudivit</h2>
     <dt><code>annotation: ;</code></dt>
         <dd>Like commentary, annotations refer to a very specific part of the score in gabc parlance.  In this case it’s the text which goes above the initial.  Our score has two lines there, and fortunately gabc supports up to two annotation headers.</dd>
     <dt><code>centering-scheme: english;</code></dt>
-        <dd>This header is actually a legacy header which is no longer supported in Gregorio.  It formerly controlled how the text of the lyrics aligned with the notes above.  This is now controlled in the <span class="tex">T<span class="epsilon">e</span>X</span> of a document, but because Illuminare doesn’t give you access to that, it's continued use of an older version of Gregorio means that you still have access to it.  In this case our text is in Latin and thus follows the <a href="../graphy.html">Latin alignment conventions</a>.  In more recent versions of Gregorio we refer to this as <code>vowel</code> centering in order to be more descriptive.</dd>
+        <dd>This header is actually a legacy header which is no longer supported in Gregorio.  It formerly controlled how the text of the lyrics aligned with the notes above.  This is now controlled in the <span class="tex">T<span class="epsilon">e</span>X</span> of a document, but because Illuminare doesn’t give you access to that, its continued use of an older version of Gregorio means that you still have access to it.  In this case our text is in Latin and thus follows the <a href="../graphy.html">Latin alignment conventions</a>.  In more recent versions of Gregorio we refer to this as <code>vowel</code> centering in order to be more descriptive.</dd>
     <dt><code>%fontsize: 12;</code></dt>
     <dt><code>%spacing: vichi;</code></dt>
     <dt><code>%font: OFLSortsMillGoudy;</code></dt>