Swapping the directions of the outer and inner borders seems to make sense.
I'll include that in my fixes.
David %^
From: Graham Asher [mailto:graham.as...@cartotype.com]
Sent: 27 June 2011 17:14
To: David Bevan
Cc: Werner LEMBERG; freetype-devel@nongnu.org
Graham,
Certainly the FT stroker could be speeded up by limiting the use of
trigonometric functions as far as possible.
However, that would be quite a lot of extra work, so I won't be making any
changes in that direction at this time.
Thanks.
David %^
From:
Hi,
our building system warned me that there are .gitignore files
distributed in release tarballs of freetype.
Could you remove them in upcoming releases?
Regards
Marek
P.S.: I see that they are there since 2.3.12
___
Freetype-devel mailing list
in openSUSE we apply a patch called freetype2-bitmap-foundry.patch
which seems to add foundry support to PCF font files, likely to fix
the problem reported over at
http://lists.freedesktop.org/archives/fontconfig/2006-February/002072.html
. The patch is attached for your inspection, can
Hi;
On Wed, Jun 29, 2011 at 6:41 PM, Werner LEMBERG w...@gnu.org wrote:
in openSUSE we apply a patch called freetype2-bitmap-foundry.patch
which seems to add foundry support to PCF font files, likely to fix
the problem reported over at
On 25 Jun 2011, at 06:56, Werner LEMBERG wrote:
Please try the current git snapshot and play with the options
--hinting-range-min and --hinting-range-max.
Currently, the default value for hinting-range-max is 1000; this means
that the autohinter tests all ppem values up to 1000 to find
Marek Kasik mka...@redhat.com writes:
our building system warned me that there are .gitignore files
distributed in release tarballs of freetype.
Could you remove them in upcoming releases?
Why should .gitignore files be removed from release tarballs?
They're part of the source code.
A build
