<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr">
<p></p>
<div>Well the modifided tcl AFAWCT gives uniform patch rendering on all OS with the same font.</div>
<div><br>
</div>
<div>Also this tweek is compatible with Purr-Data.</div>
<div><br>
</div>
<div>It came from a long discussion we had with Alex, he was mad cuz his help-patches done on OSX were bad on linux & windows.</div>
<div><br>
</div>
<div>We concluded that:</div>
<div><br>
</div>
<div>Each OS was using a different font: dejavu:linux, monaco:macOS, courier:windows.</div>
<div><br>
</div>
<div>So we started testing all on DejaVU and we still got his help-patches bad.</div>
<div><br>
</div>
<div>Then we use extended metrics and “All solved”.</div>
<div><br>
</div>
<div>Obscure why vanilla:monaco:osx fits for vanilla:dejavu:linux:mod.tcl</div>
<div><br>
</div>
<div>But anyway this tcl mod renders perfectly patches that were done with extended, or with Purr-Data.</div>
<div><br>
</div>
<div>GOP needs testing, but surely vanilla will behave as if it was extended.</div>
<div><br>
</div>
<div>Only changes are :</div>
<div>@ pd-gui.tcl line 127 you will find the Pd vanilla font metrics </div>
<div><br>
</div>
<div>The actual real pixel dimensions of the font are none of our business and irrelevant cuz patches render the same or really close on all OS.</div>
<br>
<p></p>
<p><br>
</p>
<div id="Signature"><font face="Courier New, Courier, Monospace" size="2">Mensaje telepatico asistido por maquinas.</font>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Jonathan Wilkes <jancsika@yahoo.com><br>
<b>Sent:</b> Monday, February 20, 2017 5:16 PM<br>
<b>To:</b> Lucas Cordiviola; pd-list@lists.iem.at<br>
<b>Subject:</b> Re: [PD] (wip) Preferences file.</font>
<div> </div>
</div>
<div>
<div style="color:#000; background-color:#fff; font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<br>
<div class="qtdSeparateBR"><br>
<br>
</div>
<div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1487610391847_3116" style="display:block">
<div id="yui_3_16_0_ym19_1_1487610391847_3115" style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<div id="yui_3_16_0_ym19_1_1487610391847_3114" style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif; font-size:16px">
<div class="y_msg_container" id="yui_3_16_0_ym19_1_1487610391847_3145"><i id="yui_3_16_0_ym19_1_1487610391847_3174">>> But you are taking an internal format passed between the GUI and the core and exposing it to </i><span style="font-size:12pt"><i>become a
public API. And that format virtually guarantees that users will misunderstand how it works:</i></span>
<div id="yiv2318163514">
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3144">
<div dir="ltr" id="yiv2318163514divtagdefaultwrapper" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<blockquote id="yui_3_16_0_ym19_1_1487610391847_3176" style="margin:0 0 0 40px; border:none; padding:0px">
<div></div>
</blockquote>
<div></div>
<div><span style="font-size:12pt"><i></i></span></div>
<div id="yui_3_16_0_ym19_1_1487610391847_3173"><br clear="none">
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3143">> Ok, so then a new flag?</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3469"><br clear="none">
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3468">> -fontmetrics <name> … vanilla or extended</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3467"><br clear="none">
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3179">> Or something like that?</div>
<div></div>
<div id="yui_3_16_0_ym19_1_1487610391847_3221"><br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3515">I'm still not convinced anyone actually understands what the font sizing algorithms are doing,
<br>
</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3516">or whether they are indeed buggy. Under those circumstances I don't think it's a good idea
<br>
</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3517">to expose a new setting to the user.<br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3518"><br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3519">Has anyone actually read the handful of relevant procs/functions responsible
<br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3520">for the sizing?<br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3521"><br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3522">For example-- if you choose "12" in Pd's font size dialog, the actual pixel size for the
<br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3710">font displayed on the tk canvas could be -11, -12, -13, etc. Are the discrepancies in
<br>
</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3721">your screenshots due to different actual pixel sizes, or did you normalize everything
<br>
</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3722">to the same actual pixel font size?</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3723"><br>
</div>
<div dir="ltr" id="yui_3_16_0_ym19_1_1487610391847_3724">-Jonathan<br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3725"><br>
</div>
<div id="yui_3_16_0_ym19_1_1487610391847_3726"><br>
</div>
<div id="yiv2318163514Signature"><font id="yui_3_16_0_ym19_1_1487610391847_3727" size="2" face="Courier New, Courier, Monospace">> Mensaje telepatico asistido por maquinas.</font>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>