Re: Creating a new back-end for Pango
- From: Behdad Esfahbod <behdad behdad org>
- To: James Hu <jamesyjhu gmail com>
- Cc: gtk-i18n-list gnome org
- Subject: Re: Creating a new back-end for Pango
- Date: Wed, 05 Aug 2009 14:44:07 -0400
On 08/05/2009 02:30 PM, James Hu wrote:
Hi,
As UIFont is only a subset of Cocoa Text, it does not contain any of the
advanced text layout capabilities available in Pango. The next best
thing below UIFont is very simple glyph displaying in Core
Graphics/Quartz, and can't be used for displaying anything but the most
basic latin scripts. Thanks again!
-James Hu
Doesn't the new iPhone support Arabic?
Anyway, if you need builtin shaping from Pango, you then have to build with
the FreeType backend. Right now, that's the only way you can get Pango to
shape (instead of delegating to the native system, which you don't have).
That said, we are separating the shapers from the FreeType backend though, so
in a couple of months you'll be able to use them with any backend you want.
They are OpenType shapers though. No AAT.
behdad
On Wed, Aug 5, 2009 at 10:26 AM, Behdad Esfahbod <behdad behdad org
<mailto:behdad behdad org>> wrote:
On 08/03/2009 01:51 PM, James Hu wrote:
Hi,
I'm trying to port Pango to the iPhone. The iPhone doesn't have
ATSUI,
but instead uses UIFont, which is a subset of the OS X's Cocoa Text
system. And due to iPhone's memory size restraints, I'm trying
to avoid
including Cairo into the mix and draw directly with Core
Graphics (which
is what Cairo uses anyways).
Why would you want to use Pango then?
behdad
Do you guys have any pointers on what classes need subclassing,
and what
hooks are available in Pango to include a new backend? Any help
would be
much appreciated. Thanks!
-James Hu
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]