Page MenuHomePhabricator

Consider using a custom content model for translation units
Open, LowPublic

Description

This would solve, or make it easier to solve:

And probably a bunch of other things, although those stood out from my review of the backlog. On the other hand dealing with all of the translation units in the database having a content model of "wikitext" would be a pain.

Event Timeline

On the other hand dealing with all of the translation units in the database having a content model of "wikitext" would be a pain.

It’s just a database migration, isn’t it? It may be long-running, but not really complicated. (I think it’s okay not to log them to Special:Log – it’s basically just a changed default.)

Yeah, I guess. But I don't think retroactively reassigning the content models of revisions is something that was done before, and not doing that will make things worse rather than better because one of the points of this is clean handling of own revisions.