Topic on User talk:Daniel Kinzler (WMDE)/MCR-PO

And I hope TimedMediaHandler doesn't actually add a slot per language. Anomie (talk) 17:25, 1 March 2018 (UTC)

What would be the alternative there? We want to be able to filter by language in the page history, I imagine, so we can't just put everything in one slot. Same goes for template subpages (documentation, maybe even localization) on multilingual wikis.

This is somewhat relevant because if there are pages which have hundreds of slots do to i18n then always generating a ParserOutput and SecondaryDataUpdates for every slot seems like a no-go.

One item of note is that role_id is a smallint, so one extension using up 400-some of the 32767 available IDs could be problematic. Especially if it becomes a pattern.

If it becomes a pattern, maybe the slot table should have an optional language field?

I18n as a first-class citizen is a core principle of MediaWiki and I don't see how that could happen without some sort of support for slot localization.

TimedMediaHandler might use a format that can store multiple languages in one slot, as Wikibase does (I believe) for its translations of data strings. Or TMH could keep using its own namespace with subpages.

Or maybe a "slot_lang_id" could make sense. But it's not the only option, and could have drawbacks such as making the history of the "main" version harder to follow with all the updates to translations.

I don't think those are great alternatives. Putting everything in a single slot would make following the main version (or any other) even harder; using subpages preserves all the problems that MCR was supposed to solve (e.g. things like export, protection, move not working out of the box).