From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Fri, 19 May 2006 15:36:01 +0100 From: rog@vitanuova.com To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Subject: [9fans] combining characters Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 5202b850-ead1-11e9-9d60-3106f5b1d025 erik wrote: > rob has suggested passing uncomposed characters to libdraw and handling > the problem there. but there's one problem with that. how do you stic= k > a nonspacing horn onto an arbitrary letter? how do you put a grave acc= ent > on top of that? (transliterations of cryllic to the roman alphabet use= some=20 > double- and triple- accented letters which do not exist in precombined = form > within unicode.) perhaps there are actually two problems here: 1) how to get libdraw to map back from a sequence of combining characters to a character in the font that represents that sequence. 2) how to draw sequences of combining characters that don't exist in prec= ombined form within unicode. it's quite possible that one might wish to provide pre-rendered glyphs for some of these sequences - the current font format can't deal with that. another issue is dealing with code (e.g. libframe) that assumes that characters do not overstrike - i.e. that there's a 1-1 correspondence between Runes and glyphs. yet another is how one should deal with character-based indexing, for ins= tance indexing in sam expressions - does /=C3=A9/-#0+#1 point to the character = after the unadorned e, or after the whole sequence? it'd be nice to sort this issue out properly; surely it shouldn't be too hard?