Re: [ft] Glyph issue in freetype 2.3.10

[suzuki toshiya]

Hi,

The improvement in freetype, not Pango? I recommend to migrate
freetype-2.4.4 which was just released yesterday. In any releases
of freetype, the changes are summarized in freetype-2.x.y/docs/CHANGES.
The remarkable changes since freetype-2.3.x to freetype-2.4.4 are:
* genuine TrueType hinter is enabled by default, because its patent
  is expired.
* many vulnerabilities (some of them could be security issues of
  arbitrary code injection & compromising the application by the
  malicious fonts) are fixed.
* 64bit platform support is improved.
Unfortunately, I'm not sure if there is any rasterizer performance
improvement. Werner, if you know anything, please let me know.

--

BTW, I heard that GTK 3 will drop DirectFB backend.
http://mail.gnome.org/archives/gtk-devel-list/2010-August/msg00096.html
http://mail.gnome.org/archives/gtk-devel-list/2010-August/msg00224.html
Is there any candidates for you to migrate from GTK/DirectFB?

Regards,
mpsuzuki

Manoj Kumar Bhatta wrote:
> Hi,
> 
> If you do not mind, could you please tell me what are improvements  of
> freetype 2.3.7 to 2.3.10/11 ?
> Any performance improvement,if so how to measure ?
> 
> Thanks,
> Manoj
> 
> 2010/12/2 suzuki toshiya <address@hidden>:
>> Haha, I was feeling the version of Pango was slightly too old
>> and thinking about how to encourage you to update newer revision.
>>
>> Regards,
>> mpsuzuki
>>
>> Manoj Kumar Bhatta wrote:
>>>>> I'm afraid something wrong in Pango, and it
>>>>> might be long-term issue to analize why this trouble
>>>>> occurs.
>>> I have updated Pango library from 1.22.1 to 2.18.0 and the problem solved 
>>> !!!
>>> Now I can see arabic/indic properly.
>>>
>>> Thanks for your help.
>>>
>>>
>>> On Mon, Nov 29, 2010 at 5:45 PM, Manoj Kumar Bhatta <address@hidden> wrote:
>>>>> I'm afraid something wrong in Pango, and it
>>>>> might be long-term issue to analize why this trouble
>>>>> occurs.
>>>> I also think,there may be problem with pango/pangoft2.
>>>> But I have no clues now where is the problem exactly.
>>>>
>>>>> OK, please tell me the versions of component softwares:
>>>>> GLib, Cairo and Pango, and configuration options you used
>>>> Software and its versions.
>>>>
>>>> GLib: 1.17.6 ( config with  --with-libiconv
>>>> --enable-iconv-cache--disable-selinux  --disable-fam --disable-xattr )
>>>>
>>>> Cairo: 1.8.10 ( config with --enable-directfb=yes --enable-xcb=no
>>>> --without-x --disable-xlib --disable-xlib-xrender  --disable-win32
>>>> --disable-pdf --disable-ps --disable-svg --enable-png )
>>>>
>>>> Pango: 1.22.1 ( config with  --without-x )
>>>>
>>>> Though, I have updated cairo-1.10.0. But did not work.
>>>>
>>>> -Manoj
>>>>
>>>> On Mon, Nov 29, 2010 at 3:49 PM,  <address@hidden> wrote:
>>>>> Hi,
>>>>>
>>>>> Thank you very much for screen shots. Apparently,
>>>>> there is shaping error, the enclosing vowel signs
>>>>> are not reordered to form correct ligature.
>>>>>
>>>>> However, unfortunately, I (and maybe Werner too) have
>>>>> no candidates in my mind about the root causing this
>>>>> error. I'm afraid something wrong in Pango, and it
>>>>> might be long-term issue to analize why this trouble
>>>>> occurs.
>>>>>
>>>>> On Mon, 29 Nov 2010 13:17:15 +0530
>>>>> Manoj Kumar Bhatta <address@hidden> wrote:
>>>>>
>>>>>>> 1) how many prebuilt libraries in your DirectFB/GTK?
>>>>>>>   a) all are prebuilt by external developer (e.g. some Linux 
>>>>>>> distributors)
>>>>>>>   b) all, except of freetype-2.3.10
>>>>>>>   c) all, except of previous freetype-2.3.9 & current 2.3.10.
>>>>>>>   d) other combinations
>>>>>> We have built all the libraries from its source.( including DirectFB
>>>>>> to freetype)
>>>>>> We built freetype 2.3.9 and freetype 2.3.10 to check the issue.
>>>>> OK, please tell me the versions of component softwares:
>>>>> GLib, Cairo and Pango, and configuration options you used
>>>>> (if you have any account to a web server with huge storage,
>>>>>  I want to obtain your building directory of the components).
>>>>>
>>>>> I will make a modified Pango showing many many debugging
>>>>> messages, to trace its Indic shaper behaviour. Maybe using
>>>>> "pango-view" is sufficient to check the shaper's behaviour.
>>>>>
>>>>> Regards,
>>>>> mpsuzuki
>>>>>
>>>>>> On Fri, Nov 26, 2010 at 5:05 PM,  <address@hidden> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> On Fri, 26 Nov 2010 16:49:27 +0530
>>>>>>> Manoj Kumar Bhatta <address@hidden> wrote:
>>>>>>>> I have used freetype 2.3.9 to display Indic/arabic language using gtk.
>>>>>>>> It displays correctly with its contextual interpretation.
>>>>>>>> But when I changed to freetype-2.3.10, I can see only original form of
>>>>>>>> each glyph, thus without any contextual
>>>>>>>> interpretation.
>>>>>>>> My environment is DirectFB/GTK.
>>>>>>>>
>>>>>>>> Can anyone suggest what can be the issue ?
>>>>>>> Umm, it's not easy for me to setup DirectFB/GTK environment
>>>>>>> soon, so please let me know more detail about your trouble.
>>>>>>>
>>>>>>> 1) how many prebuilt libraries in your DirectFB/GTK?
>>>>>>>
>>>>>>> 2) how did you update freetype?
>>>>>>>
>>>>>>> As far as I know, the text layout engine in GTK (Pango/
>>>>>>> HarfBuzz) does not rely any functionalities of FreeType2
>>>>>>> for Arabic/Indic text layout, it invokes FreeType2 to
>>>>>>> translate from Unicode to glyph index, and load a glyph
>>>>>>> data by glyph index. If these 2 functionalities are broken,
>>>>>>> I guess, the component glyphs would be wrong already
>>>>>>> (not contextual layout error). If you can make some
>>>>>>> screenshots, it's appreciated.
>>>>>>>
>>>>>>> Regards,
>>>>>>> mpsuzuki
>>>>>>>
>>> _______________________________________________
>>> Freetype mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/freetype
>>