Werner LEMBERG | 12 Oct 10:15 2015

Re: [ft] FreeType 2 install issue

> I didn't see any e-mail address on this page that specifically
> mentions installations issues:
> http://freetype.sourceforge.net/developer.html#mailing-lists

Please write to the `freetype' mailing list for such issues.

> I can't get gmake to install the software properly.  [...]
> % pwd
> /usr/home/tree/Downloads/freetype-2.6.1
> % ./configure
> [...]
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> [...]
> gmake: Nothing to be done for 'unix'.
> Why is that message given, please?

It's a harmless artifact of the quite complicated setup of FreeType's
build system, and I haven't investigate yet how to suppress it (I'm
quite sure that it is possible).  Please ignore it.

> % sudo gmake install
> rm -rf /usr/local/include/freetype2
(Continue reading)

Huang Song (AA-AS/EIS3-CN | 8 Oct 12:04 2015

[ft] commercial usage

Dear Ms./Mr.

            As far as we know, Freetype is base on FTL and GPLv2  licenses.


            Can we use it in commercial software freely and don’t open our source codes(Can only select FTL license)?


            Thank you!



Mit freundlichen Grüßen / Best regards

Leo Huang 黄 松

Bosch Automotive Diagnostics Equipment (Shenzhen) Limited

5/F, A, Garden City Cyber Port,
Nanhai RD No. 1079

Nanshan district
Shenzhen 518067


Tel.  +86 (755) 8302 3805
Fax  +86 (755) 8347 6707

Mob.+86 158 8970 9520

Song.Huang <at> cn.bosch.com



Freetype mailing list
Freetype <at> nongnu.org
Werner LEMBERG | 5 Oct 08:06 2015

[ft] Announcing ttfautohint version 1.4

ttfautohint 1.4 has been released.

The source tarball, statically-linked binaries for Win32 (TTY and GUI) and
OS X (TTY only) are available from




Instructions to build the GUI version on OS X can be found at




PS: Downloads from savannah.nongnu.org will redirect to your nearest
    mirror site.  Files on mirrors may be subject to a replication
    delay of up to 24 hours.  In case of problems use



This project provides a library which takes a TrueType font as the input,
remove its bytecode instructions (if any), and return a new font where all
glyphs are bytecode hinted using the information given by FreeType's
autohinting module.  The idea is to provide the excellent quality of the
autohinter on platforms which don't use FreeType.

The library has a single API function, `TTF_autohint'; see
`lib/ttfautohint.h' for a detailed description.  Note that the library
itself won't get installed currently.

A command-line interface to the library is the `ttfautohint' program; after
compilation and installation, say

  ttfautohint --help

for usage information, or say

  man ttfautohint

to read its manual page.

A GUI to the library is `ttfautohintGUI'; it uses the Qt4 framework.  The
compilation of this application can be disabled with the `--without-qt'
configuration option.


Version 1.4 (2015-Oct-04)

* Support for Thai and Lao scripts.

* Support for the Arabic script.

* Better support for scripts that contain superscript-like and
  subscript-like glyphs, e.g., the International Phonetic Alphabet (IPA).

* Accents and other `non-base' glyphs are now hinted without snapping to
  blue zones.

* A new control instruction syntax form was added to adjust the mapping
  between glyphs and styles.  Right now, its usage is quite limited; a
  forthcoming version will give much more flexibility.

* The `touch` keyword in a delta instructions file was buggy: If used for a
  point `P` at a ppem value `s`, it sometimes led to unwanted movements
  of `P` for ppem values unequal to `s`, thus causing outline distortions.
Werner LEMBERG | 4 Oct 12:23 2015

[ft] Announcing FreeType version 2.6.1

FreeType 2.6.1 has been released.

It is available from




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

See below for the relevant snippet from the CHANGES file.



PS: Downloads from  savannah.nongnu.org  will redirect to your nearest
    mirror site.   Files on  mirrors may  be subject to  a replication
    delay   of   up   to   24   hours.   In   case   of  problems  use



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
(e.g.,  colored  text  rendering,  `hollowing',  etc.).   However,  it
greatly simplifies these tasks by providing a simple, easy to use, and
uniform interface to access the content of font files.

FreeType  2  is  released  under  two open-source  licenses:  our  own
BSD-like FreeType  License and the  GPL.  It can  thus be used  by any
kind of projects, be they proprietary or not.


CHANGES BETWEEN 2.6 and 2.6.1


    - It turned  out that for CFFs  only the advance widths  should be
      taken from the  `htmx' table, not the side  bearings.  This bug,
      introduced in  version 2.6.0, makes  it necessary to  upgrade if
      you are using  CFFs; otherwise, you get cropped  glyphs with GUI
      interfaces like GTK or Qt.

    - Accessing Type 42 fonts returned  incorrect results if the glyph
      order of the embedded TrueType font differs from the glyph order
      of the Type 42 charstrings table.


    - The header  file layout  has been  changed (again),  moving  all
      header files except `ft2build.h' into a subdirectory tree.

      Doing so  reduces the  possibility of  header file  name clashes
      (e.g., FTGL's  `FTGlyph.h' with FreeType's `ftglyph.h')  on case
      insensitive file systems like Mac OS X or Windows.

      Applications  that  use  (a)  the  `freetype-config'  script  or
      FreeType's `freetype2.pc' file for pkg-config to get the include
      directory  for the  compiler,  and (b)  the  documented way  for
      header inclusion like

        #include <ft2build.h>
        #include FT_FREETYPE_H

      don't need any change to the source code.

    - Simple access  to named instances  in GX variation fonts  is now
      available (in addition to the  previous method via FreeType's MM
      interface).   In  the `FT_Face'  structure,  bits  16-30 of  the
      `face_index' field hold the current named instance index for the
      given face  index, and bits  16-30 of `style_flags'  contain the
      number of  instances for  the given face  index.  `FT_Open_Face'
      and friends also understand the  extended bits of the face index

      You need to enable  TT_CONFIG_OPTION_GX_VAR_SUPPORT for this new
      feature.  Otherwise, bits  16-30 of the two fields  are zero (or
      are ignored).

    - Lao script support has been added to the auto-hinter.


    - The auto-hinter's Arabic script support has been enhanced.

    - Superscript-like and  subscript-like glyphs  as used  by various
      phonetic alphabets like the IPA  are now better supported by the

    - The TrueType bytecode interpreter now runs slightly faster.

    - Improved support for builds with cmake.

    - The  function  `FT_CeilFix'  now   always  rounds  towards  plus

    - The  function  `FT_FloorFix'  now always  rounds  towards  minus

    - A  new load  flag `FT_LOAD_COMPUTE_METRICS'  has been  added; it
      makes FreeType  ignore pre-computed  metrics, as needed  by font
      validating  or  font  editing  programs.  Right  now,  only  the
      TrueType  module supports  it  to ignore  data  from the  `hdmx'

    - Another round of bug fixes  to better handle broken fonts, found
      by Kostya Serebryany <kcc <at> google.com>.
Lawrence D'Oliveiro | 2 Oct 04:12 2015

[ft] Debian Stable Still Has Old FreeType

I’ve just been getting to the bottom of a mysterious discrepancy in the
metrics of a .otf font between machines running Ubuntu 14.04 and those
running Debian (Stable 8.1 and also Unstable).

Turns out Debian Stable is still on version 2.5.2-3 of FreeType,
while Unstable has only just upgraded to 2.6-2. And whereas the
Ubuntu version of FreeType identifies itself as “2.5.2-1ubuntu2.4”, it
exhibits the newer behaviour rather than the older one.

This isn’t the first time I’ve come across a problem with Debian
FreeType, only to discover that upstream/newer versions don’t have that

Freetype mailing list
Freetype <at> nongnu.org
Kane O'Donnell | 12 Sep 07:53 2015

[ft] Fast wordcloud using FreeType?

For a pet project, I'm looking to make a wordcloud generator (e.g. http://www.wordle.net/) that is as fast as possible, and as someone quite new to text rendering, etc., I was wondering if the community could offer thoughts about terms of using FreeType for this? What I effectively need to be able to do is:

  1. map a given string (font + rotation) to some sort of binary pixel array so I can tell what space the word fills.
  2. store that to a "canvas" pixel array (this is used to store word positions and make sure they don't overlap, etc)
  3. once word placement is done, then be able to save the canvas (i.e. drawn words) to a vector format (for printing etc) that faithfully represents the original canvas.

From what I've read, FreeType will allow me to handle 1. and 2. relatively easily. However, I'm not sure about 3. While it's easy to, for example, save the position/rotation of all placed words, and then naively convert that to e.g. SVG, I'm not sure whether e.g. font size 32 means the same in FreeType as it will in SVG, and hence whether or not my non-overlapping word layout will be preserved. I guess that's my key question.

More than happy to get general feedback on such a project, including other suitable libraries -- though a key requirement is for it to be as fast as possible.


PS -- I've done something in Python but there was a messy and imperfect hack to convert from PIL (bitmap) to matplotlib (PDF), which basically failed point 3 as outlined above. I've also done this in Java, and I managed to find two libraries which did the job well. However, now I'm keen to learn a new language, and I enjoy using this as an example.

PPS -- I'm aware there are other methods (quad-tree + bounding boxes), though they're not as simple as the "does this pixel overlap that one" approach, and sometimes less functional and performant.

Freetype mailing list
Freetype <at> nongnu.org
Matthew Allen | 7 Sep 04:28 2015

[ft] Font kerning issue

I'm working on some code that uses Freetype to render text and some of the characters are too close together:

Would anyone be able to have a look at the code and comment?

Matthew Allen
Michael IV | 30 Aug 12:35 2015

[ft] Vertical line spacing problems with different fonts.

I am drawing multi line text using FreeType2.
Now,I compare my text position with Adobe AfterEffects built-in text.
I found that using standard fonts like Verdana the auto spacing looks good.
But with some less standard fonts like Segoe UI the second line text has a shift of several pixels on vertical axis.I set the line specing using Font metrics Height property.
Interesting also is that if I manually set the line spacing using this formula:

pen.y -= verticalSpacingInPixels / (fontSizeInPixels/ FontMetrics->UnitsPerEM )

then both in AfterEffects and in my app the spacing looks the same.

What can it be?May be Adobe AfterEffects calculates auto spacing in some unique way?But then why does it show the same results as in my app for standard fonts?


Freetype mailing list
Freetype <at> nongnu.org
Werner LEMBERG | 25 Aug 10:58 2015

[ft] FreeType patents page updated

In another mailing list there was a reference to


I wasn't aware that this page exists...

Consequently, I've just updated the patents page at


Tom Harlock | 19 Aug 17:33 2015

[ft] FreeType


I am looking to take a single truetype glyph's bytecode parse it and draw it (i.e. a single character, extracted from the map).  I have searched through the documentation, and couldn't find anything directly relevant.   Is this possible without modifying the source?  If so is it specified in the documentation, and where?

Thanks in advance,

T. Harlock
Freetype mailing list
Freetype <at> nongnu.org
Roy | 16 Aug 01:52 2015

[ft] WOFF2 support?

Hello list,

I wonder if Google's WOFF2 will be supported by freetype in future?