On Mon, May 11, 2009 at 8:50 PM, Daniel Schwen lists@schwen.de wrote:
The simple (albeit ugly) solution would to add a parser version field to the revision table, drag the old parser along as 'legacy', make the new parser the default (and only) option for all new edits, and spit out a warning when you are editing a legacy revision for the first time. The warning you be made dependent on the cases that break with the new parser. Cases that break could be detected by comparing tidied HTML output from both parser versions.
Sounds cool, but it'd require a formalization of MW markup first (something that should have been done long ago). What about correcting stuff from "old" behavior to new parser via bots/update scripts, even for old revisions?
Marco