All HCMC Blogs

I just finished my touch-up the Fantastique and Purgatoire texts. I mostly included CC's footnotes, but I made some other (very minor) formatting changes, going from the updated Word documents of the two texts she sent in October. First off, concerning the Fantastique:

• I added the <figDesc> that CC had on her transcription of the title page.
• I added in the "S. l. n. d. In-8." that came below the title, but I wasn't sure how to mark it up (because I don't exactly know 100% what it is!!), so I put it for now as a .
• In note 4, there is some italicized text, but I'm not sure why it's italicized -- I used <soCalled> and <mentioned> tags where I deemed it appropriate given the context, but I'm still not 100% sure. I also forget at the moment if these produce guillemets or if they make the text italic in the way that the <foreign> tag has been programmed to in the schema. I will do a search in the site and hopefully I'll get some answers. If <soCalled> and <mentioned> tags DO produce guillemets, what how should I mark up these italicized words? (I think this is a question for MH).
• I added in CC's footnotes as well, which was kind of the main point. Just thought I'd say.
• I also changed the page number format according to current practice (MH and I discussed this a few weeks ago). There were no <fw type="pageNum"> tags -- instead, only <pb n="x"> tags, which MH explained were problematic in that the "actual" page numbers can be a bit of a grey area, so we've been marking simply <pb/> to signify a page break and then the page number itself is a part of <fw> (formworks). So I changed this in the Fantastique.

And as for the Purgatoire...

• I added in CC's <figDesc>, as for the Fantastique.
• I also changed the <pb n="x"> to the combination of <pb/> and <fw type="pageNum" place="top-(left or right)" rend="float: (left or right)">.
• I added in the docDate in roman numerals, as shown on CC's recent transcription, but there's also this In-* thing after it and once again, I ended up using because I'm not sure what it is!
• QUESTION: If there's a note within one of these works that's attributing information to a source, e.g. Virgil's Aeneid, would I mark this up as a <title level="m"> since it involves bibliographical information? This is what I have done in the Purgatoire.
• Once again, I'm not sure if I'm using the <mentioned> and <slCalled> tags I'm using are appropriate. MH, I think I might need you to check this in both texts.
• I also italicized the bibliographical attributions that were within the text itself (e.g. the anonymous author puts books by Saint Basil in brackets after certain things he/she says) -- I marked these up also as <title level="m"> because I consider them to be bibliographical information again.
• This becomes a problem, potentially, when it comes to books from the Bible being put in brackets, as the author italicizes them. MH, I remember our conversation about not italicizing books from the Bible in regular circumstances, but I marked these up as <title level="m">s as well due to their italicization in the transcription.

... thoughts? suggestions?

I captured Leiter and exported it. Started to capture Konstan. Started to transcribe Feeney.

Taking a day to try to get these hours down.

Trying to keep steady progress with ScanCan and the Mariage article markup, while at the same time troubleshooting new problems with the eXist 1.4 RC build (had to do a new build with the final/stable release, for deployment on Monday).

Converted my project to a runnable application (not easy -- had to manually edit manifest.mf, specify the main class, etc.; best to start with a Java app target if that's what you want to end up with). Now it will zip and return the size of a string on the command line; I'll add NCD from the command line next.

I have caught up to Loring's work on the first wave of 1849 XML files, and I tuned up some placenames toward the day's end.

Starting Monday, Loring and I will engage the system we discussed for the remainder of 1849. I predict that we should be able to complete 1849 by next Thursday.

I've now marked up five pages of Corps des époux, and encountered more new features to document:

• The text requires linking to specific locations in texts in the anthology; in the cases I met today, these were page references inside Choliere (which is still not really in a state to be up on the server -- that's another matter). There was no way of doing this, but I've created one today: ever <fw> tag which is @type="pageNum" or @type="folioNum" generates an XHTML @id attribute generated from its content, so you can now write a link like this:

  <ref target="xhtml.xq?id=choliere#p_82">

  to link to page 82 of the Choliere. This will only work if there is such an <fw> tag in the XML, and in cases where there are duplicate page numbers (as in the Amboise), only the first instance will get an id. Older and smaller documents that don't have explicit <fw> tags usually have a <pb n="xx> formulation, and these will not get ids and not be linkable. It may be that we therefore want to go back and mark up those documents appropriately; but if they're short it doesn't really matter, and if they're long, they're most likely going to get reworked anyway.
• Blockquotes are common and some have biblio references at the end of them:

            <cit rend="block">
              <quote>
                Si toutes nos fringuantes, qui ont si grande envie de sçavoir aux despens de leur pucellage que c’est de s’acoupler avec le masle, estoient assubietties à la rigueur d’une telle loy … i’en tiens la plus-part si doüillettes qu’elles aimeroient mieux estre filles toute leur vie, qu’avec une si mal plaisante ceremonie commencer leurs nopçages… 
              </quote>
              <bibl>(<ref target="xhtml.xq?id=choliere#p_83">p. 83</ref>)</bibl>
            </cit>
            
  

We also have a potential collision between our editorial notes and footnotes in original texts (the Cabinet Satyrique is the main case). After some discussion, I've changed editorial notes so that they show up looking like little buttons, leading to a popup, whereas original footnotes should be encoded in-place, as they originally looked (at the bottom of the page where they appear). The Fantastique Repentir will be the test case for this.

Changes haven't yet been migrated to the server, because it's a bit fragile; I have a brand-new stack for Mariage built with 1.4 stable, with a couple of extra tweaks, which I'm planning to deploy on Monday.

The eXist db now seems to require a full re-index whenever you upload files into it; they don't get properly indexed just through the upload process. My guess is that this is because we actually deployed a pre-release version, and there were some tweaks after it was fully released. My plan now is to build a new version with the Cocoon/eXist package I built on Monday for MJ, test that locally and then replace the server copy with it. I also want to make a further change to conf.xml, through my build script, as follows:

<db-connection cacheSize="48M" collectionCache="24M" database="native"
        files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="-1">

becomes

<db-connection cacheSize="48M" collectionCache="24M" database="native"
        files="webapp/WEB-INF/data" pageSize="4096" nodesBuffer="1000">

With the setting at -1, the system consumes all available memory when doing indexing; with it set to 1000, it keeps only 1000 nodes in memory at a time, leaving memory free for other threads.

This article's biblio has 52 items(!). Marked up 28 so far.

Got interested in making some Java stuff work properly -- I'm porting the USM code from Delphi to Java. Not immediately needed by anything, but ultimately required by Mariage and for DH 2010 (if accepted). I want to do little and often to maintain familiarity with the code.