w3c / w3c/mathml-core

Searching or matching text

Open
#220 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

In https://github.com/w3c/mathml-core/issues/219 , the reply states:

If the spec (or its implementation) allows searching or matching of text, including syntax and identifiers understand the implications of normalisation, case folding, etc. Also check the detailed guidance for Text-processing.

The spec does not address the searching or matching of text.

But maybe it one day should? Would knowing answers to questions such as:

  • Should the ascii query "-x2" match against
      <mrow>
        <mo>&minus;</mo>
        <msup><mi>x</mi><mn>2</mn></msup>
      </mrow>
    
  • Should the ascii query "1.2" match against a <mn>1,2</mn> in a page with lang attribute indicating a country using a decimal comma? And vice versa for the query 1,2 against <mn>1.2</mn> in a page with lang attribute suggestive of a decimal point? Or neither, or both?
  • Should searching for a fenced expression, as with the ascii query (x,y) match against equivalent notations say with lang="fr", such as ]x,y[ ? Probably a good place to say "no" and draw the line of what is within reasonable expectations...

Would adding some text discussing these aspects be generally helpful for better math i18n in the ctrl+f "page search" of browsers?

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 issue #219 and the linked W3C Text-processing guidance first; the issue provides no repository file or test entry point. Determine whether MathML Core should define search and matching behavior for the listed normalization and locale examples, then record the agreed scope or specification text.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation, internationalization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.