Page MenuHomePhabricator

Use a configurable Alphabet to generate backlink markers in Cite (Parsoid)
Open, Needs TriagePublic

Description

For reference see T383216: Use a configurable Alphabet to generate backlink markers in Cite (legacy) and the work done in [1]

Implementation details:

  • Adapt the code introduced in [1] to be reusable between Parsoid and the legacy parser.
  • Should be backwards compatible with the current mechanism where a i18n message is used: the PHP configuration feature flag will switch between numeric+legacy-i18n backlink markers, or the entirely new mechanism.
  • Add tests

[1] https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cite/+/1111359

Event Timeline

Stalled to get a clear opinion on the priority, since we realized that this task needs to be prepared by introducing explicit backlink markers to Parsoid.

Change #1115354 had a related patch set uploaded (by Awight; author: Awight):

[mediawiki/extensions/Cite@master] [WIP] Explicit HTML for backlink markers

https://gerrit.wikimedia.org/r/1115354

Change #1115446 had a related patch set uploaded (by Awight; author: Awight):

[mediawiki/extensions/Cite@master] [WIP] Backlink mark rendering service

https://gerrit.wikimedia.org/r/1115446

Change #1115447 had a related patch set uploaded (by Awight; author: Awight):

[mediawiki/extensions/Cite@master] [WIP] Consistent backlink labeling for Parsoid

https://gerrit.wikimedia.org/r/1115447

Change #1115354 abandoned by Awight:

[mediawiki/extensions/Cite@master] [WIP] Explicit HTML for backlink markers

Reason:

split into smaller pieces

https://gerrit.wikimedia.org/r/1115354

Exasperating detail is that the legacy code paths don't have enough information to choose between numeric or legacy i18n markers, since that's controlled by the choice of dollar variable in yet another i18n message. I'm considering having Parsoid only follow the new code paths...?