Attached is a patch for tafpgm.c; please apply temporarily to make
the `fpgm' table four bytes longer.
Thanks for that.
Have you been able to test that? Are fonts generated with the
slightly larger `fpgm' table rendered correctly, or do you still get
an egg-shaped `O' glyph?
Otherwise, I'm
Hi, sorry i forgot about that.
Patch wouldn't apply
i get -
patching file tafpgm.c
patch: malformed patch at line 14: };
My patch file looks like this (taken from your post) -
diff --git a/src/tafpgm.c b/src/tafpgm.c
index 1268e29..3874844 100644
--- a/src/tafpgm.c
+++ b/src/tafpgm.c
My patch file looks like this (taken from your post) -
diff --git a/src/tafpgm.c b/src/tafpgm.c
index 1268e29..3874844 100644
--- a/src/tafpgm.c
+++ b/src/tafpgm.c
@@ -4298,6 +4298,11 @@ unsigned char FPGM(bci_hint_glyph) [] = {
ENDF,
+ PUSHB_1,
+100,
+ FDEF,
+ ENDF,
What i have noticed with ttfautohint is that often e.g. a regular
weight of a font will grow in size at a bigger % than the bold
weight. So i'm thinking the Regular is 'over-hinted', maybe.
Well, ttfautohint has no possibility to decide whether a font is bold
or not... The Infinality
Thanks for that.
Also, how easy might it be to implement an Option that auto-instructs only the
Y-axis ? One thing i'm noticing is that font file sizes almost double as a
result of ttfautohint (10-20% more than manual hinting) and I'm wondering if
much of the x-axis stuff might be
The 'final image' is simply the ttfautohint instructions with the addition of
links (double links work best in this instance). I did no extra hinting from
fontlab - what you see afaik is pixel fitting from the ttfautohint
instructions, plus the effect of the additional links. Sadly Fontlab has
The 'final image' is simply the ttfautohint instructions with the
addition of links (double links work best in this instance). I did
no extra hinting from fontlab - [...]
[...] if i look at the same font in FontForge's Gridfitmode, then i
don't see the egging issue at all.
Exactly! Such a
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
Thanks again for your invaluable help in testing ttfautohint!
My pleasure. Very keen to see a working autohinter available to font
designers :)
The feedback i'm getting from my screenshots is that the ttfautohint
output is overall superior under DirectWrite to the original hinted
I am curious - as i understand it(?) ttfautohint uses freetype to
find snap zones etc from which it bases it's TT instructions output.
I've copied a large part of the autofit module into ttfautohint;
additionally, I'm calling some FreeType routines for generic reading
and parsing of the input
Hi Werner,
Do you think it's possible that the autohinter can be tweaked to lessen the
effects of the aggressive vertical filtering of GDI?
or is it already at the limits of what's possible for GDI?
The feedback i'm getting from my screenshots is that the ttfautohint output is
overall superior
Just posted screenshots of ttfautohint output under DirectWrite
(Cleartype Grayscaling).
Thanks again for your invaluable help in testing ttfautohint!
Interesting. imo, generally the ttfautohint output is superior to
the original fonts' output, though there are some glitches, e.g. dot
http://code.newtypography.co.uk/
Just posted screenshots of ttfautohint output under DirectWrite (Cleartype
Grayscaling).
Interesting. imo, generally the ttfautohint output is superior to the original
fonts' output, though there are some glitches, e.g. dot accents are malformed.
However, I don't understand where the differences come from.
Nothing in the hinting instructions added by ttfautohint is
specific to ClearType. It uses a large number of twilight points
which is probably unusual a bit, but this doesn't explain how the
asymmetry can come into existence.
On 19 Jun 2011, at 16:37, Werner LEMBERG wrote:
I'm guessing the render differences are caused by my tests being run
on WinXP Win7.
Interesting. Is Win7 OK? Does WinXP only fail?
On Chrome the Win7 XP were near identical, as the browser uses GDI on both
OS's.
I will do some tests
Mhmm. Up to now I've *never* seen a font rendered with FreeType
which shows such a large deviation from the Windows font engine. I
believe that FreeType's output is quite trustworthy.
heh. Really? Depends what you mean by 'large deviation' i guess. I
only ever seem to see differences
Hi
updated ttfautohint from the repository made a better waterfall test page.
The ttfauto hinting looks much better imo, though still not 100% perfect yet :)
i have now also included a test of a version of Ubuntu Font with TTF
instructions tables replace by instructions from Fontforge's
On 18 June 2011 04:42, Werner LEMBERG w...@gnu.org wrote:
Please post a URL
where I can download the Ubuntu font you've used.
http://font.ubuntu.com
Of note is that at larger sizes (20px - 30px) the rendering breaks up
on curves. Is it possible that the autohinter is not yet set to
I have added detailed shots to http://code.newtypography.co.uk/?p=898
At 400% magnification the difference does not look so great, but at 100% the
difference in rendering is noticeable. I'll leave hinting interpreation to the
experts, but to my eyes the vertical extremes of curves are not being
but i am embarrassed to admit that i have built the library but have
not found how to use the 'autohint' function :) a quick howto,
please!
One important thing I've forgotten to mention: You need the current
git version of FreeType to test the ttfautohint library; the
`configure' test for
I've carried out some simple tests using ttfautohint with the Ubuntu Font on
Win XP Win7, Chrome12 Firefox4.
The screenshots are at http://code.newtypography.co.uk/
Looks good so far, but i shall test more fonts, particularly a serif and a bold
display face. I chose Ubuntu Font as i know it's
On 17 June 2011 19:43, Dave Crossland dcrossl...@google.com wrote:
A Verdana comparison would be nice! :)
Yet, on consideration, impossible, due to proprietary licensing
restrictions. What a pain! :)
___
Freetype-devel mailing list
Vern,
I have now added some simple upper lowercase waterfall tests to
'ttfautohint tests' at http://code.newtypography.co.uk
thanks a lot for the tests and the test images! Please post a URL
where I can download the Ubuntu font you've used.
Of note is that at larger sizes (20px - 30px)
The 'stretched' x-height could be a matter of taste, but personally
i would like to see the autohinter err on the side of less
stretching if possible.
Hmm. I could add the ability to switch off x-size snapping, and I
could also change the rounding rules to something similar the SROUND
24 matches
Mail list logo
