Mariage

EDIT by MDH 2011-12-22: I believe this task has been obviated by the proposed (and partially-implemented) change from using <argument> to using <label>. Setting this task to Completed.

Note to self: I thought I had made substantial amendments to the schema that would permit us to use <argument> inside e.g. <p>, because that's where our marginal arguments most often show up. However, in the Le Blanc text, that seems to be failing, so I need to revisit it. The text has been marked up in such a way that open ps and divs are being closed before and argument and opened again afterwards, and when I try to refactor appropriately, the code turns out not to be valid. Either the validation process is failing somehow, or the schema is not the most recent, or perhaps my modifications didn't go far enough.

EDIT by MDH 2011-12-22: I believe both of these issues are now fixed. I wrote a template to split lists and it's now in use, and I think LSPW has fixed the erroneous @target attributes. Setting this task to Completed.

Several XHTML validation issues have arisen recently. They fall into the following categories:

• Unexpected elements inside lists. le_bon_mariage.xml has many instances of page breaks, and forme works which occur inside lists. The XSLT doesn't expect this, and outputs XHTML elements inside <ul> and <ol> which are of course invalid (only <li> is allowed).
• Duplicate ids in reference links. Reference links inside the text are provided with unique ids so that you can navigate to them, and these ids are constructed from the target id of the reference itself, followed by an underscore and a number; numbers are provided in sequence by counting preceding references. This is going wrong somehow, resulting in more than one reference link with the same id attribute in the XHTML.

The first requires a policy decision (do we allow other elements than item inside of list?), followed by fixes to the XML and/or the XSLT to deal with the consequences of the policy. The second seems to be caused by typos in the @target attributes of ref elements in the references file; I've identified a set of these and asked LSPW to fix them. The same kind of typos also show up in anthology documents, so I've identified a stack of them using XQuery and sent them to LSPW too.

NOTE: With regard to the first issue, I wrote to the TEI list, and had a number of useful responses; I think the most appropriate was to keep the current markup (which is, after all, "correct"), but use a two-stage transformation to get the document to XHTML. In the first stage, any lists bisected by page breaks, forme works etc. would be split into two lists, allowing the second transform to proceed appropriately. This is a really good idea, and could also be used to handle bisected lgs, which are currently output as <ul>/<li> sets if they're not bisected, or <div>/<span> sets if they are.

Arising out of a discussion with CC: The intended use of <choice>/<orig>/<reg> in the original transcriptions of the engravings is to restore normal contemporary usage, while the modern transcription is a full modernization. However, there are instances of <choice>/<orig>/<reg> which are used to replace long s with short s (dating back to when we had no modernizations), so these are inconsistent with our policy, and we should get rid of them. I might be able to do this entirely mechanically -- in the case of any regularization where the only difference is between long and short s, I can simply replace the entire <choice> element with the contents of <orig>; while for every regularization where a long s exists in the <orig> but other things are also regularized in the <reg>, I can add an attribute we can use temporarily to find and manually fix them. This is now on my task list.

The abbreviations deriving from Latin, listed in CC's post, will be handled like this:

• Each distinct abbreviation will have a <glyph> element in the <charDecl> section of the file header, explaining it briefly.
• Each instance of the abbreviation will be marked up in the original transcription following this pattern:

  <choice>
    <abbr>Vo<hi rend="vertical-align: super;"><g ref="#theGlyphTag">9</g></hi></abbr>
    <expan>Vous</expan>
  </choice>
  

• The XSLT will display ONLY the rendered <abbr> element, and will give it a @title attribute for mouseover which is constructed from the information in the <glyph> element(s) referenced inside the <abbr>. This differs from a regular <choice>/<abbr>/<expan>, in which the <expan> is used as the @title attribute. The actual expansion will normally be available to readers in the modernized transcription, since these all occur in the engravings.

Transcription and annotation of Blanchon's Stances du mariage has been completed. The text is now published on the site, however, it appears under the category of "Satire" which is a problem because it is not a satire. CC suggests that a new category should be created, possibly "Éloges du mariage". We'll have to discuss this with MH when he returns from holiday.

In our texts, arguments frequently occur in marginal position, without interrupting the flow of the text. We now have an example of one which occurs inside one of our weird extended quote forms, so I need to make <argument> an acceptable child of <quote> in the ODD, and generate a new schema.

In both the original texts of Bon Mariage and Ville Thierry, the table of contents appears in such a way that the chapter headings/descriptions are aligned to the left while the page numbers on which the chapters begin are aligned to the right. Because of this complex formatting, we cannot simply encode the table of contents as a list as we normally do. I discussed this with MH and he will reflect on how to deal with those texts.

A bug has emerged in the handling of references which reference other references. This is how to reproduce it:

• Go to the Forest Nuptiale.
• Search for Braga, and click on the reference link.
• Inside that reference link, click on the link to Concile de Trente.
• Click on any other reference link in the document.

When the embedded Trente reference is shown, it's unformatted (paragraphs and links are missing). Thereafter, formatting is missing from any reference which shows up in the box. No idea why this is happening (yet), but we never predicted there would be references which are only linked from inside other references.

[EDIT BY MDH: I've looked at these and can't find anything wrong in any of the programming code (XSLT, CSS or XHTML output); furthermore, the extra line breaks don't occur in Opera or Google Chrome, so I conclude this is caused by a Firefox bug, and I'm marking the task as Completed.]

Just a reminder to MH to fix the following lines contained in argument tags that include an extra line break when viewed online: Lines 10327, 10358, 10396 and 10534. Thank you!

[This is in the FOREST NUPTIALE.]

1) Lines 10328-10338 (extra line break occurs between "phes" and "In-" in XSLT):

<div>
<argument rend="float: left; margin-left: -6em; text-align: left;">
<ab rend="font-style: italic; font-size: 70%; text-align: left;">
Philoſo-<lb/>
phes <ref target="../../back_matter/references/references.xml#indien">In-<lb/>
diens</ref>.<lb/>
</ab>
</argument>
<p rend="margin-top: 0; margin-bottom: 0; text-indent: 0;">
ſans la liſte des Philoſophes <ref target="../../back_matter/references/references.xml#indien">In-<lb/>
diens</ref> en font pluſieurs cantons de<lb/>

2) Lines 10359-10368 (extra line break also occurs between "phes" and "In-" in XSLT):

<div>
<argument rend="float: right; margin-right: 5em; text-align: left;">
<ab rend="font-style: italic; font-size: 70%; text-align: left;">
Philoſo-<lb/>
phes <ref target="../../back_matter/references/references.xml#indien">In-<lb/>
diens</ref>.<lb/>
</ab>
</argument>
<p rend="margin-top: 0; margin-bottom: 0; text-indent: 0;">
deſquels ſont rentés, és autres, il faut<lb/>

3) Lines 10394-10406 (extra line break occurs between "des" and "Bra-" in XSLT):

<div>
<argument rend="float: left; margin-left: -5em; text-align: left;">
<ab rend="font-style: italic; font-size: 70%; text-align: left;">
Solenni<lb/>
tez au<lb/>
iour des<lb/>
nopces<lb/>
des <ref target="../../back_matter/references/references.xml#bracmane">Bra-<lb/>
mins</ref>.<lb/>
</ab>
</argument>
<p rend="margin-top: 0; margin-bottom: 0; text-indent: 0;">
ieunes,hommes & femmes: le iour<lb/>

4) Lines 10535-10544 (extra line break also occurs between "des" and "Bra-" in XSLT):

<div>
<argument rend="float: right; margin-right: 5em; text-align: left;">
<ab rend="font-style: italic; font-size: 70%; text-align: left;">
Femmes<lb/>
des <ref target="../../back_matter/references/references.xml#bracmane">Bra-<lb/>
mins</ref>.<lb/>
</ab>
</argument>
<p rend="margin-top: 0; margin-bottom: 0; text-indent: 0;">
quels couchent auec les ſœurs du<lb/>

1) Need MH to look at why all "ẽ" letters appear in bold in both the Forest nuptiale and in the Sonnet 1609 even though I didn't encode them as such. Strangely, all other letters with a tilde appear normally when viewing the texts online.

2) Also need to get MH to take a look at line 752 of the XML in the Sonnet 1609. For some reason, in the web version, the dotted page break line is pushed off further to the right.