Plex Math: pieces of horizontal stretchy brackets and double arrows snap to different pixel rows

オープン
#738 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
46/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
tex
領域
design

調査の方向性

The issue identifies uni23DE.lft, uni23DE.ext and uni23DE.mid and reports similar joins in other horizontal assemblies; it does not name source files or tests. Start by locating the font source and instructions for these glyphs, then reproduce the reported joins at the listed sizes with hinting enabled. Done means the shared strokes align across the tested assemblies without losing crispness or creating brighter pixels at joins.

索引モデルが issue の本文から書いたものです。

説明

In IBM Plex Math 1.1.0 (@ibm/plex-math on npm), the pieces of several horizontal stretchy glyphs hint the same stroke with different programs. At many sizes the hinted stroke of the extender lands exactly one pixel above or below the stroke of the end or middle piece next to it, so the assembled glyph has a step at each join. I see this in Chrome and Firefox on Windows on a 1080p screen, both at text sizes and under pinch zoom.

U+23DE (top curly bracket) is an example. The outlines of uni23DE.lft, uni23DE.ext and uni23DE.mid all put the stroke at y = 714 to 780. lft and mid have their own instructions (44 and 68 bytes). ext is a reference to uni23B4.ext, the extender of U+23B4, and uses its 11 bytes of instructions. The three programs round the shared stroke to different pixel rows at some sizes.

Here is U+23DE at 20 px, rendered with FreeType with hinting on and magnified. The top row is the original font; the bottom row is the same font rehinted with ttfautohint, discussed below.

Image

I rendered every horizontal assembly in the MATH table with FreeType, hinting on, from 14 to 80 px in 0.25 px steps, and compared the stroke height on both sides of each join. These have 1 px steps:

Glyphs Sizes with a step (of 265)
U+21DA, U+21DB (triple arrows) 83
U+23B5, U+23DD, U+23DF, U+23E1 (bottom brackets) 63
U+23B4, U+23DC, U+23DE, U+23E0 (top brackets) 52
U+21D0, U+21D2, U+21D4 (double arrows) 24

The single arrows, harpoons and combining marks have none. I didn't test the vertical assemblies: Windows and FreeType apply hints only in y, so their vertical strokes shouldn't be affected.

To reproduce, open this page on Windows at 100% scaling and look along the rows for steps in the brace:

<!doctype html>
<meta charset="utf-8">
<style>
@font-face { font-family: "IBM Plex Math"; src: url("https://cdn.jsdelivr.net/npm/@ibm/[email protected]/fonts/complete/woff2/IBMPlexMath-Regular.woff2") format("woff2"); }
math { font-family: "IBM Plex Math", math; }
</style>
<div id="rows"></div>
<script>
const sample = `<math><mover><mrow><mi>a</mi><mo>+</mo><mi>b</mi><mo>+</mo><mi>c</mi><mo>+</mo><mi>d</mi></mrow><mo stretchy="true">&#x23DE;</mo></mover></math>`;
for (let px = 14; px <= 22; px += 0.25)
  document.getElementById("rows").insertAdjacentHTML("beforeend", `<div style="font-size:${px}px">${px}px ${sample}</div>`);
</script>

What I tried on a local copy:

  • Removing all instructions makes the pieces line up, but the strokes get blurry at text sizes and the overlapping connectors show as brighter pixels at the joins.
  • Rehinting the whole font with ttfautohint at default settings removes the steps at all 265 sizes, but the stroke keeps its real thickness (about 1.3 px at 20 px) and turns grey across rows, as in the bottom row of the image.
  • With ttfautohint's strong stem snapping the stroke is crisp more often, but the steps come back (72 sizes for U+23DE).

So I don't think a generic autohinter can fix it. The pieces of each assembly would need to snap the shared stroke edges the same way, for example by rounding them against the same CVT entries.

主要言語
CSS
スター
11.8k
フォーク
626
平均マージ
1日 9時間
マージ済み PR(30日)
2

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

IBM/plex のほかの issue

IBM/plex の issue をすべて見る

似ている issue

Design の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。