Werner LEMBERG | 4 Feb 16:29
Picon

[ft] ttfautohint: separate GUI and console binaries


Folks,

it took me a whole week of intensive documentation reading and
compilation experiments, asking on various mailing list, etc., etc.,
to eventually find out that I need two binaries on Windows, one for
the console and one for the GUI.  For consistency I've decided to
create two binaries for all platform.

Sigh.  It's simply not possible to make a Windows program behave the
same way as a POSIX one.  I haven't believed it, now I know :-| Well,
I'm an absolute beginner w.r.t. to Windows programming...

After building from the current git there is now a `ttfautohint' and
`ttfautohintGUI' binary.  It compiles nicely on Windows also; I've
successfully used MinGW (but please check the `INSTALL.git' file for
more details).  The only drawback of creating a static GUI binary on
Windows is its size: Due to the Qt libraries it's about 8MByte
(compared to 150kByte on GNU/Linux using Qt DLLs).

I invite the adventurous user to compile and test!  If everything
works fine, I'll release a new version in a few days.

   Werner
Francesco Panicucci | 27 Jan 12:31
Picon
Gravatar

Re: [ft] Problem rendering V and Y less than 12 pixel text

>It looks like a font problem.  In particular, I see that you are
>rendering without anti-aliasing, and many TrueType fonts support
>bitmap rendering only in a PPEM small range (if at all).  Use a font
>editor or font dumper to check the `gasp' table of the font to find
>out the supported ranges.

 

Thanks for reply,

 

our problem is that we can’t render with anti-aliasing because we have not the alpha so we use 1-bit monochrome bitmap glyphs.

We found that the bad rendering issue is due to the update of  the freetype reference library used in our system from version 2.4.4 to 2.4.5 and later.

 

The documentation reports into the “CHANGES BETWEEN 2.4.4 and 2.4.5” section the following note: “If autohinting is not explicitly disabled, FreeType now uses

the autohinter if a TrueType based font doesn't contain native hints.”

We tested several configuration using the latest version of the library (2.4.8) in order to obtain the same result as that we had using 2.4.4 version .

We set both FT_LOAD_NO_AUTOHINT and  FT_LOAD_NO_HINTING flags but we didn’t obtain any improvements.

Using the 2.4.8 library and the FT_LOAD_NO_AUTOHINT flag the “v” and  ”y” glyphs are bad rendered. Than, setting FT_LOAD_NO_HINTING flag we have the problem with “t” glyph and finally using both the flags the “t” and “y” glyphs are not perfectly aligned and “J” is missing.

 

https://docs.google.com/open?id=0B0eADBsvqd19ZGFiODBjNmMtYjY1NC00NDA3LWE0YzEtNzJmYmIwZGU2N2U1

 

Our question is, how can we set any flags or parameters in order to obtain with 2.4.8 version of the library the same behavior we had using 2.44 version?

 



Francesco

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Anders Wallin | 24 Jan 18:45
Picon

[ft] FreeSerifBoldItalic and "zj"

Hi list,

I'm using font geometry from libfreetype6 (2.4.4-2ubuntu1.1) to test
an application I am writing.
My application takes only non-intersecting lines or curves as input.

I've run into a problem with FreeSerifBoldItalic and "zj". In my
program this produces overlapping characters. I've tried it with
Inkscape, LibreOffice, and GIMP also. LibreOffice produces overlapping
characters while Inkscape and GIMP do not:
http://www.anderswallin.net/2012/01/with-freeserifbolditalic-dont-ever-write-zj/

Here is the code I am using to extract geometry from freetype:
https://github.com/aewallin/truetype-tracer/blob/master/src/ttt.cpp

Any thoughts on why this is happening and how to avoid it?

thanks,
Anders Wallin
Khaled Hosny | 24 Jan 02:08
Favicon
Gravatar

[ft] Slightly less out dated Windows binaries

Hi all,

I was looking for FreeType Windows binary to cross-compile an
application for Windows, and found the GnuWin32 ones that are linked in
the download page too out dated for the application I was building (as
already stated), then incidentally I found 2.4.2 binaries in the GTK+
for Windows page:

http://www.gtk.org/download/win32.php

So I thought to share my 'discovery' with others, and may be it would be
a good idea to add a link to it into the download page so it can be
found easily (it does not show in at least the 1st two page of Google
search for 'freetype windows').

Regards,
 Khaled
Antonio Bigi | 18 Jan 16:33
Picon

[ft] Problem rendering V and Y less than 12 pixel text

Hi all,
I'm using freetype2 on an embedded device. When I run my application on device with 7-inch display all the glyphos are rendered fine (as shown in the image above).





If I run the same application on a device with 9-inch or 12-inch display some glyphos (V, v, Y and y) are not rendered correctly. As shown in the image above.


https://docs.google.com/open?id=0B49ffoLIUA2YZDkwMTAzNmEtYTEyMy00MDVjLThmNTgtMzY4ZTRiYTJhMGEw 


7-inch and 9-inch display has 135 DPI, while 12-inch display has 96 DPI.
The size of the text is set using FT_Set_Pixel_Sizes(fHandler->face, 0, fontH);

In the image above I colored in red the whole canvas and in yellow the bitmap glyph area.



I get the bitmap using the following code:

error = FT_Load_Char(fHandler->face, c, loadFlag);
if (error)
return -1;

FT_GlyphSlot bitmapGlyph = fHandler->face->glyph;
FT_Bitmap& bitmap = bitmapGlyph->bitmap;


Do you have any suggestions on how to resolve this problem?


I approach a dirty solution forcing autohint during load of V and Y characters

if (fontH<12 && strlen(text)==1 && (text[0]=='V'||text[0]=='v' || text[0]=='y'||text[0]=='Y')){
loadFlag |= FT_LOAD_FORCE_AUTOHINT;
}




It works on 12-inch display but I think this solution is too specific and dirty to avoid that other problems appear in the future on other display models.
Using always autohint flag the quality of rendering became poor.

Thanks,
Antonio



_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Jochen Jägers | 17 Jan 14:27
Picon

[ft] ugly output with freetype and gtk

Hello,

i'm developing an embedded system for home automation based on
gnu/linux.

The userinterface is build in HTML/Javascript displayed in a fullscreen
browser based on webkit-gtk with freetype as font-backend.

I get ugly output on some glyphs. I've made a screenshot to illustrate
this ugly output. 

http://tinypic.com/r/4uwbkl/5

Look at "Standort" for example. The "d" has two pixels in the top left
corner. I get this ugly output with different types and different file
formats. The text in other gtk-based applications look ugly too.

I've tryed many things i found on the internet like different settings
for hinting, lcdfilter and subpixels but nothing worked.

I've also tryed different versions of freetype (2.4.4 and 2.4.8) with
the same ugly result.

At the moment I've no idea to solve this problem.
Do you have any idea what i can try?

Greetings
Jochen Jägers

_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
Werner LEMBERG | 13 Jan 20:13
Picon

[ft] FreeType License and patents


Folks,

I've recently stumbled across the following paragraph from the Apache
license 2.0 (http://www.apache.org/licenses/LICENSE-2.0.html):

  3. Grant of Patent License.

  Subject to the terms and conditions of this License, each
  Contributor hereby grants to You a perpetual, worldwide,
  non-exclusive, no-charge, royalty-free, irrevocable (except as
  stated in this section) patent license to make, have made, use,
  offer to sell, sell, import, and otherwise transfer the Work, where
  such license applies only to those patent claims licensable by such
  Contributor that are necessarily infringed by their Contribution(s)
  alone or by combination of their Contribution(s) with the Work to
  which such Contribution(s) was submitted.  If You institute patent
  litigation against any entity (including a cross-claim or
  counterclaim in a lawsuit) alleging that the Work or a Contribution
  incorporated within the Work constitutes direct or contributory
  patent infringement, then any patent licenses granted to You under
  this License for that Work shall terminate as of the date such
  litigation is filed.

Looking up the FreeType License I've found out that we don't have such
a clause...

I would like to add something similar, with the exception that code
especially marked as patented within the FreeType source code is not
covered.

Comments?

    Werner
Werner LEMBERG | 25 Dec 23:41
Picon

[ft] ttfautohint 0.6 has been released


ttfautohint 0.6 has been released.

It is available from

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

or

    http://sourceforge.net/projects/freetype/files/ttfautohint

Merry Xmas!

   Werner

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
    http://download-mirror.savannah.gnu.org/releases/

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

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
`src/ttfautohint.h' for a detailed description.  Note that the library
itself won't get installed currently.

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

  ttfautohint --help

for usage information, or say

  man ttfautohint

to read its manual page.

=============================================================================

New in 0.6:

* Improved handling of composite glyphs.

* Implement option `-p' to pre-hint glyphs with original hints before
  conversion takes place.

* Don't add a DSIG table if there is none in the input font.

* Human-readable error messages instead of hexadecimal error codes.

* Better tests (both at runtime and compile time) to reject too old FreeType
  versions.
vernon adams | 17 Dec 10:40
Picon
Favicon
Gravatar

[ft] freetype autohint versus ttfautohint

Werner,

What could be the differences between a font hinted with ttfautohint 
rendered with freetype, and a non-hinted font rendered with freetype's 
via it's built-in autohinter?

As i understand it there should be no difference, as ttfautohint is 
based on freetype libs anyway. But what if a non-hinted font is rendered 
on a freetype system under 'full' hinting? Will that font be autohinted 
and rendered exactly the same as a ttfautohint'd font?

Just trying to work out what pros/cons maybe of 'ttfautohinting' fonts 
that are to be used on freetype systems :)

Many thanks

vernon
David Welch | 13 Dec 20:26
Picon
Gravatar

[ft] Cannot run C compiled programs Mac OSX

Hello all,

Im trying to install freetype on a MacBook running OS X 10.6.  Here's my procedure:

=================================================
$  curl -L -o freetype-2.4.8.tar.bz2 http://sourceforge.net/projects/freetype/files/latest/download?source=files
$  tar -xf freetype-2.4.8.tar.bz2 
$  cd freetype-2.4.8
$  ./configure

FreeType build system -- automatic system detection

The following settings are used:

  platform                    unix
  compiler                    cc
  configuration directory     ./builds/unix
  configuration rules         ./builds/unix/unix.mk

If this does not correspond to your system or settings please remove the file
`config.mk' from this directory then read the INSTALL file for help.

Otherwise, simply type `make' again to build the library,
or `make refdoc' to build the API reference (the latter needs python).

cd builds/unix; ./configure 
checking build system type... i386-apple-darwin10.7.0
checking host system type... i386-apple-darwin10.7.0
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... configure: error: in `/tmp/freetype-2.4.8/builds/unix':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
make: *** [setup] Error 1
=======================================================

I've attached my configure log file.  Any help would be appreciated!

David Welch

Attachment (config.log): application/octet-stream, 6736 bytes
_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
shinobu2.watanabe | 12 Dec 07:18
Picon

[ft] FreeType license confirmation

Hello.

 

I'm Shinobu Watanabe, working for Toshiba Corp. Japan.

 

We are considering using “FreeType” in our products.

Before going any further, however, we would like to confirm the following so that we are sure to fully respect your rights. 

You are the author and owner of the copyrights in the program.

You have distributed the program under the attached license that

permits us to use and redistribute the program with or without modification provided that any conditions stated in the license are met.

 

If you would please send me a return email confirming the above, that would be most appreciated.

 

And thank you very much for taking the time to create such a useful program.

 

Best Regards,

 

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

Shinobu Watanabe

 

Visual Network Team 2

Visual Network Software Dept,

Software Center

Toshiba Degital Media Engineering Corporation

 

Tel:+81-48-574-2410

E-mail:shinobu2.watanabe <at> toshiba.co.jp

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

 

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

Gmane