Spent most of the day reading through SF tracker items in preparation for the Paris meeting. Also put the P5 source into an instance of eXist so I can query it with XQuery, and used that to prepare a summary of one issue (@usage="mwa|rwa"), which is up for discussion. Also did some travel planning (getting from the airport to the hotel, etc.).
November 2, 2011
Carol from Sociology asked if it was possible to export data from the Agenda list view to an excel spreadsheet. There is no built-in feature, but the data is in an html table, so you can simply copy and the table data and you get tab delimited fields and return delimited records on the clipboard, which you then simply paste into the spreadsheet.
I tested copying and pasting from the timetable view and while all the cells and data are successfully copied, there is a problem because in the html table there are rowspans (e.g. for time blocks that take 90 minutes span 3 30 minute rows) and those are not reproduced in the spreadsheet. The data for a 90 minute block appears in the first row and the two rows below are empty. So it would take a fair bit of manual styling of the spreadsheet to reproduce the look of the html table.
Hist dept noted that in the New Offering form the prompt for the sequence details said "Sequence
One (Fall term)" no matter what term had been selected in the Term control above. I modified the load_creation_area.php file in the agenda instance in lang to change that text to "Sequence Details" (as the "One" only makes sense if they've selected the Full-Year term, which has two sequences. I also added two elements "seq_1_detail_subhead" and "seq_2_detail_subhead" and modified the files common_scripts.js and agenda.css so that the subheads appear only if the user has selected "Y" as the course term. seq_1_detail subhead contains "(Fall sequence for full-year course)<br />" and seq_2_detail_subhead contains "(Spring sequence for full-year course)<br />.
...from Megapode.
November 1, 2011
Hoping to leave on time, but a series of help requests from RAs kept me engaged.
These two blocks of XQuery will search for page-image links in the header <biblScope> and in <pb> tags and report any that don't match the expected pattern. That doesn't mean they're bad, just that they need checking.
header <biblScope>s:
xquery version "1.0";
declare default element namespace "http://www.tei-c.org/ns/1.0";
for $b in //biblScope[@type="startPageImage"]
let $bits := tokenize($b/@facs, "/")
where not(starts-with($bits[2], $bits[1]))
or not(matches($b/@facs, '((co)|(rg7))_((g8c)|([0-9]{1,3}))_[0-9]{2,2}/((co)|(rg7))_((g8c)|([0-9]{1,3}))_[0-9]{2,2}_[0-9]{5,5}[rv].jpg'))
return (xs:string($b/ancestor::TEI/@xml:id), $b)
<pb> tags in the body:
xquery version "1.0";
declare default element namespace "http://www.tei-c.org/ns/1.0";
for $pb in //pb[@n]
let $bits := tokenize($pb/@n, "/")
where not(starts-with($bits[2], $bits[1]))
or not(matches($pb/@n, '((co)|(rg7))_((g8c)|([0-9]{1,3}))_[0-9]{2,2}/((co)|(rg7))_((g8c)|([0-9]{1,3}))_[0-9]{2,2}_[0-9]{5,5}[rv].jpg'))
return (xs:string($pb/ancestor::TEI/@xml:id), $pb)
There's a problem with the display of the chapter heading "Le traictement de la femme nouuellement accouchee, & tout le temps de ſa couche" (c.50.p.845) in the Maladies des femmes table of contents. There is a break between "tout" and "le" but there shouldn't be one.
EDIT by MDH: This appears to have solved itself, or to have been solved by a previous fix. There's no break I can see. It's possible to make lines break by setting very large text in a narrow browser window, but that's preferable to having the text disappear or intrude into another block of text.
Fixed a bug with page number positioning by re-working some of the margins on the various types of <fw>. Changes documented in CSS file.
This bug proved to be a bug in Firefox so it's now closed.
<g> elements were previously only handled when they occurred within <abbr> tags, but they do occur elsewhere, so I've now added a new handler which shows their character description as a mouseover popup wherever they show up. The original handler for <xsl:template match="choice[child::abbr[descendant::g] and child::expan]"> has also been tweaked so that it more clearly distinguishes between the expansion of the abbreviation, and the explanation of the one or more gaiji characters which appear in it.