A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/adobe-type-tools/afdko/issues/655 below:

[tx] Bounding box not calculated correctly when start point is on right most edge of bounding box · Issue #655 · adobe-type-tools/afdko · GitHub

When looking for the answer for why comparefamily was incorrectly reporting bogus stems for a typeface, I realized that with a glyph like so:

<?xml version="1.0" encoding="UTF-8"?>
<glyph name="guilsinglright" format="1">
  <advance width="0"/>
  <outline>
    <contour>
      <point x="261" y="202" type="line"/>
      <point x="261" y="227" type="line"/>
      <point x="77" y="435" type="line"/>
      <point x="74" y="435" type="line"/>
      <point x="40" y="386" type="line"/>
      <point x="40" y="383" type="line"/>
      <point x="182" y="202" type="line"/>
      <point x="40" y="25" type="line"/>
      <point x="40" y="22" type="line"/>
      <point x="58" y="-5" type="line"/>
      <point x="61" y="-5" type="line"/>
    </contour>
  </outline>
</glyph>

the bounding box gotten by comparefamily with tx from here:

cmpfFont.metricsDict = {}

has the bounding box at 236, not 221 like it should be. This seems consistent with glyphs that have their start point on the right edge.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4