From: Kent Karlsson (kentk@cs.chalmers.se)
Date: Tue Nov 11 2003 - 18:30:56 EST
Jill Ramonsky wrote:
I infer some confusion among contributors to this thread, some of whom
are
still talking to me as though I'm only interested in a sort algorithm
and nothing else.
No, but it has been the only reasonable issue that has come up in this
entire discussion.
Ken Whistler wrote:
You could, of course, avoid this problem if the "DIGIT COMBINING
LIGATURE" were
actually just a visible symbol, rather than an invisible format control
that would have
dubious support in most platform software. For example, you could simply
make use
of an existing symbol and *define* it to be your {digit combining
ligature} symbol.
Thus, for "2F", you could have, e.g.:
21¤5
where ¤ is defined as a digit composition operator,
Maybe COMBINING DOUBLE BREVE would be a more expected choice
of duodigit composer, and the normal display would be just fine.
(As I mentioned, ordering rules can be made to handle that with
a suitable prehandling and a suitable tailoring, using existing
tailoring
mechanisms for the latter. One could instead build this directly into
the key calculation, but that goes outside of what 14651 says.)
/kent k
This archive was generated by hypermail 2.1.5 : Tue Nov 11 2003 - 19:21:45 EST