Author Topic: [4692 win] TT Hinting broken  (Read 641 times)

Luc[as]

  • Beta: FontLab Studio Win
  • Hero Member
  • ***
  • Posts: 295
    • LucasFonts
[4692 win] TT Hinting broken
« on: 2013-02-07, 06:02:58 »
TT hinting does not work when "[v] use custom [cmap] encoding" is switched on, doesn't make any sense does it?

Adam Twardoch (FontLab)

  • Product and marketing manager, Fontlab Ltd.
  • Administrator
  • Hero Member
  • *****
  • Posts: 566
  • FontLab Studio 5.1.2, Mac OS X 10.6.8
    • FontLab
Re: [4692 win] TT Hinting broken
« Reply #1 on: 2013-02-21, 12:54:31 »
Indeed it doesn't.

I would advise not using the "Use custom cmap encoding" option. We added it to FontLab Studio 5 but now consider it deprecated. Rewriting the "cmap" table into some custom stuff should be done on a post-processing level, using tools such as DTL OTMaster or ttx.
Regards,
Adam Twardoch
Fontlab Ltd.

Luc[as]

  • Beta: FontLab Studio Win
  • Hero Member
  • ***
  • Posts: 295
    • LucasFonts
Re: [4692 win] TT Hinting broken
« Reply #2 on: 2013-02-22, 06:50:10 »
Huh? You mean that even though FontLab has an interface for this job we shouldn't use it and do it by hand in another tool? Can you explain why? Is FontLab doing it wrong?

Anyway, I am not writing the "cmap" table into some custom stuff, but just add a standard cmap this way which is needed to make TTF fonts run on Macs as well.

Adam Twardoch (FontLab)

  • Product and marketing manager, Fontlab Ltd.
  • Administrator
  • Hero Member
  • *****
  • Posts: 566
  • FontLab Studio 5.1.2, Mac OS X 10.6.8
    • FontLab
Re: [4692 win] TT Hinting broken
« Reply #3 on: 2013-02-22, 09:41:28 »
1. Which cmaps are you adding? 1.0? 0.3? Any other?

2. Does the default FLS behavior produce TTFs which are in some way no good for Mac OS X? Could you please elaborate why you need the custom cmap setting?

Thanks,
Adam
Regards,
Adam Twardoch
Fontlab Ltd.