Mario Todorov | 29 Jul 10:11 2014

[ft] A problem with Cyrillic fonts

I need to make my player Marantz UD5007 (which uses FreeType) to show Cyrillic subtitles, but instead it
shows only things like 3/4, D with a slash in the middle and so on. What am I to do? I tried saving the .srt file
in ANSI, Unicode, Unicode big endian and UTF-8. The first and the last showed different signs (not the
right ones) and the others weren't even recognized as subtitle files. I hope you can help me.

Have a nice day,
Michael IV | 20 Jul 17:11 2014

[ft] Tab (\t) escape space

Hi All.I can't understand how I convert tab (backslash t) to glyph numerics.
I mean,if I have "Hello\tWorld" string ,how many spaces should I insert between 
"Hello" and "World" ?


Freetype mailing list
Freetype <at>
LM | 17 Jul 22:26 2014

Re: [ft] Freetype Digest, Vol 115, Issue 8

On Thu, Jul 17, 2014 at 12:00 PM,  Werner LEMBERG wrote:
> Sorry, I have no idea what is causing that.  Please contact the MinGW
> list and ask for assistance, CCing me.

MinGW list will just send the problem back to the library developers.
I used to be very involved in giving support on that list.  I'll
attempt to debug it further when I have time to and see if I can come
up with a work-around or figure out what's changed between the
different versions of freetype.  I mainly wanted to know if it was a
bug or a desired result so I'd know how to proceed when I attempt to
fix or work around it.

> No, it should work out of the box.  Maybe a problem with the autoconf
> tools ? have you tried to compile and install the newest versions of
> autoconf and libtool?  What msys provides by default is quite old.

I have later versions of GNU autotools I've built from source that I
can try.  I also have latest version of GNU make currently installed.
If the older version of freetype works and the newer doesn't with the
same set of tools, it doesn't sound like the tools that are causing
the issue.

LM | 17 Jul 13:58 2014

[ft] freetype dll for mingw

I've been building freetype on MinGW with msys.  I just upgraded my
freetype build script from freetype- to freetype-2.5.3.  I
noticed some minor differences in the build including a new
freetype-config.1.  However, there was one important difference
between and 2.5.3.  Using the same commands, the prior version
generated a .dll file (it created both libfreetype-6.dll and
libfreetype.dll.a).  The current version only generates the static
library.  I tried adding --enable-shared to the configure options, but
the results were the same.  Do I need to do something special to
generate a dll file with version 2.5.3?  I can always build a shared
library with dlltool after the fact if dll creation is no longer
supported.  Was wondering if this was a desired change in behavior for
the freetype build system or if it was an issue.  Just to be sure, I
reran both build scripts (one for and one for 2.5.3) in my
current environment and I get the same outcome.  The earlier version
creates a shared library and the 2.5.3 version does not create one on
my system.  Am wondering if this is a desired result or not so I can
decide how best to work around the situation in my build script.

Thank you.
datao zhang | 9 Jul 03:45 2014

[ft] : Microsoft YaHei UI font can't be displayed well

Hi all:
when i test the freetype 2.5.3 with microsoft YaHei UI font in 12, 14, 16, 18, 20, 22, 24 pixel size, i find Freetype engine can't handle it correctly in some text size, ex: 12, 14, 24 px size. I have enabled TT_CONFIG_OPTION_BYTECODE_INTERPRETER and TT_CONFIG_OPTION_SUBPIXEL_HINTING. I add an attachment here. The character "据" (unicode: U+636E)used as test case in attachment.
Does anyone have idea for this problem? Thanks!
Freetype mailing list
Freetype <at>
Michael IV | 1 Jul 15:57 2014

[ft] Number '2' glyph outlines for "verdana regular" get rendered wrong

Hi All.I am testing font rendering from outlines.I am testing with Verdana.ttf regular.
All the charset renders perfectly except of  glyph of number 2 which gets cut off at the angle.I tested other styles of Verdana (italic and bold) and those work correctly.

Now,I am using FT_Outline_Decompose
to build the outline path.Is it possible it misses some segment cases? 

Here is the screenshot of the issue:

Freetype mailing list
Freetype <at>
Vincent Larsen | 19 Jun 19:02 2014

[ft] Characters showing as absent from a font

To whom it may concern;


I am using FreeType with the open source BabelStone Han font and have noticed FreeType doesn’t show some characters as being in the set (for example, FT_Get_Char_Index returns zero for character E7 [lowercase c with a cedilla under it).  I have verified the characters in question by looking at the font with Window’s charmap program.

I am still very new to FreeType and was wonder if there were any suggestions you could give that might get me past this problem.




Freetype mailing list
Freetype <at>
Michael IV | 18 Jun 14:55 2014

[ft] Outline decompose scaling

Hi All. I am decomposing outline of a glyph to paths.But the points have huge coordinated even after division by 64.

Every point I am getting from the path is by default in a range of ~984036148 .How do I convert such a number to normal font size? 

Michael Ivanov
Graphics Software
Tel:+972 54 4962254

Freetype mailing list
Freetype <at>
Yose Widjaja | 16 Jun 17:05 2014

[ft] FT_Load_Glyph and invalid argument (error 6)

Hello All,

I just recently ported my codebase to android (from linux) and when my code got to the point of:

         int glyph_index = FT_Get_Char_Index(face, moo);
         if(glyph_index != 0){
              FT_Load_Glyph(face, glyph_index, 0); // returns 6

it returns error 6, which seems to mean "Invalid Argument".

I've checked the "face" argument, and it has been initialized with FT_New_Memory_Face properly (the file size input was non zero, it returned zero etc).

The fonts used were identical with the one in linux. What other potential errors could I have been missing?

I've checked both the library and header versions of freetype, and both are 2.5.3.

Can anyone point me to the right direction?

Freetype mailing list
Freetype <at>
Jeffrey Sheen | 13 Jun 11:42 2014

Re: [ft] Question: linker errors when building freetype for iOS in Xcode

Hi all,

I have successfully built a full version of freetype2, using the freetype-ios project's Xcode project file. However, I am still unable to build a minimal version of freetype2 using the 'configure' command line method. Ideally, I would like to just build support for TrueType and OpenType font formats.

Please find attached my 'ftoption.h' and 'modules.cfg' files, and the batch script used to cross compile for iOS architectures (including the i386 simulator).

I get linker errors when trying to use the static library built with this configuration. Specifically:

Undefined symbols for architecture i386:
  "_FT_Gzip_Uncompress", referenced from:
      _sfnt_init_face in libfreetype-ios+simulator.a(sfnt.o)
ld: symbol(s) not found for architecture i386

I can see that 'sfnt_init_face' calls 'FT_Gzip_Uncompress' in the source code.

Although there is no dependency mentioned in the documentation, is it the case that the TrueType or OpenType modules require Gzip support to be enabled? I have disabled it in my build options, as I interpreted it as being optional.

Any help is much appreciated.



On 23 May 2014 12:03, Jeffrey Sheen <jeff <at>> wrote:
Dear Werner and the wider freetype mailing list,

I just wanted to say that I fixed my OSX build environment by reinstalling the latest distribution of the Xcode command line tools.

I have updated my StackOverflow question with this solution, so that others with the same issue can resolve it without resorting to the mailing list.

Thank you for your patience,


On 15 May 2014 17:09, Jeffrey Sheen <jeff <at>> wrote:
After contacting the owner of the freetype2-iphone git project, it seems that he has the same problems building the library with Xcode. I have decided to put that approach to one side for now, and to follow the procedures detailed in INSTALL.UNIX and INSTALL.CROSS.

My execution of the `configure` script is currently not working with the parameterisation suggested on StackOverflow, resulting in errors to do with the `limits.h` and `assert.h` header files. However, this is specific to my build environment, and not a general freetype2 question.

I have addressed the StackOverflow community to try to resolve this:



On 14 May 2014 23:58, Jeffrey Sheen <jeff <at>> wrote:
Many thanks for your quick response Werner.

This being my first foray with freetype2, I had indeed overlooked the customisation of `ftmodule.h`.

After commenting out the modules corresponding to those `.c` files that I had omitted from the compilation step, I rebuilt the product. I ended up with a library of 3.2MB, as opposed to the previous build of 2.6Mb. I then re-added it to my other, dependent Xcode project.

The first clean and build cycle of the dependent Xcode project yielded the same linker errors, so there is still something awry. I will give it another go in the morning.

Perhaps I will jettison my plan to build the freetype2 library with Xcode altogether. There are some suggestions for a command line process that I can attempt instead.

On 14 May 2014 19:38, Werner LEMBERG <wl <at>> wrote:
> However, when trying to build the dependent Xcode project, I get the
> following linker errors:
> "_bdf_driver_class", referenced from:
> [...]
> I notice that these errors contain the names of modules that I have
> disabled, by removing their respective ".c" files from compilation
> in the original "freetype2-ios" Xcode project.
> Was there some other configuration required in that Xcode project,
> in order to remove references to these disabled modules?

I guess that you've missed to update `ftmodule.h' to hold only the
modules you are going to use.  Cf. `docs/CUSTOMIZE'.


Attachment (configure-make-ios+simulator): application/octet-stream, 5357 bytes
Attachment (ftoption.h): text/x-chdr, 70 KiB
Attachment (modules.cfg): application/octet-stream, 8 KiB
Freetype mailing list
Freetype <at>
Szépe Viktor | 9 Jun 22:23 2014

[ft] checking national glyhs

Good morning!

I'd like to detect whether a glyph (e.g. 0x0150) is part of the font.  
Actually detect Hungarian language support of webpages. Font file  
names are extracted from CSS.

Is it OK?
ftdump -v /usr/share/fonts/truetype/msttcorefonts/verdana.ttf | grep 0x0151

Or should I care about these?
    0: platform 1, encoding 0, language 0
    1: platform 3, encoding 1, language 0 (active)
..any of them could contain that glyph.

It would be great to have an automated shell (CLI) tool.
Please help me.

Szépe Viktor

+36-20-4242498  sms <at>  skype: szepe.viktor
Budapest, XX. kerület

Freetype mailing list
Freetype <at>