<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 04/10/2020 18:05, Martin Frb wrote:<br>
</div>
<blockquote type="cite"
cite="mid:f855618b-62eb-e9b9-6434-d97548774f3f@mfriebe.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 04/10/2020 10:14, Mr Bee wrote:<br>
</div>
<blockquote type="cite"
cite="mid:125995113.1541726.1601799288108@mail.yahoo.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div class="ydpe3779a4eyahoo-style-wrap"
style="font-family:Helvetica Neue, Helvetica, Arial,
sans-serif;font-size:16px;">
<div>
<div dir="ltr" data-setdir="false">If it does work, would
you please submit it as a patch for the next release? At
least, add a note that the font ligatures feature only
supports monospaced fonts and only works on Windows. It's
better than nothing.</div>
<br>
</div>
</div>
</blockquote>
revision 63951<br>
<br>
Windows only, compile with -dWINDOWS_LIGATURE<br>
Tested with Cascadia.<br>
</blockquote>
<br>
I did add a couple of checks. Amended it for right to left languages
(Arabic).<br>
<br>
Arabic only works with certain fonts. <br>
And Japanese Katakana seems not to work at all (or I have not found
a supporting font, while without this feature it works with "Deja
Vue" and others).<br>
<br>
It appears that this API restricts Windows font substitution
abilities.<br>
It might be that in order for all this to work, one has to use the
newer "uniscribe" API.<br>
<br>
I also kind of assume that in the current IFDEF code the use of the
DX array (ETO) is wrong. But I could not produce any errors from
that / And it only would happen if NeedETO = True.<br>
<br>
So for the moment, this stays highly experimental.<br>
<br>
</body>
</html>