Parsoid-based wikitext "linting" tool for "buggy" / "deprecated" wikitext usage; keywords: broken wikitext information
OpenPublic

Assigned To
None
Priority
Lowest
Author
ssastry
Subscribers
marcoil, Qgil, Elitre and 7 others
Projects
Tokens
"Love" token, awarded by jayvdb."Like" token, awarded by Quiddity.
Security
None
Reference
bz46705
Description

During parsing and running various transformations, Parsoid has sufficient information about buggy wikitext usage that can be passed back to editors for fixing up (Ex: fostering of content out of tr-rows because of missing td-wikitext tags, or missing newlines, etc).

This can also be a good way to slowly deprecate reliance on edge case behavior by editors (Ex: multi-comment whitespace lines are treated different from single-comment whitespace lines -- this is just a side effect of PHP parser code and should be made consistent in the parser after deprecating its usage).

This is more a longer-term goal and can be a good self-contained project for someone.


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=50547
https://bugzilla.wikimedia.org/show_bug.cgi?id=62323
https://bugzilla.wikimedia.org/show_bug.cgi?id=66413

bzimport added projects: Parsoid, Easy.Via ConduitNov 22 2014, 1:29 AM
bzimport set Reference to bz46705.
ssastry created this task.Via LegacyMar 29 2013, 8:50 PM
GWicke added a comment.Via ConduitAug 14 2013, 12:06 AM

Another thing we could potentially lint for is auto-inserted start / end tags as mentioned in bug 51945. These are fairly common, so some filter would be needed to narrow it down to cases that are likely to cause problems.

GWicke added a comment.Via ConduitAug 14 2013, 12:07 AM
  • Bug 51945 has been marked as a duplicate of this bug. ***
Elitre added a comment.Via ConduitFeb 26 2014, 4:37 PM

In order to decide if you want to be more lenient in accepting bad table-row wikitext, here's an example of how things can go wrong
https://fr.wikipedia.org/w/index.php?title=Aquila_Italiana&diff=101605787&oldid=90404051
(chatting with Subbu it seems to be caused by unnecessary | marks).

ssastry added a comment.Via ConduitMar 6 2014, 4:11 PM

Actually https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Check_Wikipedia is a related project that we should incorporate into our discussion.

Check the following section on that page which is relevant to this project.
https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Check_Wikipedia#Round_2

Arlolra placed this task up for grabs.Via WebNov 25 2014, 8:10 PM
Arlolra set Security to None.
ssastry moved this task to Needs Discussion on the Parsoid workboard.Via WebDec 9 2014, 5:25 PM
Qgil added a subscriber: Qgil.
Qgil added a comment.Via WebFeb 11 2015, 1:44 PM

Wikimedia will apply to Google Summer of Code and Outreachy on Tuesday, February 17. If you want this task to become a featured project idea, please follow these instructions.

ssastry added a comment.Via WebFeb 11 2015, 2:58 PM

Hardik Juneja already worked on this for last year's GSoC .. we are at this point awaiting internal resources to polish it off, deal with a few more things, and enable it in production.

marcoil lowered the priority of this task from "Low" to "Lowest".Via WebFeb 12 2015, 11:47 AM
marcoil added a subscriber: marcoil.
Qgil removed a project: Possible-Tech-Projects.Via WebFeb 12 2015, 11:49 AM
marcoil moved this task to Backlog on the Parsoid workboard.Via WebFeb 12 2015, 11:51 AM
Qgil moved this task to Hacking proposals on the Wikimedia-Hackathon-2015 workboard.Via WebFeb 25 2015, 10:35 AM
Quiddity awarded a token.Via WebMay 15 2015, 6:26 AM
Qgil added a comment.Via WebMay 24 2015, 9:13 PM

Just checking, is there someone working on this task in Wikimedia-Hackathon-2015? If not, please remove the project.

jayvdb awarded a token.Via WebMay 25 2015, 6:26 AM

Add Comment