Worked on a couple more things on KB's list of desirable fixes for the Keats site. Changed the style of a button, fixed some individual instances of oddities, and created an experimental replacement for the current image-only page banner, using a modified version of part of the image and incorporating text. Everything is tricky and mess because Dreamweaver.
Encoded the whole of the actual translation, mainly using s/r in gedit, because it's so well structured. Seems to be rendering well. Did a few more pages of the intro, and confirmed that there are no conventional endnotes; the Notes section is keyed to the stanza numbers.
listPers in the particDesc seems right as well.
I began looking at the code mapping for ligatures and other special characters. Not sure what exactly needs to happen there. Created a bash script that looks through the IML files to investigate how often that character is used; I couldn't use XSLT or anything like that since the ampersands, etc, are difficult to search with for text. I now have a script that lists the characters by number of use. It needs to be finished, however, so that we can see which files contain these characters and how we should work with them.Brief meeting, nothing to report. Added generation of AJAX fragments to the build process for people and places, and the people fragments are now used in generating the pages, which speeds it up a fraction.
For the new translation we definitely need the <caesura> element, so I have:
- Manually added the element to the RNG file which I'm now maintaining as the P4 schema.
- Added it to the content model of the
<l>element. - Added handling for it in the output to XHTML5 and PDF, and tested.
- Added handling for it in the P5 output, and tested.
Tweaked and improved my tagging tool JavaScript. This goes very smoothly nowadays.
Meetings meetings meetings.
Met with MT and JT. We established coding and documentation standards for XSLT, Schematron, and Ant (to some degree), and figured out how the ISE2, ISE3 and GitHub repos will relate to each other and to the Jenkins build. Documentation in Github repo.
Lots of details and a plan of action thrashed out; documentation in Google Drive docs.