[cairo] About cairo_show_text and UTF-8...
behdad at cs.toronto.edu
Sun Jan 8 03:12:07 PST 2006
On Sat, 7 Jan 2006, Mike Emmel wrote:
> Cairo has the design that for each backend you provide a backend specific
> implementation I did not mean that fontconfig would be the solution on win32/mac
> just that for each platform or backend you may have a implementation
> specific to that solution. Pango provides a pluggable abstraction
> layer and is dependent on gobject mainly to support this abstraction
> layer and to provide plugabble renderers. This can be removed if you
> assume your working with a fixed implementation chosed at compile
> Internally in pango any particular implementation of the pango api is
> not that large.
Have you any proof that the pluggable architecture is making any
problems whatsoever? Is it just the glib dependency you are
> For cairo I'm saying it makes sense to extract these core
> implementation remove the gobject dependency and expose them as
> directly linkable libraries.
> Its already in pango just do a
> ls pangocairo* Once you make the PangoCairoRenderer a simple C struct
> and not replaceable then the gobject dependency is basically gone
> win32 vs fontconfig is already handled I guess ATSUI is not at least
> in the code I have.
The ATSUI stuff is already in CVS. Again, the question is: do
we want to duplicated/copy all the Pango functionality into
cairo? If we do, I'm sure we will get messages about ripping the
text stuff because "my application doesn't use the text api and
the implementation is god damn huge.." I'm really with not
extending the toy api at all.
> I worked on this already.
> > --behdad
> > http://behdad.org/
> > "Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
> > -- Dan Bern, "New American Language"
"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
-- Dan Bern, "New American Language"
More information about the cairo