HCMC Blogs

Tiny bug in the TEI Simple XSLT broke the build: LS used the @resp attribute on <soCalled>, which is a nice idea and makes perfect sense, but which the simple code wasn't expecting. Took a while to narrow it down, but it was an easy fix.

Wrote the Endings proposal JT and I planned out the other day and submitted it to JADH.

Dental appt in the morning.

The diagnostics is now showing lots of errors in filenames and links, so I've handled the bulk of them in a semi-automated way because they were amenable to that. We're now down to 64 bad filenames and 4 bad links.

I've made the updates to the database, by rsyncing most of the dev version over the live codebase (keeping a backup).

The changes are:

1. There's now a "First Line" field in the Poems table, where you can add the first line of a poem which otherwise would be indistinguishable from others with similar titles ("Song", "Sonnet" etc.).
2. The "Related poems" field now uses a combination of the Title, the First line (if there is one), and the id of a poem to give you something which (I hope) is findable and unique for each poem. When poems start with punctuation (quotes or whatever) they'll sort to the beginning, so you usually need to scroll past the quoted titles to get to the regular ones.
3. There is now a publicly-accessible read-only view of the database here. I haven't linked this from anywhere or publicized it yet; I think the plan is to hide the notes field in this view, which will take a bit of work.

One note: there's an additional field in the poems table which just amalgamates all the text values of the other major fields, to make for a simple search field, which was used for the WordPress plugin. Since that's no longer working, and it was going to be difficult to combine the trigger I needed for the new First line field with the original trigger that also ran on update on that table, I've removed the original trigger. That means the plugin will no longer work, so if we need it to do so at some point, we'll need to figure out how to combine those two triggers in a single operation.

Editor packages are working well now on my machine and the instruction documents are starting to come together. We need to start testing cross-platform, which is the next step.

Lots of work done today on editor packages in oXygen. I've now put the schematron within the ODD file, have it building out in the proper files (thanks to MH's code), and have a nice validation suite working. In data/tools/, there's a file called "validate.html"; editors can open it up, press the play button, and all of their files are validated.

I've modified MH's process schematron code slightly so that it doesn't fail immediately if it finds an error; it compiles all the errors first and prints out the message, and then fails. I like this a bit more, since I would likely use this code when debugging/testing the ODD, etc, and it's nice to see all the errors all at once.

The setup and updating builds are both working nicely; still not cross-OS compatible, but otherwise they're nearly ready to be used, I think. However, the committing stuff is melting my brain. I've looked at both svnant (http://subclipse.tigris.org/svnant.html) and svntask, and tried nearly everything I could find online, but nothing seems to work. More work to be done there.

Edit: I was misspelling the variable (I was passing ${password} and not ${pwd}). A very silly mistake, which I will chalk up to the combination of travel, conferencing, and sun over the last few days.

Trying to get diagnostics working well for DVPP.

Did a set of reviews which were due immediately. :-)

We now have diagnostics giving stats, and providing tests for ill-formed image filenames on the filesystem, and database records that point at images that aren't there. This is a good start, and there's plenty for people to get their teeth into.