This currently:
More will come, including hopefully a build of the PDF, but that will require some decisions about where our copy of XEP is to live.
Got a spreadsheet of revised material description info from Nanaimo last week; I've now processed this with XSLT into SQL statements and used it to update the db.
On late duty.
I now have an ant build file written, which grabs the XML dump from the db, processes it into the simpler XML my existing code is used to working with, and builds the Streets HTML file. It also validates all the existing XML before starting, something which threw up some horrible invalidities. There's a bunch of encoding that took place on the Haney prose data which abandoned our schema entirely and went for tei_all, which obviously caused much markup drift; I've now incorporated the needs of that encoding into our schema. The existing directory files also had lots of problems, so I've tightened up the schema and fixed those; everything now validates. I need to build a lot more Schematron into the ODD file.
But now we're good to go on building stuff like diagnostic checks and generational suggestions into the build process.
Consolidated an article from copyediting for the authors to do final revisions.
Met with LB and MN to discuss overhaul of the Wheelock Latin site. Conclusions:
Fixed a huge number of errors in the source XML, and added some pre-processing to fix many of them. Set up three levels of validation for the incoming XML and the generated XML as part of the build process, and then started hacking away at the remaining errors in the HTML output. What's left, as far as I can see, is just the problem of milestone elements showing up as direct children of e.g. list elements. That's on the table to be fixed next week.
Assisted SB with editing faculty page; publishing
Website in progress.
Sent update to SA, MH
After some investigation, I found that the best option for validating XHTML5 is not the RNC schemas from whattf, which depend on datatype definitions in their own namespace that I can't seem to find a jar implementation of; instead, the VNU project provides a single JAR file which can do it. I've integrated that into the project and I'm now doing validation of XHTML5 pages produced by the build.
Two sets of errors were easily fixed: first, the encoders seem to have been making up language codes as they went along, so there were hundreds of invented ones. I've fixed all those. Second, the files are not in Unicode NFC. I have XSLT to fix that in the XML, but I haven't run it yet; instead, I built normalization into the pre-processing of the XML, which solves the problem for the XHTML output, and also protects against bad data coming in in the future. But I will fix the normalization in the source XML files soon.
What's left is about 1100 errors of the expected type (divs inside spans and the like), each of which will have to be looked at in the hope that generic fixes that cover lots of them can be found. Meanwhile, validation of XHTML5 is now a solved problem, very usefully, and I'll be able to port this fix to other contexts. I don't know if I can find a way to make it validate all the fragment files, though. One option there would be to build them all into a single file, validate that, and then delete it.