Philosophy ready to make the site Judy has been working on live.
Moved dev site from www-dev folder to www folder.
Current site is in web folder, so made copy of that for archive.
Contacted sys-admins to get web.uvic.ca/philosophy pointing at www folder and not web folder in their account.
I forgot to activate the redirect on the index.php page in the root of the new site, until reminded by sys admin guy when he activated new URL.
March 30, 2010
DL sent floor plan of proposed space and furniture in TEF. I asked her to reduce bookcases by one and increase bookable workstations by one. Also asked her what we're to do with stuff that we aren't taking with us to TEF (leave alone, label, move to corner?)
modified .htaccess file in restricted access folder in philosophy site based on requests from department
Greg and Martin working out what to do with the servers in B006 and our switch next door. After discussion back and forth and meeting with sys admins, it looks like we'll be taking Rutabaga and our switch with us for the move and putting the four servers primarily supporting ETCL work in the care of the sys admins.
I got confirmation of move date from Dawn and Greg will let the systems people know so they can move the servers and switch at the same time.
The Jar Bundler application includes an executable file JavaApplicationStub. The versions I have of Jar Bundler created a version of that file that either was PPC-only, or supposedly binary but defaulted to PPC. Problem is that in current release of Mac OS 10.6.2 the default is to disable "Rosetta" the code that allows ppc-apps to run on the intel chipset. User sees a "this application requires Rosetta to run, do you want me to enable Rosetta" message.
I found a page on the web that explained how to replace the version of the JavaApplicationStub created by my version of Jar Bundler with another version of that file and it would default to the intel chipset and failing that use PPC. Tested it and it works.
http://neosmart.net/blog/2009/make-old-java-applications-fully-snow-leopard-compatible/
Did most of this work out-of-office but posting here in case something similar comes up with university work.
BI wanted images of the appropriate flag (British, French, Russian) to appear depending on the language selected.
I added a class attribute
<h3><a title="English" href="?lang=english"><img src="images/en.gif" alt="UK flag icon" class="english" /> English</a></h3>
<h3><a title="Français" href="?lang=french"><img src="images/fr.gif" alt="French flag icon" class="french" /> Français</a></h3>
<h3><a title="Русский" href="?lang=russian"><img src="images/ru.gif" alt="Russian flag icon" class="russian" /> Русский</a></h3>
There's already a javascript method display_language_elements(show_language) invoked on page load which hides and shows elements based on their class attribute. Also had to add a float right css rule to ensure the images appeared on right edge.
Half of meeting was presentation by fund raiser and Centre for Religion in Society head on issues involved in creating a similar kind of centre for digital humanities.
Ray and I will likely be addressing next faculty meeting on procedure for proposals involving HCMC resources (people or equipment).
March 29, 2010
We are currently using <angle brackets> to denote a gloss supplied by Ewa
or other editors, rather than by the fluent speaker who actually uttered the Nxa'amxcin example. For example:
hə̣́ll
hə̣́ll ECH
hə̣́lə̣l Y39.109
√hə̣́l-C₂
lazy; <tired>
Y39.109
This indicates that speaker Y glossed this word "lazy", but the editors would also like it to appear in the English-Nxa'amxcin word list under "tired".
However, Martin noted that the angle brackets "amount to an alternative markup system, bypassing the XML, so it's definitely not ideal -- it will make it
difficult to find those particular items, or style them in a particular
way. They should be tagged in the proper way at some point."
So we need to figure out how best to tag them. I suggested we could mark them all with <bibl>ECH</bibl>, but we don't actually want these glosses to appear on the database website. We just want them to be searchable when we're creating the word list.
So this is another issue to be sorted out when we next pick up the project.
Leaving early for appointment.
JS-R called to say he wanted to order the documents by id, and to show the actual filenames of the pdfs etc. rather than the attachment icon. Made those changes in his codebase.