On Mon, 5 Nov 2018 14:33:35 +0000 (UTC), Hin-tak Leung hintak_leung@yahoo.co.uk wrote:
On Monday, 5 November 2018, 22:16:56 GMT+8, Byeongsik Jeon bsjeon@hanmail.net wrote:
On Mon, 5 Nov 2018 14:06:32 +0000 (UTC), Hin-tak Leung <hintak_leung@yahoo.co.uk mailto:hintak_leung@yahoo.co.uk> wrote:
There is no need for application using freetype to change the interpreter version at compile time - you can do that at runtime by setting the FREETYPE_PROPERTIES environment variable. This was introduced in freetype 2.7/2.8-ish.
When you fix the interpreter version, it does not satisfy both types of the fonts together.
The idea of FREETYPE_PROPERTIES is that you should choose on an application-by-application basis. And maybe also that using Microsoft's Tahoma instead of wine's is a bad idea?
On Mon, 5 Nov 2018 17:17:04 +0900, Byeongsik Jeon bsjeon@hanmail.net wrote:>
The problem arises in native Tahoma. MacOS has Tahoma builtin. and Wine's Tahoma has a low priority.
In the Freetype interpreter version 40, the native Tahoma returns a different glyph metrics than Windows GDI.
This patch is about the situation in which one application uses Tahoma and Consolas together. Also, make sure you do not need to add individual settings based on the font type.
Arial, Courier New, etc. These fonts have the same problem, though there are differences in degree.
You are basically advocating switching the interpreter version based on font vintage/age , using a heuristics on the presence/absence of a table to tell you how old a font is. I think that is bad. Fix the font, or using a better way of telling the age of a font :-).
The gasp table is not like that. It is the information that reflects the intention of the font creator.