> I hope some of these knowledge in comments, probably also alsewhere,
> are copied over before its removal. There are people who want to
> know what Apple/MS does which FreeType does not (yet), even if those
> corners are practically unimportant and/or nobody is doing anything
> about it any ti
For entirely unrelated reasons, I have looked at some of the related code in
the last few days. While most people are unlikely to miss any crucial
functionality since it is not even enabled in the default build, there are two
comments of the "this feature not yet implemented" kind in the GETIN
Dear Hin-Tak,
> If it is all the same to you, I'd prefer it to say, but I guess I'll end up
> maintaining a revert in the FontVal fork. There is incentive in the FontVal
> backend to keep this, to match the Microsoft rastering backend.
I could not find any references to Infinality or
TT_INTERP
On Thursday, 23 June 2022, 05:26:10 GMT+8, Alexei Podtelezhnikov
wrote:
> I could not find any references to Infinality or
TT_INTERPRETER_VERSION_38 or FT_Property_Set in your Font-Validator
repository.
The switch between different interpreter version is via _lib.PropertySet(...)
in
I wonder how well it really matches? As far as I remember, it does
something superficially similar but the actual MS rasterizer works
differently?
If it is all the same to you, I'd prefer it to say, but I guess I'll end up
maintaining a revert in the FontVal fork. There is incentive in the FontVal
backend to keep this, to match the Microsoft rastering backend.
=== original musicToday's Topics:
1. Infinality
Dear FreeType community,
We have just committed a forewarning about Infinality removal.
- TrueType interpreter version 38 (aka Infinality) that was first
introduced about 10 years ago in FreeType 2.4.11 is now deprecated
and slated to be removed in the next version. TrueType
