HCMC Blogs

This long-outstanding task is still waiting to be done. I worked through all the documents except the Varin, and was able to automate some of it by using regexes. There are some situations in which a <ref> and a correction coincide, where the consequences for rendering would be difficult to figure out, so in those cases I've left a note in place for the moment.

LB has integrated the new content into the WD Guidelines chapter, and I just did a final copyedit and added some tweaks.

Per decisions in the previous post:

• Appendix index entries now include all allomorphs.
• Where allomorphs have different feature structures (through <vAlt> elements in the <fs>), the prefixes and suffixes for affixation are now sensitive to those differences and supply the correct versions for each allomorph (this needs rigorous confirmation by ECH).

I've also done a considerable amount of cleanup of the rendering of all indexes, especially the root-based index, which had headwords hanging over into the page margin.

One outstanding question: the root-based index headwords do not include allomorphs right now. I think they probably shouldn't (it's cleaner and clearer without, and in any case you would most likely get to them from the main entries), but if we decide otherwise, all that needs to happen is that code from the fo_extra_indexes.xsl/outputExtraIndexEntry template would need to be imported into the fo_root_based_index.xsl/outputEntry template.

On late duty covering for JN; also trying to meet a submission deadline.

Deadline day: just got it finished a few hours ahead of the close. This was a re-working of the CodeSharing talk I did last year, with many improvements. In the process, I worked on some annoying bugs in the tei2odt conversion for JTEI, but mostly without success. I can't figure out why font settings don't work as I would expect them to.

We will be meeting with the Land Title Office staff, so we met today to prepare a list of questions relating to issues around granularity of properties, co-ownership, and various other thorny problems arising out of the data we already have.

We also talked about the handling of documentary data for the project as a whole, and our clusters in particular. The resulting plan is to get an unlimited account on Zotero for the first year, and see how that suits our needs. We will create a protocol which re-purposes some of the existing Zotero fields we don't need for things we do require that aren't covered (since Zotero doesn't allow custom fields). We will also put in place XML processing for XML output dumps of the Zotero db so that we can run validation and consistency checks on the data, and ensure errors are corrected. Finally, JS-R's existing document database will be exported as XML and turned into a format that Zotero can ingest; this will involve some detailed processing of citation information to create filepath-like string values representing the exact location of a document (archive/collection/box/file etc.). Using this system we will be able to reconstruct a tree-like view of the documents in their archives down the road.

Guenther Goerz has also created a Mac version of the Image Markup Tool using Wine Bottler (it's a large download). Download it from the IMT Downloads page.

BG recommended the use of MarcEdit to handle the binary Marc file, and it works a treat; downloaded the Linux-y distro, which is actually just the .NET version, but with some extras, and after installing the mono-complete package, this runs with mono MarcEdit.exe. It read the large binary file and was able to convert it into a larger XML file, which is a bit big for Oxygen to handle comfortably, but can be browsed, and will certainly be amenable to XQuerying in eXist.