<html><head></head><body><div class="ydp67138606yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>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.</div><div><br></div>
<div id="ydp67138606yahoo_quoted_1654578839" class="ydp67138606yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, 5 November 2018, 21:53:48 GMT+8, Byeongsik Jeon <bsjeon@hanmail.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On Mon, 5 Nov 2018 13:32:18 +0300, Dmitry Timoshkov <<a shape="rect" href="mailto:dmitry@baikal.ru" rel="nofollow" target="_blank">dmitry@baikal.ru</a>><br clear="none">wrote:<br clear="none">> It's not reasonable to expect application developers to dive into this<br clear="none">> kind of very specific and technical details. Developers just expect that<br clear="none">> things work. This is how it works under Mac and Windows.<br clear="none">><br clear="none">I'm not saying that all application developers should do this.<br clear="none">Also, the developers does not need to do this on Mac or Windows. Because<br clear="none">it works as they expected.<br clear="none"><br clear="none">This solution is a way to fit the definition of the gasp table.<br clear="none">Unlike general application development, it is not a special technique in<br clear="none">the development that directly accesses the fonts.<br clear="none"><br clear="none">>><br clear="none">>> Interpreter_version = gasp_version ? 40: 35;<br clear="none">> <br clear="none">> If that's this simple why freetype can't do that on its own?<br clear="none">> <br clear="none">It is an option to decide how to operate. Even if the Freetype does it<br clear="none">automatically, the Freetype should be made selectable it. If the action<br clear="none">is not matched to Windows, we will have to consider another solution.<br clear="none"><br clear="none">Is it a problem that it solve the problem using the API provided by the<br clear="none">Freetype? It is a solution that can be widely applied to the Freetype<br clear="none">already distributed, including MacOS XQuartz v2.7.11.<br clear="none"><br clear="none">This problem may be solved in some next version of the Freetype. Then we<br clear="none">can add some patch. But the patch for the past versions will still need.<div class="ydp67138606yqt5660378099" id="ydp67138606yqtfd82938"><br clear="none"><br clear="none">> <br clear="none">> There is nothing special in fonts handling that Wine does that other applications<br clear="none">> don't or can't do.</div><br clear="none">> <br clear="none">A typical Linux application does not refer to the gasp table. But isn't<br clear="none">the Wine already referring to it?<br clear="none"><br clear="none"><br clear="none">I didn't think this solution would be a controversial issue. Maybe it's<br clear="none">the result of my awkward English expression. In fact, I don’t think I’ve<br clear="none">heard an answer that makes sense to why this solution is wrong.<br clear="none"><br clear="none">This can be solved by Wine, even if it is not a bug caused by Wine<br clear="none">itself. Then the effect is more extensive.<br clear="none">I am grateful for the comments.<div class="ydp67138606yqt5660378099" id="ydp67138606yqtfd74358"><br clear="none"><br clear="none"><br clear="none"><br clear="none"></div></div></div>
</div>
</div></div></body></html>