> WL> OK. So FreeType should obey the `gasp' table by default? Or
> should WL> this be a new FT_LOAD flag? Or a rendering flag?
>
> Please not by default. I *NEVER* want monochrome rendering when I
> use aa.
But some fonts are *designed* to obey the gasp table! In particular
there are fonts
> WL> Is it really `spotty'? I've never tested it, ...
>
> Try (a modern version of) gnu emacs to give libotf a whirl.
I use it all the time, but I have no knowledge about complex scripts
like Arabic or Khmer.
Werner
___
Freetype-devel mailing
> "WL" == Werner LEMBERG writes:
WL> Is it really `spotty'? I've never tested it, ...
Try (a modern version of) gnu emacs to give libotf a whirl.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
___
Freetype-devel mailing list
Freetype-dev
> "WL" == Werner LEMBERG writes:
WL> OK. So FreeType should obey the `gasp' table by default? Or should
WL> this be a new FT_LOAD flag? Or a rendering flag?
Please not by default. I *NEVER* want monochrome rendering when I use aa.
I'm far from alone in that preference.
I still think fo
Hi,
I have a CFF font with a BlueScale value of 48.
FreeType stores this value *1000 in a FT_Fixed.
Which causes an overflow resulting in a negative number.
cfftoken.h:
CFF_FIELD_FIXED_1000( 0x109, blue_scale, "BlueScale" )
As far as I can tell this value is only used in pshglob.c,
psh_blues_sca
