w3c / w3c/mathml-core

largeop ascent/descent when using a vertical glyph assembly

Open
#55 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-tests
Dominant language
HTML
Stars
56
Forks
20
PR merge metrics
No merged PRs in 30d

Description

From https://docs.microsoft.com/en-us/typography/opentype/spec/math:

"Note that for assemblies growing in the vertical direction, the distribution of height between ascent and descent is not defined. The math-layout engine is responsible for positioning the resulting assembly relative to the baseline."

Per https://mathml-refresh.github.io/mathml-core/#the-glyphassembly-table there are two cases:

(1) "Set B to the advanced width, ascent and descent of the glyph of id MathGlyphVariantRecord.variantGlyph. "

(2) "If there is valid GlyphAssembly subtable then set B to the glyph assembly width, glyph assembly ascent and glyph assembly descent for the target size T." which is itself "If GlyphAssembly is vertical, the width is the maximum advance width of the glyphs of id GlyphPartRecord.glyphID for all the GlyphPartRecord in GlyphAssembly.partRecords, the ascent is the glyph assembly stretch size for a given target size T and the descent is 0."

So in case of a largeop glyph assembly, the descent is always 0. I don't think people care about this case, but just opening to be sure...

(For stretchy glyph assembly the ascent/descent of the mo is later calculated from the non-stretchy siblings)

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

Read the OpenType MATH and MathML Core glyph assembly sections cited in the issue, comparing vertical largeop and stretchy cases. Confirm the intended ascent/descent behavior and document the agreed clarification in the specification; no repository file or test is named.

Written by the indexing model from the issue text.

Assessment

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.