Plastica: Experimental 3D typeface issues


Hello guys,
I’m nearly finishing work on my new experimental 3D typeface called Plastica. I’m facing few problems I would like to discuss.

It is CFF OpenType made in FontLab on PC. Outlines are very precise and I used atypical custom UPM of 2300 units (23 modules at 100 units). But this should be fine regarding to older nodes on Typophile.
There are two versions: Plastica One (Striped) and Plastica Two (Outlined).
And here is what I struggle with:

1) On-screen rendering issues:

How can I remove all hinting data?


Hello everyone, thanks for reading!

I have been working on a new batch of fonts & while I though that I was well aware of all the basic ins & outs of hinting I have been encountering some information that casts doubt on this.

In short…

1.) What is the simplest & and/or most reliable way to inspect a ttf ot otf file & determine if it contains any hinting data?

2.) What methods might I use to remove any and all hinting data from an otf or ttf font file?

At my disposal I have fontlab5, fontforge, fontographer & the latest adobe fdk.

Thank you all in advance.

Microsoft VTT for hinting

Hello everybody!

I want to download the Microsoft VTT tool, but I can't figure out how is it possible!
Right here, on http://www.microsoft.com/typography/tools/vtt.aspx it tells that I must fax them a copy of a signed agreement. First of all, come on, fax in 2014? And also the link to that agreement doesn't work.

I've googled for it and couldn't find any solutions. I've seen some links to it on the FontLab forum, but they also do not work.

Does anybody know how to get Microsoft VTT?



I was wondering if anyone has experience with ttfautohint. The website offers a lot of information on hinting, but I can't find any information on how to actually use this software. I ran a ttf file through the program and it spit out a file without an extension. I added .ttf and it's a workable font which is 32kb bigger than the original file, so I assume it works. However, I don't know what the best settings are, and does anyone know if this can help me with hinting otf fonts as well? It doesn't run through the program in any case.

Raleway font - I'm not sure it's hinted for screen?


For a project I'm using Raleway through Google Fonts as a good alternative for Gotham. When I put some headers in a light weight, I get the feeling there's a bit of "warping" going on, so I guess there's no screen hinting apparent. First of all, I thought every Google font was a webfont, and thus adjusted for that particular use... but is that true? Or is it just about .woff-files that are not neccesarily hinted for screen usage?

ttfAutohint - Some advice from user would be useful.


I've seen some type designer used ttfAutohint http://www.freetype.org/ttfautohint/. For those who have tried it, can you give us your comments. Also, It seems possible to installed it on MAC OSX, however after a few inconclusive tests, I failed. Your help would be useful to help me to installed it. Thanks!

Recommend web fonts with great hinting

Could you recommend web fonts that you like and that have excellent hinting for the screen?

I am interested in work-horse typefaces for body text that I can purchase the rights to use with @font-face, so that would exclude all the offerings from those wonderful subscription based services. I have found the results from type at MyFonts can be spotty, and they never say if a font has been hinted by the designer.

Feel free to suggest your own work. I am interested in expanding my knowledge of good work that is out there. Thanks very much.

Type for LCD projectors

Interesting quandry, wondering if anyone has experience with this:
I'm working on a projected infographic for an exhibition. Besides the many challenges around getting said projection to look great in a small 24x24' gallery, I'm having a hard time getting the type to look good. Are there specific typefaces that work well with projectors? Should I be looking for type that is optimized/hinted for older raster displays?
Apologies for my lack of proper terminology. I'm delving into unknown territory, personally.

Background on my setup:

Different Auto-hinting tests and results

Hi typophiles

I'm trying to figure out which is the best quick auto-hinting solution, right now I know 4 (quick) options:

• No Hinting
• Fontlab Hinting (with proper stems/blue zones)
• FontSquirrel
• TTFautohint Program (thanks to Dave Crossland)

(I've attached the results) The question is:
Do you know any other quick auto-hinting options that might be worth a try?


*I'm using Chrome on Windows 8.1, and the tests with Impallari testing tool

webfont Advanced


some pics from my work on a font for my webpage destinated for very small sizes around 9px.
I am struggling with balancing hinting for small screen sizes, special versions for negative use on black ground with sub pixel rendering and so on…

In this pic one can see the results comparing (for now only) two browsers Google Chrome and Safari both on Mac.

For me the first one is the best, yet it is achieved with a particular thinner version of the same font only for the use on black ground. Otherwise as known sub pixel rendering tends to make fonts look much bolder than they are in reality.

Fractional Advance Widths vs. Advance Phantom Point


Hello Typophiles,

Apologies for the nerdiness on a first post.

In the midst of some last checks before releasing my first real font, I noticed an unpleasant beating frequency effect on repeated characters at smallish ppems when testing on Windows 7 with the "Natural" mode of DirectWrite ClearType rendering (tested via Firefox with the Anti-aliasing Tuner add-on). The characters phase in and out of different degrees of bluriness.

With a bit of investigation, it looks like this is due to fractional advance widths. I was hoping to be able to control for this by slightly adjusting the advance width phantom point via TrueType hinting. However, it looks like Windows is ignoring that in this rendering mode and using only the designed width instead.

Capline overshoots render strangely on Mac at 13 pt and 18 pt


Hi everyone,

I'm having some issues with a truetype web font conversion on FontSquirrel. The resulting truetype hints look as good as they can on Windows, but at 13 pt and 18pt only, the overshoots on rounded glyphs render strangely. I haven't found a solution for this yet, but I'm hoping someone might be able to help me get to the bottom of this.

Is it possible that the truetype hinting instructions are affecting rendering on OSX? I've read that hints are mostly ignored by this operating system in favor of something more built in, so I'm a little confused.

Are there certain tests I should run, or is there more information that would be helpful in understanding the issue?

Image below:

Bitmap Rasterization


Hi there,

I’ve experience a quite fuzzy thing: Exporting a font two times from FontLab, no known changes in the output settings.
The 1. font is the red text below, the 2. is the white text.
The only thing that was changed in between the 2. font-exports was the numbers (0 – 9) and the punctuation (,.;!?“”…) not displayed here.

It appears to be that now the Bitmaps are not the same anymore (especially the horizontal stems in a, e, s and h in the attached 300% example).
Anti-aliasing method is set to sharp in Photoshop, but this it seems has nothing to do with the different jittering in the result.

Any help or hint is highly appreciated!

Fussiness under the baseline


I'm cant find a solution to this little problem:

If you look closely, will see that at 14 and 16pts there seems to be grayscale pixels under the /n serifs. How can I remove it, so it looks like the ones at 15, 17 and 18pts? (Firefox/Mac)

The blue lines are already in place, like this:

However, the problem remains.
I spend all day experimenting, hinting, un-hinting, tweaking blue values, looking at pixels, etc... and wasn't able to find a solution. Nothing seems to make any difference.

The greyscale pixels below the /o are OK, but not the ones below the /n, /i, /l, etc...

Macbook Pro, retina screens, hinting, the future

Hello all,

In light of yesterday's unveiling of its Macbook Pro (with Retina Display), seems like good time to restart this question:
What do you see as the future of TrueType hinting? The short-term value is obvious. I get it. I'm with you.
But when breaking out the checkbook, how do we measure the value of hinting in the context of improving rasterizers, iOS's limited appetite for hinting, screen resolution, etc.?

This is an honest question, not a statement. It's a wonderful, daunting, inspiring, confusing time of possibilities and pitfalls.
Love to read some thoughts on this, in light of Apple's news. Many thanks.

Berlowized in the Big Apple--TDC Webfonts seminar.

Thanks to David Berlow for leaving the Vineyard long enough to enlighten and entertain us at the NYC TDC. The day flew by, we came we saw, we got some hints about web type. And a good time was had by all. Special thanks to Carol Wahler for running a smoothe sailing event, and to Nick Sherman for doing all that keeky stuff!

Correcting a glyph's hinting


I have recently purchased Quadraat Sans for use on a website and noticed it has some buggy hinting in Cyrillic glyphs at 17 px size. And I am just not going to use a different size.
That is, horizontal stems of letters "э", "з", "є", "н" are pixel lower than they should be — a really crucial detail in a Cyrillic font. And it ruins this font.

So I want to correct TrueType hinting of those letters. I know it's kinda illegal to do that, but that's not stealing a font or making a copycat and selling it. Just want to fix the bugs.

I have never dealt with hinting. So I had googled a lot, found some tutorials, but most of them are soo difficult to understand. TrueType hinting seems to be a mysterious process even for some of the authors of those tutorials.

FontLab Studio: How to duplicate a glyph with all its information


I have taken a TrueType font with a free license, DejaVu Sans. Then created a new empty glyph, and copy-paste one of its glyphs to the empty one.

However, I saw that the hinting for the two is not exactly the same. When viewing the two glyphs in a word processor, I saw a difference between the two. So how can I make an exact copy of a glyph? Should I also duplicate some information inside the font’s table? Any simpler solution?

Will hinting be necessary when 300dpi high-res screens are the standards?

With the high res screens coming closer, (http://www.macrumors.com/2011/05/12/samsung-2560x1600-tablet-lcd-paves-w...), I was wondering if hinting will still be necessary if fonts are rendered with the same quality as a magazine or a book on screen.

Fonts being vector based, even zooming in won't impair any quality, so I'm not really sure if hinting will be necessary when all computers and portable devices are built with high res screens.

Also, if hinting isn't necessary, will the font file be significantly lighter, allowing webfonts to include more otf features like ligatures?

Thanks for your inputs on this :)

Could any Fontlab gurus help a novice with hinting?


So a couple of years ago, I made my first font, Yagi Double. Then I wanted to hint it, got scared when I saw the amount of work involved. Now I'm ready to try again but it STILL seems too tedious, like I'm missing something. What I've read so far on the subject:

As I understand it, you come up with an array of numbers representing the location of stuff like the baseline, cap height, x-height, etc. You feed these into two different areas in Fontlab. With an inline font like this, there are twice as many of these numbers. It's a lot of hassle.

1. Does this really produce good hinting results at the end, if I could force myself to do it properly?

Hinting, Helvetica, Nimbus Sans and CSS


Firstly, let me preface the post by saying that I am a complete newbie at everything pertaining to fonts, type, css or design, so please, be gentle.

The story thus far is as follows:

I'm designing a web page for a few friends (and myself), so that we have something (anything) online until our organisation has the funding to get a better page up and running. Luckily, I'm not doing the coding, a friend of mine is.

Font hinting on iPad?

Does iPad make any use of font hinting, if available, please? I mean not just safari browser, but the device itself, e.g. in purchased apps.

As far as I know, the CoreText rendering engine on Mac OS X completely ignores font hinting and rather employs subpixel antialiasing (source: http://www.typotheque.com/articles/hinting).

However, iOS devices do not use subpixel antialiasing (probably due to portrait/landscape orientation switching) and do only standard "grayscale" antialiasing, which obviously leads to less precise results. So I am wondering whether or not do they make any use of font hinting (to compensate this)?

optimizing font for small size on a mac?


I'm trying to optimize my font for small, set sizes on-screen (9pt, 11pt, 13pt) specifically for osx. i don't know very much about font-exporting and the rasterization process, but i'm told that i font-hinting doesn't work on osx because quartz doesn't listen to the hints. is there any other method of optimizing fonts for small sizes on macs? the only other solution i can think of is to make separate font files for each size… and that just seems downright sloppy.

sorry this is a bit of a novice question, but my usual solution of scouring the internet for an answer hasn't been pointing me in any helpful directions.

thanks in advance!

Optimal rendering in browsers


I am having an issue with a font in development, and it is this: The vertical stems are too irregular in width/colour/weight when they are rendered in webbrowsers like Safari or Firefox in OS X. Firefox is marginally better than Safari. A PDF has the same issue, but to a lesser degree. All the stems in question are of exactly the same width. Other fonts like Ariel or other webfonts do not show this issue. I tried both CFF/OTF and TTF, but they both have the same issue. This leads me to think there is some hinting setting I have borked, but OS X does not use hinting, so huh? What can be wrong? I'm working with a UPM of 2048, but I seem to remember making a test in 1000, and that had the same issue.

I'll be grateful for any pointers, hints, puns.