Devonshire

Worked on the rendering of the apparatus, specifically on the showing of the relevant line in a popup, with the lemma highlighted:

• Modified poem.xsl so that it makes the lemma into a link which calls a JavaScript function.
• Wrote JavaScript to find the relevant line.
• Wrote functions to render out the text of the line, ready for highlighting.
• Added a function to highlight any instances of the lemma in the line, then pop up the rendered line on the right of the screen.
• Added CSS as appropriate (will need some tweaking for subtlety).
• Tested.

Everything works, except that:

• Sometimes there's a lemma which is not quite the same as the line, or portion of it. See LDev005 line 17 for an example. In this case, nothing is highlighted. That might be OK.
• Sometimes there are elements in the line which shouldn't be part of the popup, such as notes or figures. These need to be suppressed. See LDev005 line 31 for an example.

Adding this as a task so that I get the above two things looked at before my vacation.

Met with the ETCL folks, and got the following requests for fixes/changes/new features in the critical apparatus output:

• Sigla in the crit app should be clickable, leading to (or popping up) a proper MS description. This will be based on a mapping XML file for all the witnesses which Karin will supply.
• All readings from the same line should be displayed (initially at least) in one block, separated by a space 5ems wide, to conform with traditional practice. This should be switchable, though, because we have no space limitations and can give readers the option to see each item on a separate line if they wish.
• The user should be able to switch on orthographic variants, which are currently invisible.
• Instead of the word "Omitted", we should use "omit." in italics.
• Clicking on the line number should pop up a copy of the base text line, with the lemma highlighted (if possible -- this might be done with JavaScript).
• Karin needs to be a user in the DB, with permissions on the Devonshire collections, so she can upload apparatus files while I'm away.

Adding this as a task.

First, install and test the app to see if it's stable and reliable (Cara reports inconsistent results on her tests). The docs make it look fairly straightforward; Stew and I had a look at it today, and read through all the Help.

If it works OK, go to the source code and see if it's going to be possible to extend it to make it produce output in TEI format.

These issues are relevant to me:

• Spaces between stanzas will be denoted using the <space> tag instead of using notes, as they currently are. This will have the effect of removing many notes which are currently cluttering up the apparatus.
• The rend attribute will be rationalized, and the range of its values reduced. For now, one thing I should do is to write my code so that it ignores all varieties of "smcap", but doubles the font size for "lgcap". Adding this as a task to make that happen.
• The type attribute on <div> tags will be rationalized, so that all poem-type divs will have a value beginning with poem_. Other values for type will be collective, which is the main container div for all the poems, notation, which will be for inline comments (usually in another hand), and notation_marginal, which is for marginalia. The last two should show up as children of a poem div, so they will need to be rendered by my code in some way.
• Trailers will be encoded using <trailer> or <closer> tags, and my code will have to render these too as part of rendering poems.
• People will be listed in a <particDesc> element in the <profileDesc>, as a <listPerson>. Each <person> tag will be linked to one or more online sources (the DNB or LOC) using an <ident> tag, distinguished by type="DNB" etc. Karin will create this list of people, and I'll pull relevant items from it to place in the XML document for each individual poem, and render the info into the apparatus.

Posting minutes spent discussing and documenting this.

In IE7, the popup div appears above where it should. IE's interpretation of offsetTop seems to differ from everyone else's. That'll need a fix, and while I'm doing that I can add the fix for the popup scrolling off the bottom of the page, which will also require some browser-specific code, I think.

We should by now have good TEI collation info; the next stage is to render it out to the document.

Focus on the CSS with Karin, and make sure the whole site looks good. Create a logo. Here's a suggestion: use a collage of characters cut out from the MS itself to create the title "The Devonshire Manuscript". This would represent the fact that the MS itself is a collage of contributions, and at the same time would give a period feel to the site.

Before we get too close to the deadline (April 26), we need to have Ray look at what's been done so far and ensure it meets his requirements. Do that, and get any required fixes done before proceeding.

There are two types of metadata that need to be displayed: that for individual poems, and that for the MS as a whole. The latter is simpler, in that it can be a separate view/page linked from the TOC, so do that first. The former may be slightly more difficult, because it has to be incorporated somehow into the existing poem display page.

NOTE: This task rescheduled because updated MS transcription is not yet available for me to work on.

Elaborate the basic display framework to make the display usable. Use classes for everything, so that Karin can work on the appearance of the site independently using CSS. Use only one CSS file for the whole site. Where elements have ids, carry them through to the XHTML output, and where they don't, but it might be useful (such as individual lines that we might need to jump to), create ids. The texts are relatively short, so we can pack in a lot of useful detail.

Then look at the possibility of making the two scrolling boxes capable of controlling each other through script, so that what's showing in one could cause the other to jump to a linked location if the user wants it to. For instance, a note about line 15 of the text could cause the text to move to line 15. This is not a requirement, but if it turns out to be simple, it should be incorporated.

Create the following components of the site:

1. An Index page listing all the poems, with links to an XHTML rendering.
2. A basic XHTML rendering of individual poems, comprising two boxes, one with apparatus and one with the text, scrolling independently.

No detail is to be included at this stage; we just want the basic framework to be working.

Create a Cocoon/eXist environment for the project, a basic front page with a menu, and links to two views (old/Unicode and modern/normalized) of the newly-Unicodized XML displayed with CSS.

COMPLETED TASK: Work through the RET documentation and list all the special characters we need to document. Then work with Karin to find, for each character, a Unicode representation as close as possible to the original glyph(s) (if one is available), and a detailed description of the script feature itself. Format these as a feature structure list.