<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:'Courier New',monospace;">
<p>Karel:</p>
<p><br>
</p>
<p>Metapost and Metafont are using different resolution values.</p>
<p>Metafont uses the resolution of localfont, which is 600dpi on</p>
<p>my system. Mfplain uses an effective resolution of 3600dpi. This </p>
<p>produces much larger pixel values. A lower value of u# in your </p>
<p>file should have the same effect as reducing the resolution. </p>
<p><br>
</p>
<p>However, a few tests with u# = (1/6)mm# produce the same problem. </p>
<p>I am forced to agree that there is a bug either in mfplain.mp or </p>
<p>in metapost itself (or perhaps it is in me).<br>
</p>
<p><br>
</p>
<p>Regards,<br>
</p>
<p><br>
</p>
<div id="Signature">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px"><font face="Courier New" size="3">Daniel H. Luecking [luecking@uark.edu]
<br>
Graduate Coordinator<br>
Department of Mathematical Sciences<br>
1 University of Arkansas<br>
Fayetteville, AR, USA 72701-1201</font><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Karel Horák <horakk@math.cas.cz><br>
<b>Sent:</b> Monday, August 17, 2015 12:15 PM<br>
<b>To:</b> Daniel H. Luecking<br>
<b>Cc:</b> metapost@tug.org<br>
<b>Subject:</b> Re: [metapost] metapost tfm bug with mfplain</font>
<div> </div>
</div>
<div>Daniel H. Luecking napsal(a):
<blockquote type="cite">
<pre> Karel <a class="moz-txt-link-rfc2396E" href="mailto:horakk@math.cas.cz"><horakk@math.cas.cz></a> wrote:
</pre>
<blockquote type="cite">
<pre>To make things easier, I changed all the graphics into trivial
rectangles, the incorrect dimensions are still there in case of chars 44
and 45 (octal 36 and 37). The height of these two characters is much
smaller than their width but should be higher!
</pre>
</blockquote>
<pre>I think you mean octal 44 and 45 (which are decimal 36 and 37).
</pre>
</blockquote>
It depends on the reading, I wanted to say octals of decimals 36 and 37 :-)<br>
<blockquote type="cite">
<pre>I'm just guessing here, but when metaFONT writes a tfm file, all the
dimensions are required to be less than 4096.0. It is possible metaPOST
uses the same code for creating the tfm file and makes the same
requirement. In character 36,
show h;
produces 7935.29486. It is possible that bits above the twefth are
ignored and so 7935.29486 - 4096 = 3839.29486 would be used. Or it
is possible some other truncation method is used.
There is another factor that might be at work here: there is a limit on
the number of different character heights there can be in a tfm file. If
there are more than 15, some will be adjusted so that there are only 15.
Your file seems to have 18 different heights. A similar limit is imposed on
depths and widths.
</pre>
</blockquote>
You are of course true, but metafont gives correct tfm with some changes of heights but those are neglectable (some charht values had to be adjusted by as much as 1.10536pt). On the other hand metapost does not give any information about changing the heights
at all.<br>
<br>
Originally I generated metrics with metafont but preparing now a new edition of textbook I thought that it is not more necessary to compile the source twice:-)<br>
<br>
All the best,<br>
Karel <br>
<br>
<br>
</div>
</div>
</body>
</html>