To: unicode(at)unicode.org
From: Bob_Hallissy(at)sil.org
Received: (qmail 13977 invoked by uid 0); 14 Jul 2003 12:04:30 -0000

from unicode.org (209.235.17.55) by ns.need.bg with SMTP; 14 Jul 2003 
12:04:30 -0000

from sarasvati.unicode.org (localhost.localdomain [127.0.0.1]) 
by unicode.org (8.11.6/8.11.6) with ESMTP id h6EBuEP17808; Mon, 14 
Jul 2003 07:56:14 -0400

with ECARTIS (v1.0.0; list unicode); Mon, 14 Jul 2003 07:56:14 -0400
 (EDT)

from smtp.jaars.org (smtp.jaars.org [208.145.81.51]) by unicode.org 
(8.11.6/8.11.6) with ESMTP id h6EBuCP17802 for ; Mon, 14 Jul 2003 
07:56:14 -0400

from dfwcom.sil.org (philippi.dallas.sil.org [172.20.1.21]) by 
smtp.jaars.org (8.12.8/8.12.8) with ESMTP id h6EBu0AY023170 for ; 
Mon, 14 Jul 2003 07:56:04 -0400
Date: Mon, 14 Jul 2003 06:55:59 -0500
MIMEVersion: 1.0
ContentType: multipart/alternative; boundary==_alternative 
0041799B80256D63_=
Subject: Re: Combining diacriticals and Cyrillic
Body: 

On 14/07/2003 11:10:35 Peter Kirk wrote:



>But one part of it might be rescued, if I understand rendering
>technologies correctly. Internally within a font only, Vladimir may
>define glyphs for his precomposed characters and assign PUA code points
>to them. In fact this seems to be how MS deals with some Hebrew
>presentation forms (ones which aren't in FB1D-FB4F) in Times New Roman.
>Then it can be part of the rendering technology Vladimir uses to
>substitute for the standard Unicode for his letter-accent combinations
>the PUA codes for the precomposed glyphs. For example, on a Microsoft
>system this may be included in an OpenType table, and Uniscribe (but
>only the soon to be released version which can process Cyrillic text)
>will perform the required glyph substitution. 

None of the modern rendering technologies (OpenType, Graphite, AAT) 
require that PUA (or any other) code points be assigned to such 
precomposed glyphs.



Bob