Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Hin-Tak Leung

About

Username
Hin-Tak Leung
Joined
Visits
1,040
Last Active
Roles
Member
Points
99
Posts
265
  • Re: Color will be the new Italic. Color will be the new Bold.

    You are aware that up to 8% of Caucasian males and 1% of Caucasian females have some degree of red-green color blindness? It is one of the most widely-known and common X-linked inherited illnesses. "X-linked" as in located on the X chromosome - males has one and female two, so female can be carrier without being affected.

    So one always have to be careful about relying on color to convey information - for example, if you use green-on-red for emphasis, it might have the opposite effect: a substantial part of the general population simply see it as redacted.

    I am also of the opinion that legibility comes first - ornamental to the extent of sacrificing legibility isn't.
  • Re: Google Fonts freelance font engineering remote contract (summer 2017)

    I wouldn't object to somebody (or me) spending some time uptreaming the new rasterisation backend of FontVal and creating a python binding to that freetype diagnostics code on the way, and share it with fonttools. It is just that I would not move it away from being FontVal-friendly, which is what I am afraid of if I put the code out in the open too early.
  • Re: making-fonts-proza-libre

    I didn't want to post until I have done the mac os x binary, but I 'd be interested if ttfautohint'ed fonts passed the rasterisation test in font validator 2.0 or not.

    If you have a windows computer, or brave enough to use wine on Mac/linux - just grab either 2.0.0-bin-net2 or 2.0.0-bin-net4 from https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft Font Validator/
  • Re: making-fonts-proza-libre

    @Mike Duggan : Your colleague

    @Jason Campbell raise an interesting point : is it better or worse to use a hinting tool ttfautohint (based on FreeType), to hint for fonts targeting another rendering engine (Microsoft's), or using MS VTT to build libre fonts targeting platforms where Freetype is used for rendering; or should one always use the same tool set for the platform concerned. i.e. MS VTT for fonts used on MS platforms, ttfautohint for non-MS ones.

    That was the question he was asking: can one use a hint-checking tool built around one engine to check hinting errors from tools targeting another. One might argue it is better: no secret knowledge working around each others' bugs.


  • Re: making-fonts-proza-libre

    So I am interested in whether there is any secret by-passes and overlooks between ttfautohint and the new rasterization test in Font Validator 2.0 (both based on Freetype).