Wiki markup isn't too bad

Posted Aug 18, 2025 14:27 UTC (Mon) by paravoid (subscriber, #32869)
In reply to: Wiki markup isn't too bad by t-8ch
Parent article: Arch shares its wiki strategy with Debian

Parsoid is indeed the next-generation parser, is being actively developed by a fully staffed team, and has been for ~14 years by now, if I'm not mistaken. It's *still* not the default for read views which speaks to the complexity of the problem (among other reasons). The Wikimedia Parser/Parsoid team will be the first to tell you how difficult wikitext can be in terms of semantics, so I don't think the criticism here is undeserved.

Parsoid is supposed to become the default for read view on Wikipedias by July 2026, and the default for MediaWiki 1.47 LTS (Nov 2026), with the legacy parser to be ultimately deprecated in 2028. These timelines have slipped multiple times before, and the language the WMF folks use to announce them is... careful ("tentantively scheduled", "we hope", etc.), so don't hold your breath. Fortunately one can already benefit from it by using VisualEditor, including on the new Debian wiki.

https://wikimedia.eventyay.com/talk/wikimania2025/talk/UU... and, linked from there, https://docs.google.com/presentation/d/198_UG5VmHYMoO_38s... is probably the most recent update from the project.

Wiki markup isn't too bad

Posted Aug 18, 2025 21:04 UTC (Mon) by smurf (subscriber, #17840) [Link] (1 responses)

Counterpoint: if you need 15 years to write a correct parser for a markup language, that markup language *is* bad, almost by definition.

Wiki markup isn't too bad

Posted Aug 22, 2025 18:50 UTC (Fri) by cscott (guest, #178938) [Link]

It's also taken nine years *just to write a spec* for markdown (commonmark started 2014, latest version just published 2024-01-28). Things which look simple on the surface can be surprisingly hard to nail *all the way down*.

And that's the case for wikitext, for sure. Parsoid has been in production use since 2012, and has powered all the mobile apps for almost as long. Many many other WMF projects have been using Parsoid HTML for a decade. Before we completely ditch the old legacy parser, however, we need to make sure that 99.<some number of nines>% of Wikipedia's >100M pages are bug-for-bug compatible, because we take seriously our duty as custodians of the knowledge base which is Wikipedia and the WMF projects. At this point you might consider our work more 'archivist' then 'engineer', in that our main effort isn't the parser, per se, but preserving the rendering of existing articles.

The goal of Parsoid is to render pages into well-specified semantic HTML, which preserves all the meaningful information (template boundaries, template arguments, invisible constructs, etc) of the original wikitext. This isn't *just* to allow us to use an HTML editor and round-trip back to the original wikitext, it also paves the way for other editors and markup languages in the future: as long as it can round-trip to and from "MediaWiki DOM Spec" HTML, you can use it to edit wikipedia.

More information: https://en.wikipedia.org/wiki/User:Cscott/Ideas/A_Dozen_V...