>From an implementation perspective, it is generally easiest to add it (and
>maybe its presentation forms) into the Private Use Area. Otherwise some
>language-specific processing might have to be done if Uighur Heh is
>represented as U+0647.
The fundamental question is whether to encode distinctions to be made
during the rendering process. A smart font could easily distinguish these
behaviors without code distinction as long as either a language or font
binding were present (in the case of mixed Arabic/Uighur text), or simply
use one default behavior for mono-lingual Uighur text.
A more apt question might be whether there are informational reasons
to unify the two for performing other operations such as searching,
lexical analysis, etc.
G.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:31 EDT