Re: Infinality removal (Freetype-devel Digest, Vol 299, Issue 99)
> 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 time soon. Well, I invite you to have a closer look if we are going to handle that :-) Werner
Re: Infinality removal (Freetype-devel Digest, Vol 299, Issue 99)
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 GETINFO section of the infinality diff which is not in the alternative code path. The alternative simply does not mention anything missing. 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 time soon. FWIW, those two "not yet unimplemented" features have been not yet unimplemented for 20 years :-).
Re: Infinality removal (Freetype-devel Digest, Vol 299, Issue 99)
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_INTERPRETER_VERSION_38 or FT_Property_Set in your Font-Validator repository. I was actually curious how it is useful to you. Are you sure that you use it? Please help me understand how you prefer v38 to v40. Even if you assume that v38 is very popular, please explain why you think so. I am actually very interested to find out. Thank you very much in advance. No, it is not all the same to me. I care very much that Infinality makes it a lot harder to maintain the FreeType code base. Infinality is very invasive and to my knowledge nobody touched it with a 6 foot long pole once it was merged. The author disappeared. My experience was that v40 has the same quality but a lot faster. That is our default for 6 years now. Full verbatim v35 hinting is here to stay, of course. If there is no misunderstanding here, this might actually be a good idea to maintain Infinality as an external patch. Paradoxically, this might actually create better support and community around it. Best regards, Alexei
Re: Infinality removal (Freetype-devel Digest, Vol 299, Issue 99)
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 Compat/Compat.cs, and does switch between 35 and 40 . And I have always built it with 38 enabled just in case there is any difference between 40 and Microsoft's, and I want to try 38. Microsoft's code for 37 is leaked and is somewhere on the Internet...
Re: Infinality removal (Freetype-devel Digest, Vol 209, Issue 11)
I wonder how well it really matches? As far as I remember, it does something superficially similar but the actual MS rasterizer works differently?
Re: Infinality removal (Freetype-devel Digest, Vol 209, Issue 11)
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 removal (Alexei Podtelezhnikov) 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 interpreter version 40 has been FreeType's default version for 6 years now and provides an excellent alternative. This is the last FreeType version with TT_INTERPRETER_VERSION_38 and TT_INTERPRETER_VERSION_40 treated differently. https://gitlab.freedesktop.org/freetype/freetype/-/commit/5e48c88d57a89ea7a4fda1b31f4b7fb756dd1732 Please voice any concerns that you might have with this impending change.
Infinality removal
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 interpreter version 40 has been FreeType's default version for 6 years now and provides an excellent alternative. This is the last FreeType version with TT_INTERPRETER_VERSION_38 and TT_INTERPRETER_VERSION_40 treated differently. https://gitlab.freedesktop.org/freetype/freetype/-/commit/5e48c88d57a89ea7a4fda1b31f4b7fb756dd1732 Please voice any concerns that you might have with this impending change. Alexei
Infinality removal
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 interpreter version 40 has been FreeType's default version for 6 years now and provides an excellent alternative. This is the last FreeType version with TT_INTERPRETER_VERSION_38 and TT_INTERPRETER_VERSION_40 treated differently. https://gitlab.freedesktop.org/freetype/freetype/-/commit/5e48c88d57a89ea7a4fda1b31f4b7fb756dd1732 Please voice any concerns that you might have with this impending change. Alexei
