That makes nine with last week's half-finished one. They'll need quite a lot of cleanup too. That's a priority for next week. They're appropriately named, and in the "incoming" folder. Three are pairs in the same image, and will need to be split.
Category: "Activity log"
January 31, 2011
The Subversion rollout is working well. GBS is now using it, and CC has been set up on Carrot with it (although isn't editing XML right now). Only LCC left.
This was generating sporadic errors because it was attempting to use a variable defined in another stylesheet, which wasn't included.
This reminded me, though, that references to other references (nested refs) don't work in the references page itself. That needs fixing. It may be as simple as including the popup on that page, but it might be more complicated.
January 27, 2011
RES-Z-1746-P-114.jpg arrived. I've made a start on cleaning it up, then I'll build the other sizes and the XML file.
We're now working out of a subversion repository instead of editing XML directly in home1t; this is basically essential since we have five or more people editing files in the same collection. I've set up LSPW and EGB on their editing machines with subversion and instructions, and all seems to be going well. I've also set up Radish so that it's ready for GBS when she comes in on Monday. I haven't yet set up the Mac for LCC.
January 26, 2011
Some texts (such as Varin) have quotes in them which are not signalled with quote marks; it's only clear they're quotes because of the surrounding text. These are being tagged with <quote type="noMarks">, which I've added to the schema alongside @type="italics", and added a handler to the XSLT.
The two latest texts have long and detailed tables of contents which need to be encoded. This is the recommended approach, which I've based on the Brown Women Writers Project guidelines, but which use examples from our own texts.
- The TOC as a whole is encoded as
<div type="contents">. - The main heading for the whole TOC is encoded as a
<head>element. - The TOC may then be divided into several sections (as in Le Bon Mariage), or it may be a single section (as in the case of the Ville-Thierry text). Each section should be encoded as a
<list type="toc">. - If a section of the table has its own subheader (as in the case of Le Bon Mariage), this should be included in a
<head>tag inside the<list>tag. - Each item in the TOC will be an
<item>element inside the<list>element. - Each item may contain three elements:
<label>(containing a label such as "Chap. XXXII" in the Ville-Thierry, if there is one).<rs>("referring string"), which contains the chapter title, heading or description.<ref type="pageNum">, containing the page number. This will have two other attributes:target="p_1"(which points, in this example, to page 1 of the text). It is important that you later ensure that an element with the xml:id "p_1" exists in the document; normally this would be the<fw type="pageNum">1</fw>-- in other words, the<fw>tag which contains the page number "1".rend="float:right". This designates that the page number appears on the right of the page, which is normally the case.
Here are some example encodings. This is from Le Bon Mariage:
<div type="contents"> <head> <figure><figDesc>Motif décoratif</figDesc></figure> <hi>TABLE</hi><lb/> <hi>DES CHAPITRES</hi><lb/> <hi>CONTENVS EN CE LIVRE</hi><lb/> </head> <list type="toc"> <head> <figure><figDesc>Ligne droite ray/e</figDesc></figure> <hi>LIVRE PREMIER.</hi><lb/> <hi>TRAITE PREMIER.</hi><lb/> <hi>De l'excellence & des fins du Mariage</hi><lb/> </head> <item> <rs>Des trois diverſes eſtats qui ſe retrouuent en l'Egliſe, page </rs> <ref type="pagenum" target="#p_1" rend="float: right;">1</ref> </item> <item> <rs>Combien le mariage eſt honorable. </rs> <ref type="pagenum" target="#p_6" rend="float: right;">6</ref> </item> <item> <rs>Qu'au mariage & en toutes autres actions ſe ſaut propoſer vne bonne fin.</rs> <ref type="pagenum" target="#p_10" rend="float: right;">10</ref> </item> </list> </div>
This example comes from the Ville-Thierry:
<div type="contents"> <head> <figure> <figDesc>Motif décoratif</figDesc> </figure> <hi>TABLE</hi><lb/> <hi>DES CHAPITRES.</hi><lb/> <figure><figDesc>Ligne droite foncée</figDesc></figure> <hi>CHAPITRE PREMIER.</hi><lb/></head> <list type="toc"> <item> <rs>De la grandeur & de l'excellence du Mariage. pag.</rs> <ref target="#p_1">1</ref> </item> <item> <label>Chap. II.</label> <rs>Qu'il n'y a rien de plus mal- heureux que l'état de ceux qui entrent mal dans le Mariage , & qui ne s'y con- duisent pas par les regles de la charité & de la pieté chrétienne.</rs> <ref target="#p_19">19</ref> </item> <item> <label>Chap. III.</label> <rs>Quelles sont les fins que les Chrétiens doivent se proposer , lorsqu'ils s'engagent dans le Mariage.</rs> <ref target="#p_26">26</ref></item> </list> </div>
January 20, 2011
There were some oddities in the display of references linked from inside references -- see my prior post for details. I've now fixed those. The problems arose because:
- When a reference was linked from inside another reference, it wasn't necessarily already in the page, because only references linked directly from the text are pulled into the document initially. That meant it had to be retrieved by AJAX.
- When it was retrieved by AJAX, it was a fragment rather than a full document; that meant that a lot of the context which was used by XSL matching templates was absent, so a lot of the styling was not applied.
- When the reference was retrieved, it was supposed to be added to the list of existing references. However, it replaced them instead, meaning that all subsequent reference links had to retrieve their references anew -- and they then inherited the style problems described above.
I've now fixed this so that the transformation XSL is more sensitive to fragments (it uses a formula local-name(/*) ne 'TEI' to identify a fragment, which is typically rooted on <div> rather than <TEI>). I've also tweaked the AJAX code so that it can append to the content of the target element as well as replace it, using a switch called clearTargetFirst.
January 19, 2011
CC sent the last of the metadata, plus a transcription. It's now up on the site, but it will be annotated further by CC.
January 18, 2011
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.