I've always been unhappy about the appearance of footnotes in the documents; the over-large "Note 1" headings seemed superfluous, but it's not easy to generate normal ordered lists from these because of the nature of the processing and the popping-up. I've now rewritten that code to produce something that looks much more like a normal ordered list, but still allows the nuber to be displayed when the note is copied into a popup box.
Finished marking up the second article, and also had to make some revisions to XSLT and CSS to handle some new issues thrown up by it:
- Templates for
<ref>elements can now handle linking between articles in the editorial collection, and handling of<ref>elements generally is slightly more robust. - Blockquotes are now correctly handled in the context of articles, including better margins when verse stanzas or lines are quoted.
- Popups (for notes, biblio refs etc.) now no longer have a min-height. I can't see why I gave them one originally, but it led to lots of empty space in the popup if the content was short.
On CC's instructions, fixed the dates of the Agremens texts, which were mostly wrong, and tweaked the Milan text. Also changed the display of document titles in the Teaser so that it's using the full title instead of the truncated title used in the TOC.
I've got a rudimentary (and buggy) map here: http://hcmc.uvic.ca/grs/map/
With Martin's help I got some ajax features working, but inexplicably, certain places "don't work". e.g. If you click on Troy you'll get the list of options. Click on Citations and you'll see a long list. Click on Tenedos - same thing. Now, click on most other places. Nothing. I run the query manually and it works. This way - nothing.
Can't complain. I've made some good progress in the last couple days.
Leanna and I finished scanning CO410 (V1), and CO410 (V2). We will tackle the RG series next week!
Left early.
I've been marking up the second article today, and have done most of it. In the process, I'm standardizing the markup practices, and I'll be in a position to document them in detail when I've finished and tested the document.
Things I have to remember:
- When @corresp is used to bracket multiple morpheme components for a single segment, the site needs to handle this. When you first click on the segment, it should expand into separate morpheme representations; then clicking on each of those should take you into the morpheme.
<bibl>elements need to be applied in many different locations, especially inside<def>and<form>, to make it absolutely clear what the source for each of them is. Right now, a<bibl>tends to appear in a<def>, and that actually means that it applies not only to the<def>'s parent<sense>element, but also to the preceding sibling<form>element. Since this is not reliably the case, though, we need to be explicit about it.
Ewa wrote yesterday:
Basically there are three crucial things to keep in mind when phonemicizing:
1. The “alphabet” is phonemic, so wherever a transcription deviates from the alphabet it is phonetic.
2. Raised vowels are schwas which are clearly phonetic in nature.
3. Schwas in general tend to be phonetic except for a few cases which are systematic. Only the latter kinds of schwas should be left in phonemic representations.
Took a slightly longer lunch than normal to go to the bank, but then an unexpected new db project took a couple of unplanned hours, so I ended up staying very late.