Helped on this, as I wrote the original PHP to retrieve and display the calendar feeds.
September 11, 2008
After the character set issues were sorted out, I started working on the Documents tab functionality. This will work as a kind of baby version of the main Inscriptions tab, because it has multiple fields of different kinds. I have about half of its functionality working: the top three button controls enable and disable appropriately, the New button clears out the form elements ready for a new record, the Edit button retrieves and populates the controls with the selected item data from the db, and the Delete button successfully deletes records from the db.
The remaining functionality is saving back to the db, and then the rather complicated tracking of when and if a record has been modified in the GUI, so that we can figure out whether the Save button should be enabled, and when we need to warn the user about discarding changes.
Added structures for sessionals and grad students similar to that of professors section of french site. Updated pages with links to the newly created pages. Content to be added by dept using their normal practices.
My test page for processing the rss feed from the UVic events calendar was failing. Turns out that the output formerly included a "calendar=" attribute in the link item, and now includes a "cal=" attribute; also, the output formerly escaped ampersands and now doesn't. My code in rssReader2.php had to be modified to accommodate those two changes and now it works again. I'm now in a position to start work on the scraper for the French dept site (virtually identical to the GRS scraper) and for the Dean's site (considerably more complex, having to accumulate lists for a number of departments by straight date and by department, then date.
The problem reported by SB appears to be caused by the wysiyg editor in their admin interface turning certain characters into html entities, and then the rss feeder is escaping those again so that external listeners get a double-escaped entity, producing the problem. My test also showed that copying and pasting from Word into the wysisyg editor by-and-large works, but introduces spurious nbsp entities, so one should use the "paste from word" feature in the editor.
Link: http://www.digital-scholarship.org/sepb/sepb.html
Version 73 of the Scholarly Electronic Publishing Bibliography is now available from Digital Scholarship. This selective bibliography presents over 3,350 articles, books, and other printed and electronic sources that are useful in understanding scholarly electronic publishing efforts on the Internet.
http://www.digital-scholarship.org/sepb/sepb.html
The Scholarly Electronic Publishing Bibliography: 2007 Annual Edition (PDF file) is also available.
http://www.digital-scholarship.org/sepb/annual/annual.htm
For a discussion of the numerous changes in my digital publications since my resignation from the University of Houston Libraries (http://tinyurl.com/6xkcvs), see:
http://www.digital-scholarship.org/cwb/dsoverview.htm
FromCharles W. Bailey, Jr. Publisher, Digital Scholarship
Link: http://www.mith2.umd.edu/dh09/
Alliance of Digital Humanities Organizations
Digital Humanities 2009
Call for Papers
Hosted by the Maryland institute of Technology in the Humanities (MITH) University of Maryland, College Park, USA
22-25 June, 2009
http://www.mith2.umd.edu/dh09/
Abstract Deadline: October 31, 2008 (Midnight GMT)
Presentations can include:
•- Single papers (abstract max of 1500 words)
- • Multiple paper sessions (overview max of 500 words)
- • Posters (abstract max of 1500 words)
From today's indispensible Humanist listserv, a posting by Dr John Lavagnino, Senior Lecturer in Humanities Computing, Centre for Computing in the Humanities, King's College London, about the appearance of simple text-analysis political sites like Speechwars in the US, analysing candidates' utterances.
I have XHTML pages in UTF-8, with forms in UTF-8, submitting to a database whose tables/fields are all in UTF-8, and I'm retrieving data from it and sending it back from PHP to the AJAX machinery with a header that specifies UTF-8. AND YET I was getting garbage (question marks) for non-ASCII characters. Why?
mySQL needs to be told explicitly to output data as UTF-8. You do it like this, in PHP, after making the connection:
mysql_query( "SET NAMES 'utf8' " );
45 minutes wasted on this, so I'm blogging it for the next person who's tearing their hair out over it.
Yesterday and today, had meetings with CC and the two new research assistants, introducing them to the project and the materials, and getting preferences and desktop setups organized for them. We'll have them both working on Sonnet de Courval, with SW working on the 1609 (which we'll treat as the base text), and PG working on the 1621. SW can do the base line numbering as a simple progression, and then PG can add line numbers later based on the 1609 lines, with additional lines sub-numbered (exact scheme still to be worked out).