Mariage

Four tasks have been cleared off the list -- two had already been fixed, and just needed checking, but others had to be implemented. Fixes detailed on the original posts.

The cleanup of notes resulting from input by site reviewers last year resulted in many <note>s being reduced to a single word, which is often a simple correction for the word or phrase being annotated. Such cases are not actually <note>s at all; they're better represented by <choice>/<sic>/<corr>, in the same way as we already use <choice>/<orig>/<reg>. Noticing this, we also noticed that the <mentioned> tag has been rather misused in some cases, when either <quote>, <soCalled> or nothing at all would be more appropriate. I've also added a handler for <choice>/<sic>/<corr> which is parallel with the existing one for <choice>/<orig>/<reg>

I've worked through the Sonnet 1609 text to change all such <note>s to <choice>/<sic>/<corr>; some should be <choice>/<orig>/<reg>, but I can't determine that, so LSPW will make another pass through the file and fix those. This markup can then be used as a model where similar situations pertain in other files.

EDIT: Bug fixed by MDH 2011-12-22.

I found the following problems with the Le Blanc table of contents that need to be fixed:

1) When you click on the following page number links, they don't jump to the corresponding page in the body of the text:

<ref type="pageNum" target="#p_1" rend="float: right;">page I</ref>

<ref type="pageNum" target="#p_564" rend="float: right;">564</ref>

<ref type="pageNum" target="#p_621" rend="float: right;"><choice><sic>611</sic><corr>621</corr></choice></ref>

<ref type="pageNum" target="#p_644" rend="float: right;">644</ref>

2) Page number 76 should be in line with the chapter heading in <rs> tag but it appears on the following line even though there is no <lb/>.

Following much discussion of the way we handle abbreviations, we're now thinking that it would be desirable to compile some example images, one for each generic type of abbreviation, from our source pages, and link them into the abbreviation definitions. For the first stage in this, MDH should use XQuery to extract a list of all abbreviations marked up in the text, along with their page numbers, so we can look through and pick out the best examples in each case.

Fixed a bug with page number positioning by re-working some of the margins on the various types of <fw>. Changes documented in CSS file.

This bug proved to be a bug in Firefox so it's now closed.

<g> elements were previously only handled when they occurred within <abbr> tags, but they do occur elsewhere, so I've now added a new handler which shows their character description as a mouseover popup wherever they show up. The original handler for <xsl:template match="choice[child::abbr[descendant::g] and child::expan]"> has also been tweaked so that it more clearly distinguishes between the expansion of the abbreviation, and the explanation of the one or more gaiji characters which appear in it.

The original References page has now been split into two indexes, "Noms propres" and "Terminologie médicale". These were the required changes:

• LSPW split off the medical items into a separate file called botanical.xml, also in the references subcollection.
• The XQuery now looks for a parameter called "index", and if it's set to "med", uses the botanical.xml file; if it's set to "nom" uses the regular references.xml file; and otherwise collects all the references. It includes the parameter in its XML output in the form of an @subtype attribute on the parent <list> element that contains the reference <item>s.
• The XSLT checks the @subtype parameter and retrieves the appropriate page title and introductory text for the reference list.
• The original Index menu item has been split into two.

There is currently no way to retrieve the full page with all references from a menu item or a link, although of course it's still there at its original location. Should we include a link on each of the reference pages enabling the user to see the complete merged list? If so, what should it say?