Permalink 08:59:08 am, by mholmes, 233 words, 6 views   English (CA)
Categories: Activity log; Mins. worked: 45

Root-based index sort order

SK reported an issue with the sort order of entries in the root-based index. I dug into it, and discovered: The main Moses-to-English entries appear to be sorted in the correct order. First a sort key is created like this:

<xsl:variable name="sortKey" select="if (descendant::orth) then normalize-space(descendant::orth[1]) else normalize-space(string-join(for $s in descendant::pron[seg[@type='p']]/descendant::seg[@type='p'] return hcmc:createOrth($s), ''))"/>

In other words, if there's an orth it uses the orth, and if not, it creates an orth from all the descendant phonemic prons. Then it sorts the entries using the orthographic collation:

<xsl:sort select="@sortKey" collation="http://saxon.sf.net/collation?class=ca.uvic.hcmc.moses.MosesOrthographyCollation"/>

When it comes to processing the root-based index, we were doing something slightly different:

<xsl:sort select="if (descendant::orth) then descendant::orth[1] else hcmc:createOrth(descendant::pron[seg[@type='p']][1]/descendant::seg[@type='p'][1])" collation="http://saxon.sf.net/collation?class=ca.uvic.hcmc.moses.MosesPhonemicCollation"/>

In other words, we were using the Phonemic collation. I can't remember when/where/why we have both phonemic and orthographic collations -- there must have been a reason -- but I've now switched the root-based index sort so that it uses the orthographic one. That appears to fix the problem, but SK will check for any unwanted fallout.


Permalink 04:06:04 pm, by mholmes, 12 words, 15 views   English (CA)
Categories: Activity log; Mins. worked: 120

Meeting and rewrite of presentation slides

Discussed our first draft at length, and I then rewrote my slides.


Permalink 04:34:26 pm, by mholmes, 24 words, 23 views   English (CA)
Categories: Activity log; Mins. worked: 30

Tweak to order of root-based index component sorting

Per SK, switched the order of two morphemes and rebuilt the PDF. Took a while to figure out where to make the change, though.


Permalink 04:59:26 pm, by mholmes, 81 words, 179 views   English (CA)
Categories: Activity log; Mins. worked: 45

Worked with SK on diagnostics code to replace old Python stuff

ED's convoluted Python/NTLK stuff for diagnostics just doesn't work on the new Jenkins server, and in any case it seems, as we look at it, that it could perfectly well have been done in XSLT, so SK and I have made a start on figuring out how it works and converting it. It'll take a while, but lesson learned -- don't let people use stuff just because they like it, keep the range of tech limited for any given project.


Permalink 02:55:55 pm, by mholmes, 63 words, 89 views   English (CA)
Categories: Activity log; Mins. worked: 20

Added diagnostics build scenario to XPR file

So that ECH can work remotely without needing a network connections, we've added a build scenario for the diagnostics to the Oxygen project file, so that running the default scenario on any XML document actually runs the diagnostic process. It takes nearly ten minutes, but it's still a bit quicker than waiting for Jenkins and it can be done without a network connection.


Permalink 05:13:53 pm, by mholmes, 16 words, 88 views   English (CA)
Categories: Activity log; Mins. worked: 120

Meeting with app developer

Met with AP, linguist and app developer, and shared ideas on dictionary interfaces, data-entry, and outputs.


Permalink 12:32:37 pm, by mholmes, 106 words, 108 views   English (CA)
Categories: Activity log; Mins. worked: 120

Ant task to build the PDF

Our PDF build is dependent on XEP, which is installed on my desktop, so up to now I've needed to be here to build it (since it was a scenario run from inside Oxygen). I've now converted this into an ant task which can be run remotely at the command line. Lesson learned at some cost of time: you can't use this:

  <arg value="-fo ${foFile}"/>

Instead, you have to use this:

  <arg line="-fo ${foFile}"/>

Otherwise XEP doesn't find the FO file, and assumes the fo is coming from stdin; it then complains that the root element is not fo:root.


Permalink 10:52:01 pm, by jtakeda, 15 words, 109 views   English (CA)
Categories: Activity log; Mins. worked: 60


With ED and SK, porting over diagnostics that are now cleared into schematron where possible.


Permalink 05:21:53 pm, by jtakeda, 17 words, 120 views   English (CA)
Categories: Activity log; Mins. worked: 30

SVN conflict resolution

Working with the Moses team to help resolve a conflict in SVN and helping E with XSLT.


Permalink 02:01:20 pm, by jtakeda, 64 words, 128 views   English (CA)
Categories: Activity log; Mins. worked: 45

Created metadata.xml

Attempted to run the improved Endings diagnostics code against Moses and realized that the "psn" and "m" prefix weren't defined whatsoever. After consulting with MH, SK, and ED, I created metadata.xml and defined the prefixes as best as I could. This put up a few errors with psn pointers; I fixed what I could and then added a diagnostics to the Moses build.

:: Next Page >>

Nxaʔamxcín (Moses) Dictionary Blog

This is an XML dictionary project based primarily on the materials compiled by the late M. Dale Kinkade during fifteen years of work in the 1960’s and 1970’s with more than a dozen native speakers of the language, but it also includes materials compiled by Ewa Czaykowska-Higgins in the early 1990’s.


XML Feeds