va == vernon adams v...@newtypography.co.uk writes:
va Can anyone tell me what the equivalent is of 'forced auto-hinting on'
va under fontconfig settings? is it 'hinting' false, 'Autohinter' true,
va hintstyle 'full' ?
autohint=true should override everything else.
I use a config snippet which
It's rather that code is missing which checks that segments from
different outlines have enough vertical separation. I have to
investigate yet whether this is a problem in my bytecode or a
general problem with the FreeType autohinter.
It's allways been noticeable to me that when i
Is it actually possible to specify the x-height threshold
independently of the total height threshold? I never could seem to
find that in the code!
It's a two-step approach (all line numbers from aflatin.c refer to the
current git):
1. Determine the x-height scaling factor using the
Vern,
thanks for the images.
My point is that the freetype autohinter should (if possible) render
x-heights cap heights the same as the freetype bytecode
interpreter. Though from your comment below, i think you are saying
it's not a good idea to force freetype to do that.
Well, `force'
Does TTfautohint allways snap upwards, to the pixel edge above?
rather than snapping to the pixel edge below, even if the pixel edge
below is closest?
It depends. For x-heights, the current code slightly favors rounding
up (using 0.375 instead of 0.5 as the threshold). I will soon add an
On 09/02/12 15:17, Werner LEMBERG wrote:
So, in theory, it could be possible to add a feature to allow the
user to set the threshold ? :)
Not only in theory! We are going right now to implement that. Have a
look at the `autohinter-properties' branch in the FreeType
repository.
Thats
On 09/02/12 20:49, vernon adams wrote:
It's allways been noticeable to me that when i manually hint fonts on
Windows GDI, the font at small pt sizes renders on Freetype sytems with
the x-height and Caps height lower than under Windows GDI. Therefore it
makes sense that the reverse happens when
On 10/02/12 03:07, Infinality wrote:
Hi Erik!
Distortion measurement and outline optimization is what's needed.
Not sure if this is easier, but I've thought that the easiest way
conceptually would be to force at least 1 pixel between any two
horizontal stems when available. Like, if you have
Thought this might help: http://lettersfromsweden.se/ttfautohintingreview/
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
disclaimer - it's an article written by the guy who accused me of
piracy, so my views may be biased :P
For sure though, ttfautohint cannot better well executed manual hinting
for fonts being rendered on windows GDI OS's. Would be more
informational to see GDI grayscale and Directwrite
Thought this might help: http://lettersfromsweden.se/ttfautohintingreview/
Thanks!
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
On 08/02/12 21:53, Behdad Esfahbod wrote:
On Wed, Feb 8, 2012 at 4:10 PM, vernon adams v...@newtypography.co.uk
mailto:v...@newtypography.co.uk wrote:
disclaimer - it's an article written by the guy who accused me of
piracy, so my views may be biased :P
Isn't it a compliment coming
I was testing Arabic webfonts on XP the other day and it was so
pathetic. It's just, you can't get good rendering. Period.
Hehe. Arabic is not supported (yet).
The x-height issue should definitely be addressed though.
I will.
And the file size thing is one of the first things I keep
13 matches
Mail list logo
