headers
Werner LEMBERG | 1 Dec 2010 13:32
Picon

[ft] FreeType 2.4.4 has been released


FreeType 2.4.4 has been released.

All users should upgrade.

It is available from

    http://savannah.nongnu.org/download/freetype/

or

    https://sourceforge.net/projects/freetype/files/

The latter site also holds older versions of the FreeType library.

See below for the relevant snippet from the CHANGES file.

Enjoy!

   Werner

----------------------------------------------------------------------

FreeType 2  is a software  font engine that  is designed to  be small,
efficient,  highly   customizable,  and  portable   while  capable  of
producing high-quality output (glyph images) of most vector and bitmap
font formats.

Note that  FreeType 2 is  a font service  and doesn't provide  APIs to
perform higher-level features, like text layout or graphics processing
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manoj Kumar Bhatta | 2 Dec 2010 06:57
Picon

Re: [ft] Glyph issue in freetype 2.3.10

>> 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 <mkbhatta <at> gmail.com> 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 )
(Continue reading)

Permalink | Reply | 4 comments |
headers
suzuki toshiya | 2 Dec 2010 07:03
Picon

Re: [ft] Glyph issue in freetype 2.3.10

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 <mkbhatta <at> gmail.com> 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 )
(Continue reading)

Permalink | Reply | 3 comments |
headers
Manoj Kumar Bhatta | 2 Dec 2010 07:33
Picon

Re: [ft] Glyph issue in freetype 2.3.10

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 <mpsuzuki <at> hiroshima-u.ac.jp>:
> 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 <mkbhatta <at> gmail.com> wrote:
>>>> I'm afraid something wrong in Pango, and it
>>>> might be long-term issue to analize why this trouble
(Continue reading)

Permalink | Reply | 2 comments |
headers
Werner LEMBERG | 2 Dec 2010 07:51
Picon

Re: [ft] Glyph issue in freetype 2.3.10

> 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 ?

Have a look in the CHANGES file!  Note that the current version is
2.4.4 (released yesterday).  Some speed improvements have been added
in 2.4.3 (but you should use 2.4.4).

    Werner
Permalink | Reply | 0 comments |
headers
suzuki toshiya | 2 Dec 2010 07:56
Picon

Re: [ft] Glyph issue in freetype 2.3.10

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 ?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 3 Dec 2010 13:17
Picon

[ft] Re: umlauts : Different Position between Word and FreeType


Céline,

please *never* send copyrighted material (in your case, the file
Font_U.ttf) to a public mailing list!  For this reason, I can't
forward your mail to the freetype mailing list (freetype-devel is
rather not for FreeType users).

> I have a question about umlauts.
> 
> When I use letter "ü" with Microsoft Word ( with attached font), the
> umlaut (¨)is closer to the "u" whereas I use FreeType, the umlaut is
> further.

It's simple to explain: The `FreeType' image is using the autohinter,
while the `MS Word' image uses the native TrueType bytecode hinter.
However, you can make FreeType use the bytecode hinter also; this is
documented in the API description.  If you are using FontConfig to
control your system font, it is also possible to change the hinting
accordingly.

In both cases, bytecode hinting must be activated during compilation
of FreeType.  Since version 2.4.0, this is on by default.

    Werner
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 5 Dec 2010 15:31
Picon

[ft] Re: Simple Question About How Hinting Works

[CCed to the freetype mailing list]

> I want to modify Juce to use Freetype to extract glyph outlines.
> Juce is a multiplatform GUI toolkit with some pretty nice features,
> see http://rawmaterialsoftware.com/

Currently, I get an error while accessing this page...

> Does hinting affect the outlines only?  In other words, is it
> sufficient to set the font height in Freetype and extract glyph
> curves, or do I have to use Freetype to render the curves to a
> bitmap?
> 
> Or, put another way, does all of the hinting activity occur in the
> vector representation, or are there special things that happy during
> the conversion to rasterization?

All hinting moves points, so your assumption is correct: Nothing
special happens during rasterization (except dropout control, if at
all).

    Werner
Permalink | Reply | 0 comments |
headers
Zoltan Kovacs | 6 Dec 2010 08:32
Picon

[ft] freetype and threads

Hi.

I am using freetype in one of my projects and have a question about
freetype and how thread safe it is.

My question is really simple: can I call FT_Load_Glyph() from
different threads at the same time while having only one FT_Library
instance?

I tried but it seems to cause corrupted rendering output so I think
that part should be protected by some locking mechanism in my
application to prevent parallel execution of FT_Load_Glyph() function.

Thanks,
Zoltan
Permalink | Reply | 1 comment |
headers
Róbert Márki | 6 Dec 2010 08:44
Picon

Re: [ft] freetype and threads

Hi

I strongly suggest to use multiple FT_Library objects, one for each thread, no locking is necessary.
"For multi-threading applications each thread should have its own FT_Library object."
http://www.freetype.org/freetype2/docs/reference/ft2-base_interface.html#FT_Library



On Mon, Dec 6, 2010 at 8:32 AM, Zoltan Kovacs <giszo.k <at> gmail.com> wrote:
Hi.

I am using freetype in one of my projects and have a question about
freetype and how thread safe it is.

My question is really simple: can I call FT_Load_Glyph() from
different threads at the same time while having only one FT_Library
instance?

I tried but it seems to cause corrupted rendering output so I think
that part should be protected by some locking mechanism in my
application to prevent parallel execution of FT_Load_Glyph() function.

Thanks,
Zoltan

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
Permalink | Reply | 0 comments |

Gmane