<div dir="auto">Correct. The checksum algorithm should say implementations should pad table data with zero bytes sick that data length becomes a multiple of four before performing checksum algorithm. The actual bytes following a table must NOT be used. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 31, 2020, 11:39 AM Peter Constable <<a href="mailto:pgcon6@msn.com">pgcon6@msn.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div class="m_-508107530783230923WordSection1">
<p class="MsoNormal">If we don’t make that a requirement, then the stated algorithm for calculating a checksum must explicitly and unambiguously allow for data in which tables are not four-byte aligned. Otherwise software implementers (“consumers”) are faced
with ambiguity.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Behdad Esfahbod <<a href="mailto:behdad@behdad.org" target="_blank" rel="noreferrer">behdad@behdad.org</a>> <br>
<b>Sent:</b> Monday, August 31, 2020 10:36 AM<br>
<b>To:</b> Peter Constable <<a href="mailto:pgcon6@msn.com" target="_blank" rel="noreferrer">pgcon6@msn.com</a>><br>
<b>Cc:</b> MPEG OT Spec list (<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank" rel="noreferrer">mpeg-otspec@lists.aau.at</a>) <<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank" rel="noreferrer">mpeg-otspec@lists.aau.at</a>><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] checksum / 4-byte table offset weasel wording<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">I suggest we *recommend* that tables start at 4byte offsets, since that makes access faster on some hardware. But otherwise no requirement at all, since all implementations have to be prepared to handle non-aligned tables.<u></u><u></u></p>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">behdad<br>
<a href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbehdad.org%2F&data=02%7C01%7C%7C0c63f7c7416e4cc9f99f08d84dd45c70%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637344921757739154&sdata=xdZzVqn%2Bb%2BOwMbnPKs2QIgjfYtAlrG9dLAeJdnoOOgo%3D&reserved=0" target="_blank" rel="noreferrer">http://behdad.org/</a><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Mon, Aug 31, 2020 at 9:41 AM Peter Constable <<a href="mailto:pgcon6@msn.com" target="_blank" rel="noreferrer">pgcon6@msn.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span lang="EN-CA">Currently the OT spec / OFF as well as Apple’s spec are somewhat ambiguous wrt the need for top-level tables to begin at offsets that are integral multiples of
four bytes.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"><a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.apple.com%2Ffonts%2FTrueType-Reference-Manual%2FRM06%2FChap6.html&data=02%7C01%7C%7C0c63f7c7416e4cc9f99f08d84dd45c70%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637344921757739154&sdata=ermVJuT%2F4oXstF1DZsR3yNutdfZ2pm9R6yTwo8qqxU0%3D&reserved=0" target="_blank" rel="noreferrer">Apple’s
spec</a> gives the algorithm to calculate a checksum for a table, which sums 32-bit chunks. This doesn’t necessarily imply that table lengths must be multiples of four (it could consume the first one to three bytes of a following table) except in the case
of the last table in the file—there’s no allowance in the algorithm for reaching EOF before reaching the table length. But allowing checksum for one table to count bytes from a following table would seem odd. It could alco create confusion when calculating
a checksum for the file as a whole: <i>Do overlapping bytes get counted twice?</i></span><u></u><u></u></p>
<p class="MsoNormal"><i><span lang="EN-CA"> </span></i><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA">The
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftypography%2Fopentype%2Fspec%2Fotff%23calculating-checksums&data=02%7C01%7C%7C0c63f7c7416e4cc9f99f08d84dd45c70%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637344921757749151&sdata=GU0CWCNElMkxRoE26oHHJ%2Biv9jhpJTnmDq3IonZMIV8%3D&reserved=0" target="_blank" rel="noreferrer">
section on calculating checksums in the OT spec</a> and in OFF give the same algorithm, but add a following note:</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">
<span lang="EN-CA">“</span><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#171717;background:white">This function implies that the length of a table must be a multiple of four bytes. In fact, a font is not considered structurally well-formed
without the correct padding. All tables must begin on four-byte boundaries, and any remaining space between tables is padded with zeros. The length of all tables should be recorded in the table record with their actual length (not their padded length).</span><span lang="EN-CA">”</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA">That seems like a clearly-stated requirement. But if four-byte alignment is a requirement, it shouldn’t be stated here as an implication of the checksum adjustment;
it should be stated in the description of table records within the table directory.</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA">But then in the
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Ftypography%2Fopentype%2Fspec%2Frecom%23table-alignment-and-length&data=02%7C01%7C%7C0c63f7c7416e4cc9f99f08d84dd45c70%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637344921757749151&sdata=dF2nHCQfXihSoS0omH6AD6C66yHgbGjWpC5HmglP5LU%3D&reserved=0" target="_blank" rel="noreferrer">
Recommendations section</a> of OT/OFF, four-byte alignment is mentioned as a _<i>recommendation</i>_, not a requirement:</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="EN-CA"> </span><u></u><u></u></p>
<p style="margin-left:.5in;background:white"><span lang="EN-CA" style="color:black">“</span><span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#171717">All tables should be aligned to begin at offsets which are multiples of four bytes. While
this is not required by the TrueType rasterizer, it does prevent ambiguous checksum calculations and greatly speeds table access on some processors.</span><u></u><u></u></p>
<p style="background:white;box-sizing:inherit;margin:1rem 0px 0px;outline-color:inherit;font-variant-ligatures:normal;font-variant-caps:normal;text-align:start;text-decoration-style:initial;text-decoration-color:initial;word-spacing:0px">
<span style="font-size:12.0pt;font-family:"Segoe UI",sans-serif;color:#171717">“All tables should be recorded in the table directory with their actual length. To ensure that checksums are calculated correctly, it is suggested that tables begin on 32-bit boundaries.
Any extra space after a table (and before the next 32-bit boundary) should be padded with zeros.</span><span lang="EN-CA" style="color:black">”</span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black">This is all weasel wording. Either four-byte alignment (with zero padding as needed) should be required, and the checksum calculation be stated is now—easily. Or, four-byte alignment should
not be required, but the description for calculation of checksums should be elaborated to cover edge cases unambiguously.</span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black">As allowing for the edge cases adds non-trivial complication, both in the description and in implementations, I’m inclined to make it a requirement that tables begin at four-byte-multiple offsets
(and remove the weasel wording in the Recommendations section).</span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black">Either way, there would be one possible edge case that should be covered: the last table in a file, and how to calculate a checksum if the table length is not a multiple of four. My inclination
would be to cover this —which would also cover the general case — by saying that, if a table length is not a multiple of four, then it must be padded with zero bytes to the next four-byte boundary.</span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black">Would this break any assumptions in current runtime or tool implementations to make this a clear requirement?</span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black"> </span><u></u><u></u></p>
<p style="background:white"><span lang="EN-CA" style="color:black">Thanks<br>
Peter</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at" target="_blank" rel="noreferrer">mpeg-otspec@lists.aau.at</a><br>
<a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.aau.at%2Fmailman%2Flistinfo%2Fmpeg-otspec&data=02%7C01%7C%7C0c63f7c7416e4cc9f99f08d84dd45c70%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637344921757759143&sdata=P5b61S%2FFCc2s%2FsHVl%2FMX3uQnTs01CgaU%2FeEGvRG76O0%3D&reserved=0" target="_blank" rel="noreferrer">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</blockquote></div>