Mariage

Started working on the Complaintes text:

• Went through the header and reformatted, adding various bits and pieces our practices require, and reworking other bits (creating a full <biblStruct>, for instance, and adding the <textClass>).
• Added XSLT and CSS handlers for the <sp> and <speaker> tags. This is currently rudimentary, but basically working.
• Noticed that the markup seems to be based on CC's transcription, meaning that it doesn't necessarily reflect the original document (and we don't seem to have any scans or PDF). This means that (for instance) all page numbers were originally put on the left, even on a recto; this I've fixed, guessing that odd page numbers would be right-aligned, but there's no way to check that.
• Also it looks as though LCC has included linebreaks based on the DOC transcription, but those linebreaks may well be just artifacts of the wrapping in the DOC file; we need to clarify this.

Pulled down the image markup CC has been editing, and checked them over; I found a couple of bits where there were invalid constructions, chiefly due to <choice> elements being inserted inside linegroups (<lg>) but outside their line (<l>) tags. Fixed those, and validated all the files, then uploaded the changes into the database.

I'm in the process of doing modern transcription for all of the text on the engravings, which is going quickly and will be finished by the time I leave for France. I am also reviewing all of the other annotations on the engravings.

There is an issue with linking text and images: to which versions, orignal and/or modern? Martin and I decided that keeping the links in the original exclusively makes sense. After her writes some new code (January term), I will review all of the links on the site, and no doubt introduce some new ones.

According to my notes on the 1623 version of the "Satyre ménippée", we are missing just a page or two at the end from the Bnf's pdf file. (Compare to 1608.) I should be able to either photograph or transcribe these pages as a priority on September 4, before the Bnf's annual two-week closure.

Ok, so, M., all of the references should be working now in the Varin (although some of them might not point to anything other than an 'a venir' reference because I have not been able to find reliable information yet on them. I am also hoping to go through the Varin again and proof some extra stuff (e.g. small caps instead of all large caps, commas with spaces in front of them or no spaces after them, etc), so hopefully I can do this when you're done proofing Varin. After that, it's just re-proofing Candale and continuing to proof Isembourg.

CC has created a new category for transcriptions:

<rendition xml:id="Transcription_moderne">
  <desc>transcriptional</desc>
  <label>Transcription en français moderne</label>
  <code rend="rectangle" lang="text/css">color: #ffffff</code></rendition>

I've now added that to all the remaining files she hasn't edited yet, using a search-and-replace.

Okay, so now I've realized that I was getting perhaps a bit ahead of myself these last few days starting my work on the Agremens. Looking at EM's Isembourg xml I realized that she'd added a few details that I had not thought to add into my part of the Isembourg and that would also be useful in the Candale. I have decided upon a New Order of Things for my work. This week, I will:

1. Proof EM's portion of the Isembourg.
2. Incorporate EM's extra details e.g. attributes on said tags into my part of the Isembourg.
3. Return to Candale and complete the references and alter some of the figures, said tags, etc.

Next week I plan on resuming work on the Agremens. Sorry for any delay because I really want to have the Agremens up (rough form) before I leave for Europe if at all possible, but it's a matter of quality of my xml over quantity, and I think the details EM has incorporated into her section of the Isembourg are very relevant and apply nicely to my Candale as well.

Started checking the Varin XML file. The XML was valid, but the XHTML output showed 72 validation errors. These were a couple of the causes I found and fixed:

• The XQuery that bundles the reference <div>s from references.xml into the document XML file before rendering includes one reference <div> for each distinct-value of ref/@target, selecting the <div> by using the section of the @target following the hash to find the div/@xml:id. If, therefore, the portion of the @target attribute preceding the hash is wrong, then two copies of the same reference <div> may be retrieved -- for instance, if there is <ref target="refefences.xml#blah"> and <ref target="references.xml#blah">, there will be two instances of the <div xml:id="blah"> in the output, an error which will be flagged by the W3C HTML validator. This amounts to an integrity check which throws up lots of typos in the target attribute, and I fixed many of those in the original XML.
• In references.xml, the <list> element is used with @type="bulleted" and without an @type attribute value, neither of which situations was allowed for by my XSLT, which expects @type="unordered" for an unordered list. Rather than rewrite the XML, I tweaked my XSLT to output all TEI <list> elements whose @type attribute is not equal to "ordered" as XHTML <ul> elements.

I also ran some XQuery to find a list of all <ref> tags whose @target doesn't match an existing element in the references.xml file, for whatever reason, and sent that to LCC for her to check through the list, fix typos, and put in empty reference <div> elements in the references file for any missing items.

1) Added

<lg rend="text-indent: 1em; font-style: italic; margin-top: 0; margin-bottom: 0">

to lines 3423, 3431, 3450 3499. Thankfully, no validation errors occurred this time. I'll have to wait until MH updates my changes to see if they actually appear correctly on the site.

2) When looking at the sonnet on the mariage site, I found text-indents before each drop-cap in lines 3523, 3575, 3627, 3643, 3667 and 3683 even though this was not encoded. MH suggested that I replace the <lb/> tags preceding

<hi rend="float: left; font-size: 300%; margin: 0; padding: 0; line-height: 90%; font-style: normal;">

to <lg> tags to fix the problem.

Uploaded the latest 1609 Sonnet, and then validated the HTML (not the XML, which is fine). There were three errors, which I worked through and fixed:

• There was a <fw> (page number 7) tag inside a <head> element, which is fine in TEI but ends up generating a <div> inside an <h2> in the HTML. I think the page number actually belongs outside the <head> tag anyway, so I've just moved it one level up into the containing (TEI) <div>, which solves the problem.
• The page 11 number had the same problem, fixed in the same way.
• My decision yesterday to include the <figure> element inside the <l> element to handle a floating image alongside the run of lines resulted in a <div> inside a <span>, which is of course silly. Since it's pretty clear that the only place to put the <figure> tag is inside the <l> element, because the TEI schema precludes its appearing between line elements in a line-group, and in this case the line-group is clearly coherent (in other words we can't close the <lg> and open a new one to allow a place for the <figure> tag), I need to change my rendering code so that the <figure> tag doesn't come out as a <div> in this context. I found I had already added a similar exception to handle figure elements inside head tags, so I added another clause to deal with this situation. The HTML now validates, and I've uploaded my changes to the xml file to the server location for LSPW.