[cairo] Serious concerns about cairo

[James Cloos]

>>>>> "Mike" == Mike Emmel <mike.emmel at gmail.com> writes:
>>>>> "Bill" == Bill Spitzak <spitzak at d2.com> writes:

Mike> Add drawing operations at least for ucs2 chars. No one doing
Mike> advanced text layout works with utf8 you can't internally.

Bill> Please don't use "wide characters" in the api. The sooner we
Bill> stamp this abonimation out, the better.

Mostly agreed.  Cairo should use utf8.  (In general, though, utf32
is not so abominable.  That 16 bit nonsense, OTOH, ....)

(And, one should note, glibc uses int32_t for wide chars; ie utf32
rather than that utf16 junk.)

Bill> Finding the next glyph means looking for the next byte that
Bill> does not start with 10.

s/byte/octet and, most importantly, s/next glyph/next code point/

As Bill mentions later, not all code points are glyphs.  There are
combining characters, variation selectors, joiner characters, etc.

In short, if your working with the UCS you need to think in terms
of character sequences rather than in terms of characters.

-JimC
-- 
James Cloos <cloos at jhcloos.com>         OpenPGP: 0xED7DAEA6