HCMC Blogs

I've discovered the problem with the mysteriously rebooting machines. I had a complete build working perfectly with USB sticks, then I installed the Ghost client as the last step. Instantly recreated the problem with the first insertion of a thumb drive. I found references, and tracked down a Symantec support doc here which offers a new version of ghmon.sys, which I've zipped and uploaded (couldn't upload a .sys file) here.

Took off early.

The title problem is actually in the title bar of the thumbnail window; when the titles of engravings or texts are long, they wrap too many times and the gradient fill graphic isn't large enough to fill the title bar area, resulting in unfilled bands under the title. "Fixed" this by changing the XSLT to invoke the truncation template so that long titles are truncated for the thumbnail window, just like they are for the document list. Tested on a range of browsers - seems OK, unless you make your font size so large that the same problem occurs even with short titles.

In the process of working through the files detailed in the previous post, I made the following changes to the Apparatus app:

Added some proper error handling for the condition where the template.xml file is not found. Previously, this would prevent the app from saving data, but now it can just save a text file in place of the full XML file, so there's less risk of data loss if the template file is missing.

Built a manifest file to include version info in the package. However, I'm not sure whether this is done correctly, and whether it's actually working. The info on this is sparse.

Tested on Ubuntu again, just to make sure the app remains portable after recent rebuilding of the GUI.

Today's progress, on the LDev003 and LDev004 files:

1. Re-generated them from the Collate files with my application, which fixed the problems caused by commas vs semicolons etc.
2. Categorized all the readings using my app -- that works fine. I've followed the categorizations Cara added last time around.
3. Worked through Cara's comments in the original files, and fixed remaining problems where I could.
4. Added comments for all items I'm not sure about, or where there needs to be further input from Cara and/or Ray.

Sent the results to Cara, with explanation, and the following notes:

One fairly common problem relates to additions in the witnesses. The word "added" is often, but what that means is not usually clear. For example:

Perhaps the "addition" is actually an addition in the witness (which should be tagged with an <add> tag), or simply a word which exists in the witness but not in the base text (in which case it should just be in the reading). For instance, if the base text has this:

    one three

and the witness has this:

    one two three

then the app tag should look like this:

    <app>
        <lem>one three</lem>
        <rdg>one two three</rdg>
    </app>

although it could also look like this:

    <app>
        <lem>one</lem>
        <rdg>one two</rdg>
    </app>

or this:

    <app>
        <lem>three</lem>
        <rdg>two three</rdg>
    </app>

The main point is that there must be enough in the <lem> tag to show where the extra bit in the witness actually shows up.

However, if the witness itself has "two" in the form of a scribal addition, then the app tag should look like this:

    <app>
        <lem>one three</lem>
        <rdg>one <add>two</add> three</rdg>
    </app>

Does that make sense? I've tended to use the <add> tag, especially where you mentioned using it, but I suspect that usually we're not dealing with additions in the witnesses, we're dealing with bits of text that show up in the witnesses but not in the base text -- not the same thing at all.

I think these files are close enough for me to use as the basis for writing XSLT/output code for the Web view of the MS, though, so I'll start on that next week.

I tested the fix further and discovered that the results from a search are as quoted below. So, I pass "true" instead of "false" for the last parameter and predictably the apostrophes now appear as entities, but the search works.

Error Code: 4096
Error Message: Object of class DOMDocument could not be converted to string
File: /home1t/florevid/www/includes/helpers/ajax_search.php
Line: 58

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home1t/florevid/www/includes/helpers/ajax_search.php:47) in /home1t/florevid/www/includes/classes/session.php on line 13

Fatal error: Call to a member function GetVariable() on a non-object in /home1t/florevid/www/includes/classes/lang.php on line 26

Could you tell me what's incorrect about those document titles? The site is just using the titles from the documents themselves, truncated so the page displays in a usable manner. Quite a while ago we discussed the possibility that you might add short-and-user-friendly titles for each of the documents (with regularized capitalization), but that's not been done yet, so we're stuck with the title as it is in the document. Some of them are virtually of paragraph length, so of course they have to be truncated for the purposes of the document listing. If that's all the problem is, then all we need to do is get you to add a new display title to each document. If there are typos of some kind in the titles themselves, then you just need to fix the XML code in the documents.

Planned to leave early, but ended up doing a workshop in a DHSI session...