w3c / w3c/mathml-core

manual linebreaking and indenting/supporting mo attrs

Open
#164 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The is related to w3c/mathml-core#127, but I feel that w3c/mathml-core#127 should (and so far is) about automatic linebreaking. However MathML 3 also has a number of attributes on mo that can be used for forced linebreaks and indentation. These can be useful for breaking at an = and aligning subsequent lines on them as in:
image

The linebreaking attributes from MathML 3 are given here; the indentation attributes are in the next subsection. To support the above functionality, the attributes that are needed are:
linebreak= 'newline'
linebreakstyle="before" | "after" | "duplicate" | "infixlinebreakstyle" (only before/after are high priority)
indentalign = "id" (other values are "left" | "center" | "right" | "auto" but not needed for manual indents)
indenttarget = idref

Maybe supporting indentshift would be useful also and easy to implement (just add to the left padding).

Supporting these attributes do not require any additional passes. Adding this support would be a good way to begin to support linebreaking.

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

Start with the MathML 3 linebreaking and indentation attribute sections linked in the issue, and compare the requested behavior with w3c/mathml-core#127. Done means supporting linebreak="newline", before/after linebreakstyle, indentalign="id", and indenttarget, with indentshift considered if practical.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.