Re: ERB decisions on A.17, B.9, and other questions
> In the light of these agreements, the ERB reconfirmed its earlier
> decision that XML 1.0 will not have SDATA entities. It is thought that
> most uses of SDATA entities are adequately served by character
> references to Unicode characters (see example below). Techniques for
> dealing with non-Unicode characters, specification of glyphs rather than
> characters, and related topics (such as possible mechanisms for document
> private agreements governing the ISO 10646 Private Use Areas) will be
> addressed in future revisions.
Sorry to quote all that...
If I want to put my transcription of bits of Bailey's 18th C. dictionary
on the web (actually it's already there in fairly grotty SGML), I will
want to refer to some glyphs not in unicode.
Would I do
<!Entity tall-s "s">
and hope that a style sheet could map this to (say) the font
Adobe Caslon Alternates, using an embedded OpenType font?
HTML will let me do this next year, using MSIE or Netscape, according to
the respective vendors.
There are many other characters not (or not yet) in 10646 or Unicode,
some of which can be handled by floating diacriticals -- e.g. see
http://www.portal.ca/~tiro/ for an analysis of character sets required
for current, modern languages. There are others that are incorrectly
identified in Unicode (it was made by humans...).
In the case where no glyph exists on the targent system, I obviously
want something mnemonic to appear -- I can live with
but not with
or the equivalent
(ISO 10646 user space character numbers are all that long, right?)
As long as a mnemonic string is used, I don't care whether it is
called SDATA or PRISCILLA.... :-)