Gergo Tisza, 26/04/2014 04:32:
If you absolutely had to cut some functionality out in order to roll this out more broadly, what would you eliminate?IMO we could get rid of the users, imageusage and globalusage calls without much trouble. The first one is only used for gender-correct translations.
Degrading i18n is never an option.
Nemo
On Fri, Apr 25, 2014 at 11:49 PM, Federico Leva (Nemo) nemowiki@gmail.comwrote:
Gergo Tisza, 26/04/2014 04:32:
If you absolutely had to cut some functionality out in order to rollthis out more broadly, what would you eliminate?IMO we could get rid of the users, imageusage and globalusage calls without much trouble. The first one is only used for gender-correct translations.
Degrading i18n is never an option.
Meh, if we had to choose between disabling MediaViewer and sometimes displaying usernames in the wrong gender, that would be a no-brainer. i18n is important, but not *that* important. (Also, the effect would not be that large - based on a quick grep, only about 12% of the existing MediaViewer localizations even use genders.)
I would prefer putting the genders directly into the imageinfo API, though. Ideally, any API that returns usernames should return genders as well, as they are necessary to display those usernames. Even more so if that API returns usernames from remote wikis whose API might not be public, or usernames from a ForeignDBRepo which might not even have a wiki associated...
Gergo Tisza, 27/04/2014 02:17:
Meh, if we had to choose between disabling MediaViewer and sometimes displaying usernames in the wrong gender, that would be a no-brainer. i18n is important, but not *that* important.
I disagree: i18n comes first, new features must not be allowed to cause i18n regressions. The question was what things could be dropped in case of emergency and my personal answer is that, if you can't reach a corresponding level of language support (or performance), the actual file descriptions can be shown instead of a custom solution. The custom file information area is just a pageful of stuff outside the screen anyway; loading the page description instead is not a consistent feature regression.
Nemo
(Also, the effect would not be that large - based on a quick grep, only about 12% of the existing MediaViewer localizations even use genders.)
I would prefer putting the genders directly into the imageinfo API, though. Ideally, any API that returns usernames should return genders as well, as they are necessary to display those usernames. Even more so if that API returns usernames from remote wikis whose API might not be public, or usernames from a ForeignDBRepo which might not even have a wiki associated...
Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
mediawiki-i18n@lists.wikimedia.org