TE is working on the elimination of unnecessary hi elements, as a first (although pretty hard) XSLT project. Spent some time discussing approaches, and she had it working by the end of the day. Fixed the calendarDesc issue in simplePrint output (using settingDesc -- ugly but meh). Also fixed all instances of style attributes lacking a trailing semicolon, and implemented Schematron to prevent further instances. Lots of discussion of how to rework the teiHeader and split Stow.
Since most of our work is now being documented in Asana rather than here, I'm just posting hours spent over the past couple of days of version 6.4 changes, discussions of changes to the teiHeader, build process rationalization, and a variety of other things.
Following a successful release earlier in the week, we're now able to undertake more significant structural changes to the repo and the build process. The first one, done today, was to split out the news page into separate articles, deal with the fallout, and add documentation.
Bug found in modern map functionality, and new errors introduced into Stow and PERS1 by the checking process itself. Now postponed to Friday.
Release day didn't happen due to some last-minute glitches, so it's now been rescheduled, and a comprehensive release plan has been put together in Asana to avoid the stumbles that happened today. We all learned a lot, and it'll go well when we come to do it again in a couple of weeks. Fixed a lot of minor issues and polished off a couple of tickets.
Fixing a bunch of typos and slight annoyances; building out some changes to the home page per PS.
Like MH, spent most of the day fixing CSS syntax errors. I decided to write a process that goes at the beginning of the validation build that creates a bunch of small CSS files for validation against the VNU; each separate node becomes a CSS stylesheet, with the node's XPath is embedded within the filename. The errors are then parsed by an XSLT that also retrieves the node that contains the error and then outputs a message and breaks the build.
Plan of attack going forward, I think, will be to create a new validation process that will be the automatic transformation scenario for each TEI file. It will:
- Validate the file(s) against the RNG
- Validate the file(s) against the Schematron
- Check for duplicate ids
- Validate embedded CSS (if any)
- Maybe run some common diagnostics (ref/name/bibl stuff, perhaps).