[webkit-efl] Dropping support for the pango network backend.

[ryuan Choi]

It's good news.
When it is available, I think that we can try to move to harfbuzz.

But I just want to know who want pango backend.
Default font backend of webkit-efl is freetype and tizen also use it (with
FontPango.cpp)

If it is not used and maintained well, I want to create new bug for
dropping pango backend from webkit-efl port.

As separated issue, Bug 83275 is to mix backends like you mentioned.
But I am little bit confused because webkit-gtk is similar.
And although we get harfbuzz, I am not sure that we can move to it
immediately.
We may keep the freetype backend until tizen is moved.

Best Regards,
Ryuan Choi


2012/5/16 Dominik Röttsches <dominik.rottsches at intel.com>

>  Hi Ryuan,
>
>
> On 05/15/2012 10:22 AM, ryuan Choi wrote:
>
> We've supported freetype and pango backend as font backend of webkit-efl.
>
> However, pango backend can not render well because of missing features and
> webkit-efl builds with freetype by default.
> Does anyone need pango backend?
> If possible, I will remove font backend selection checks and just use
> freetype backend with FontPango.cpp for the complex font.
>
> Related bug is https://bugs.webkit.org/show_bug.cgi?id=86369
>
>
> I remember Martin Robinson prefers to not mix those backends and wait for
> his HarfBuzz support to be merged. I asked him on IRC and he has a
> preliminary patch that he's planning to upstream soon. See also
> https://bugs.webkit.org/show_bug.cgi?id=83275
>
> Dominik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-efl/attachments/20120517/cd329011/attachment.html>