w3c / w3c/mathml-core

Explain how to use the MathKernInfo table

Open
#134 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

level-2 MathML Core need specification update need tests opentype / tex
Dominant language
HTML
Stars
56
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Just importing this from gitlab, but I think it's not a priority for now.

"I'm opening this for a future version of the implementation note. The fonts made by the GUST e-foundry group do not contains any kerning values for scripts.
The MathKernInfo table provides additional kerning corrections when positioning scripts. The choice of kern values depend on the vertical offsets of scripts and so it seems that it will make preferred widths depend on vertical metrics of MathML boxes. However, these kerning rules only apply in the simplified case where the base and scripts are just single glyph (not complex subformulas) and so it's possible to determine the vertical shifts immediately during the "preferred width calculation" phase.
Some cases to consider:

Base with many pre/post scripts (mmultiscripts)
Base/Scripts that contains a single glyph nested in mrow-like elements"

Original report: https://gitlab.com/mathml/MathMLinHTML5/issues/11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the MathKernInfo description in this issue and read the linked GitLab report for the original context. The work is done when an implementation note explains how the table affects script positioning and preferred-width calculation, including multiscripts and single-glyph scripts nested in mrow-like elements.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.