1. Cross-references: I went back and checked cross-reference examples. There is no difference between a link introduced by xr ‘See’ and one introduced by ‘cf’. So the second cross-reference type should be re-encoded using an xr tag. Do you do this, Martin, or do I?

I don't think there's any way to do this programmatically, because the <note> elements which use "cf." are discursive; there's no way for any algorithm to parse them and figure out what entry is being referred to. So it's a markup task, and as such I think it falls to you. You can assign it to me if you'd prefer, but it will take me a while to get to it, and I'll probably just have to ask you what to do in each case.

There's a simple way to find all <note> elements containing the text "cf" in oXygen:

1. Open the XML markup file in oXygen.
2. In the top left of the screen, you'll see "XPath 1.0" or XPath 2.0". Use the dropdown list to select "2.0".
3. Type this into the text box next to it:

   //note[contains(., 'cf')]

4. Press Return.
5. You should see a list of items in at the bottom of the oXygen screen. Click on each one to show it in the editor.

Doing this shows 8 items in the affix.xml file, and none at all in the s-rtr.xml, c-rtr.xml or phar-w.xml files.

Incidentally, this raising a question from me: which files are "finished" to the point where they should be uploaded into the database?

2. Martin’s question about lack of documentation of phr type=”phonemic/narrow” which are found in dictegs: We discussed this in December. See Blog of 18/12/06 Decisions. In Kinkade’s database some of the illustrations are transcribed phonetically and some are transcribed phonemically. So we decided to add phr type=”phonemic/narrow” in order to allow for phonemicization of the dicteg forms when necessary.

Mea culpa, and thank god for the blog. I've now updated the documentation to reflect this. I've also done a quick update to the rendering code so these are rendered between slashes and square brackets as in the case of <seg> elements in the <pron>.