RE: [External] Aw: Re: Re: Re: Re: Native TTF name sometimes contains crap

[Boppe, Balakrishna (D&G COE)]

Hi,

We want to create fonts using  pixelsize of the order of 14, which would 
eventually be displayed on DPI 114 display device. However, the fonts are not 
looking smoother at this pixel size.

Any special settings that we need enable make the fonts smoother ? Like 
sub-pixel rendering enable OR HINTING or anything.

Please provide the guidance!

Thanks,
Bala.

-----Original Message-----
From: Freetype <freetype-bounces+balakrishna.boppe=honeywell.com@nongnu.org> On 
Behalf Of virtual_worlds@gmx.de
Sent: Monday, September 6, 2021 10:44 AM
To: Werner LEMBERG <wl@gnu.org>
Cc: freetype@nongnu.org
Subject: [External] Aw: Re: Re: Re: Re: Native TTF name sometimes contains crap

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Please find the ftdump output and the related font attached.

Mike



> Gesendet: Sonntag, 05. September 2021 um 04:26 Uhr
> Von: "Werner LEMBERG" <wl@gnu.org>
> An: virtual_worlds@gmx.de
> Cc: freetype@nongnu.org
> Betreff: Re: Aw: Re: Re: Re: Native TTF name sometimes contains crap
>
> > Yes, for sure, hex values are more accurate. > > So ftdump returns 
> > "\U+009E\U+004F" which is the correct name, so > ftdump is doing something 
> > I do not know about. > > When I call the get-name-function as shown, the 
> > returned value is > 0x7e 0xd1 0x4f 0x53 I guess it's rather 0xb8 0xd1 0x4f 
> > 0x53 right? > So when it is a Mojibake-problem - is ftdump workarounding 
> > this? If > yes: how? Please send me the problematic font off-list. It's too 
> > hard otherwise to analyze the issue. Werner