SR is rebuilding the TEI deb now, presumably with an oXygen that has no JRE with it. I've removed the JRE in my Jenkins oXygen, and also placed a key file in the oXygen directory (which I hope will prevent it from trying to read /root/.com.oxygenxml to find the key). Running the stylesheetDocumentation.sh file at the command line now does not fail -- well, it does, but with an error about number of arguments required -- so I ran a test build of it through Jenkins to see if the actual thing worked, and the build did start successfully, but failed with what looks like an XSLT problem during a test. Waiting for feedback from SR about that.
May 11, 2011
Working at home on a personal project, I've found a bug in the way IMT handles the content of annotation titles (which are <head> elements). When reading <head> elements which contain mixed content, a space character preceding an element node is eliminated. I pinned it down and fixed it, and I've created a new release, but I'll test it at home before I release it finally.
K is sick, so DR asked me to upload and link a file directly. Did that on both the lang03 and paorweb accounts, to keep everything in sync.
May 10, 2011
Today's progress, with help from KSW:
- Made poster templates for portrait and landscape at 18x24.
- Changed out the page-images for the "What's in a Despatch" poster, because the original was actually an admiralty letter rather than a despatch. Re-labelled the new document.
- Resized the enumeration poster.
- Planned out the OAI generation poster.
From help I got from the oXygen forum, I've determined that the problem is that the JRE in the oXygen installation is 32-bit.
It was the teideb package repo that presumably gave me my oxygen install (I didn't do anything else to get oXygen installed). The package would seem to be:
tei-oxygen_12.1-tei1_all.deb
from here:
http://tei.oucs.ox.ac.uk/teideb/binary/
which contains a complete oXygen package (in data.tar.gz) which does indeed include a JRE.
I just moved the JRE elsewhere, so now it's presumably using the installed Sun Java. But I'm getting another error now:
using oXygen XML Editor stylesheet documentation generator.
Exception in thread "main" java.lang.ExceptionInInitializerError
at ro.sync.xsl.documentation.XSLStylesheetDocumentationGenerator.main(Unknown Source)
Caused by: java.lang.RuntimeException: The preferences directory: /root/.com.oxygenxml
cannot be accessed !/n Please check the read/write access on that folder and its ancestors !
There is no such directory, of course. The Jenkins process that's initiating the stylesheet script file is apparently running as root, so perhaps that's why it's looking there for preferences, but this is a headless server that doesn't need any GUI layout information. What would it be looking for in the preferences directory? I've posted for help on the oXygen forum.
If you want to use the KWIC module and specifically the kwic:summarize() function when performing full-text queries on your eXist databases, ensure that, if you have a default namespace declared, you negate that namespace in your <config> element:
declare default element namespace "http://www.tei-c.org/ns/1.0";
import module namespace kwic="http://exist-db.org/xquery/kwic";
for $result in collection('/db/francotoile/data')//tei:TEI/tei:text/tei:body[ft:query(.,"francophone")]
order by ft:score($result) descending
return
kwic:summarize($result, <config xmlns="" width="40"/>)
Note the xmlns="" attribute on the config element. Otherwise, kwic:summarize interprets the element as tei:config and throws an error.M called me over to deal with a frozen Windows VM, which had in turn frozen VirtualBox and eventually the whole machine. The VM was eating 4GB of memory. Tried restarting just the VM but it crashed again, so restarted the whole machine; that took a forced reboot because it wouldn't shut down. When we brought everything back up, there was no temporary nVivo file in the normal temp folder [user]\local\Application Data\temp, but there was a 4MB binary log file. On starting up nVivo again and trying to load the database, it complained that the original was corrupted, but offered to retrieve a cached copy; the binary log file then disappeared and the db was restored, so it looks as though it ran the log file against the original file and reconstructed all today's changes.
Note to Greg: nVivo's looking a bit unstable. We should look at extra backup options to give us more redundancy that we have.
Went through the process (with help from MH) of building a simple index using the Lucene text search engine for the FrancoToile rebuild:
<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://exist-db.org/collection-config/1.0" xmlns:tei="http://www.tei-c.org/ns/1.0">
<index>
<lucene>
<analyzer class="org.apache.lucene.analysis.standard.StandardAnalyzer"/>
<analyzer id="ws" class="org.apache.lucene.analysis.WhitespaceAnalyzer"/>
<text qname="tei:body" analyzer="ws">
<ignore qname="tei:note"/>
</text>
</lucene>
</index>
</collection>
The important notes are:
- You need to declare the namespaces you use in your documents in the <collection> element (e.g. xmlns:tei above)
- Use the full element names with namespaces when adding the indexes (e.g. tei:body)
Used these Exist docs as guides:
Met with PS and CC on May 11 to discuss the state of FrancoToile. All systems go; no bugs or issues to report. The completion of full English/French translations for all text on the site is ongoing. Other than that, no outstanding issues were noted.
Workstudy is done, so fewer timesheets now, but still three for Mariage RAs. Submitted today.