Pim Blokland asked as follows. quote
Now my suggestion was the browser program which displays this file should be able to look at the font information in the XML file, open the font file and retrieve the names of all characters in it, so it can show the "&hwesta;" character (and all other characters) without needing a long list of ENTITY entries in the XML. Anyone else think this would be a good idea? end quote Well, I think it would be a good idea. Could you explain it further please? For example, starting from a golden ligatures collection character ct ligature, which I have designated as U+E707 within the Private Use Area within the golden ligatures collection. Does this mean that for each Private Use Area item which I specify I would need to specify a single word name for use in such constructs? I am happy to do that, thinking that g_ct would be a suitable name for the golden ligatures ct item. I could fairly easily devise such names for most of the golden ligatures collection and with a little thought will hopefully be able to devise suitable names for the rest. Am I right in thinking that this system will only really work if the names are unique, so that if someone else devises a code for ct at some other code point then it is important that the name for that usage is other than g_ct or is it not essential, though just desirable, for the names to be unique? Can you possibly post an example of what files would need to carry which information please so that the g_ct name could be used in the manner which you suggest? William Overington 19 March 2003
