Unclear how to use `Operators_fence` special table
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 56
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
The Operators_fence special table has the entry {U+0331}, which taken at face value is the code point for a combining below macron. But that is clearly not a fence. It is, however, what you get for the content string "||" after applying Step 2.3 of the algorithm to determine the category of an operator.
Should this table then be utilized by first applying the above replacement to an input string before performing a lookup, or is this the only exception? Regardless of the answer, I think a comment explaining it should be added to the spec.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the Operators_fence special table and the linked Step 2.3 algorithm in the MathML Core specification. Determine whether lookup should apply the replacement to the input or treat U+0331 as an exception, then add a comment explaining the decided behavior in the specification.
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
- 35/100