Hi Behdad Same problem Mathieu mentions is there with the combined Tibetan script mark characters U+0F73, U+0F76, U+0F77, U+0F78, U+0F79 & U+0F81. These need *decomposing* into two or more characters so that the individual glyph elements can be separately positioned above and below the base glyph which may consist of one or more consonants and so, in Tibetan, is of variable height. - Chris Behdad Esfahbod wrote: > On Sat, 2007-01-20 at 20:34 +0700, Mathieu Pellerin wrote: > >> Greetings, >> >> I was wondering if the Pango developers have an ETA on a >> yet-to-be-supported feature that, lacking the proper technical term, I >> would define as 'unicode combined char'. >> >> For example, the unicode character U+17FE, a Khmer vowel. You can >> reconstitute the vowel using two other unicode character (U+17C4 and >> U+17C7) hence me labeling it 'unicode combined char'. >> > > According to my Unicode 5.0 data files, there is no such character as U > +17FE. > > >> I'm not sure how it'd affect other languages, but for Khmer while it's >> not critical, it would certainly be a time saver. >> > > While Pango can be smarter about canonically equivalent Unicode > sequences, the fonts can help too, by correctly populating their 'ccmp' > OpenType feature. That currently doesn't work for Khmer though: > > http://bugzilla.gnome.org/show_bug.cgi?id=385168 > > If you let me know more about your situation (are you designing a font? > Did you really mean the nonexistent U+17FE? etc.) I may better help. > > >> Matt >> > > _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
