Met with JJ to discuss glyph encoding and came up with a fairly robust course of action for encoding. While most glyphs are fairly simple (long S) there are instances of combining characters (y + (e|u|t) above) and we assume there will be similarly difficult glyphs.

We divided the problem into four parts:

1. How to encode in the charDecl

   • JT will discuss with MH and SA about the best strategy, based off of some of the work MH + SA have done for LOI.

2. How to encode in the text itself (i.e. what should the @xml:id of the glyph be)

   • We think yUAbove, yTAbove et cetera would suffice and is easily readable by encoders etc

3. What to put in the glyph tag

   • There are a few options: 1) Nothing; 2) the literal character [which is what we've been doing so far, but may not suffice for characters in future]; 3) a normalized version of the string (i.e. yu); 4) A regularized version of what the character represents (thou).
   • JJ and JT think (4) is the best approach as it will help for future searching and indexing; it is basically a short form of using choice and friends.

4. How to process and render:

   • This will come later, but basically, if we decide to use a regularized string, we can either replace the string with its regularized format (or make that an option) or display the character as best we can with the full-featured font that we use.

To do: JT will discuss some of the various encoding solutions with MH and SA; once decisions are made, JT will implement.