Help update on rubrics

Resources/public/help/help.xhtml

@@ -190,8 +190,8 @@ function generateTOC(toc) {
 </tr>
 </tbody>
 </table>
-<h4 id="rubrics">Entering multiple rubrics without intervening music</h4>
-<p>The  rubric field can only contain a single line of text. To  enter multiple rubrics, which will appear in multiple lines in the print edition, type the rubrics in one line and separate them using  the symbol <em>#</em>.</p>
+<h4 id="rubrics">Rubrics</h4>
+<dl><dt>Entering multiple rubrics without intervening music</dt><dd>The  rubric field can only contain a single line of text. To  enter  multiple rubrics, which will appear in multiple lines in the print  edition, type the rubrics in one line and separate them using  the  symbol <em>#</em>.</dd><dt>Line and page break markers in Rubrics<br /></dt><dd>Enter the break marker as single or double "pipe" characters, like "|| PSALMUS" or "| TROPUS". Folio numbers for such break markers can currently not be input and should be supplied to the typesetter in the separate text document.<br /></dd><dt>Rubrics below a line of music<br /></dt><dd>A rubric appearing below a line without following music should be input in the rubric field of an empty line following the last line of music.<br /></dd></dl>
 <h4>Entering special characters</h4>
 <dl><dt>Windows</dt><dd>Use Windows' <a href="http://windows.microsoft.com/en-us/windows/using-special-characters-character-map-faq">Character Map</a> to choose the symbol. Even though the font will be a different one in mono:di and the printout, best choose Arial in the Font dropdown list. Characters can be searched by name if the "Advanced view" check box is selected. For inputting ę (e-caudata), you can search for "ogonek" in the search field.<br /></dd><dt>Mac</dt><dd>Use OS X' <a href="http://support.apple.com/kb/HT1518">Character Viewer</a>. Characters can be searched. For inputting ę (e-caudata), you can search for "ogonek" in the search field.</dd></dl>
 <h3>Music level</h3>
@@ -343,10 +343,7 @@ This kind of annotation should not be over-used. Like internal  annotations, typ
 <h4>Line 2</h4>
 <dl><dt>source no.</dt> <dd>each source in the CM volume will receive a number, based on the order it appears in the       volume</dd> <dt>source identifier</dt> <dd>this is the abbreviation for the manuscript&rsquo;s shelfmark (Provins,   Biblioth&egrave;que       municipale 12 (24) is recorded here as Pro 12)</dd></dl>
 <h4>Line 3</h4>
-<dl><dt>transcription numbers (order in source: printed transcription number)</dt> <dd>
-<p>This  field should include two numbers divided by a colon. The first number  indicates the order of the transcription in the source; the second  number appears in the print edition as the transcription number (at the  beginning of the transcription with a square       around it).</p>
-<p>As an example, in CM II-1, the first trope             complex in a source will have 1:1 in this header field. The base chant sung with this             trope complex, appearing immediately after it in the source, will have 2:1P in this             header field. On mono:di's management page, the files will be ordered           according to the <span style="text-decoration: underline;">first</span> number           in this field. Only the <span style="text-decoration: underline;">second</span> number will appear in the print edition. The first number serves a function for our typesetters; the second number serves a           coordinating function for the volume's readers.</p>
-</dd> <dt>genre</dt> <dd>of the chant (trope = trop; offertory = off)</dd> <dt>incipit</dt> <dd>standardized spelling</dd> <dt>feast</dt> <dd>also abbreviated and standardized according to Corpus troporum (Nativitas = Nat)</dd> <dt>start folio</dt> <dd>of the chant in the manuscript (22v) without f. or r.</dd></dl>
+<dl><dt>transcription numbers (order in source: printed transcription number)</dt> <dd> This  field should include two numbers divided by a colon. The first number  indicates the order of the transcription in the source; the second  number appears in the print edition as the transcription number (at the  beginning of the transcription with a square       around it). <br />As an example, in CM II-1, the first trope             complex in a source will have 1:1 in this header field. The base chant sung with this             trope complex, appearing immediately after it in the source, will have 2:1P in this             header field. On mono:di's management page, the files will be ordered           according to the <span style="text-decoration: underline;">first</span> number           in this field. Only the <span style="text-decoration: underline;">second</span> number will appear in the print edition. The first number serves a function for our typesetters; the second number serves a           coordinating function for the volume's readers. </dd> <dt>genre</dt> <dd>of the chant (trope = trop; offertory = off)</dd> <dt>incipit</dt> <dd>standardized spelling</dd> <dt>feast</dt> <dd>also abbreviated and standardized according to Corpus troporum (Nativitas = Nat)</dd> <dt>start folio</dt> <dd>of the chant in the manuscript (22v) without f. or r.</dd></dl>
 <h4>Line 4</h4>
 <p>the information for this line is recorded from the chant's text edition. If the  text edition does not       contain the information, the field can be  left blank.</p>
 <dl><dt>text edition incl. volume no</dt> <dd>for example, CT I</dd> <dt>text&rsquo;s identifying number</dt> <dd>only for text editions like Analecta hymnica, where each text receives its own number</dd> <dt>base chant incipit</dt> <dd>This field is for CT X and CT IX, which uses a base chant incipit to  identify each element. We cite exactly corresponding to CT.</dd> <dt>feast, service, base chant genre</dt> <dd>as they appear in CT, for example Nat III intr</dd> </dl>
@@ -425,7 +422,7 @@ This kind of annotation should not be over-used. Like internal  annotations, typ
 <h4 id="deleteEmptySyllable">Empty syllable can not be deleted</h4>
 <p>If you have an apparently empty syllable (no pitches, no text, but an empty dotted text box below the staff) that will not automatically disappear, check whether there is a line or folio break marker attached to it.&nbsp; The folio break will appear left to the empty syllable box.&nbsp; If that line or folio break marker is deleted, the syllable will disappear automatically.</p>
 <h4>Melismas broken over lines or pages</h4>
-<p>Break markers imported from Word documents are associated with the syllable following the break marker.&nbsp; Music that is input after the break marker will therefore be put inside the following syllable. It is currently not possible to create pitches after the break marker that are associated with the preceding syllable. To achieve the desired result, the break marker has be input a second time inside the preceding syllable. The originally generated marker has to be deleted.</p>
+<p>Break markers imported from Word documents are associated with the syllable following the break marker.&nbsp; Music that is input after the break marker will therefore be put inside the following syllable. It is currently not possible to create pitches after the break marker that are associated with the preceding syllable. To achieve the desired result, the break marker has to be input a second time inside the preceding syllable. The originally generated marker has to be deleted.</p>
 <h3>Error messages</h3>
 <h4>Server error 401</h4>
 <p>If you are receiving this error, there has not been interaction between your browser and the mono:di server for a longer timespan so that the server terminated the session. Reload the page and log in again.</p>