Met with Ewa, and we made the following decisions:

1. We'll use the comma-above rather than the hook-above, because community-friendly forms are more important than strict phonetic accuracy.
2. All entries will have a form/pron/seg element with the attribute type="phonemic", which will be the first pron in the form element, and will constitute the phonemic/orthographic form which is displayed, and on which people will search.
3. The search system will allow the use of all characters in the phonemic/orthographic markup, as well as plain-ascii versions of the entries (=phon/orth minus diacritics).
4. We will try to generate the plain ascii versions for searching automatically, or (even better) find a way to configure searching so that it can do fuzzy matching against diacritic-free versions.
5. The dicteg elements will need rewriting. This is what one currently looks like:

   <dicteg type="narrow">
   <cit>
   <quote>[blah]<gloss>He hasn't eaten.</gloss>
   </quote>
   <bibl>W2.72</bibl>
   </cit>
   </dicteg>

   The target form looks like this:

   <dicteg>
   <cit>
   <quote>
   <phr type="phonemic">[blah]</phr>
   <phr type="narrow">[blah]</phr>
   <gloss>He hasn't eaten.</gloss>
   </quote>
   <bibl>W2.72</bibl>
   </cit>
   </dicteg>

   This will make for a more community-friendly display, and mean that we can search the examples in the same way as we search the entries.