[Mediawiki-i18n] [Multimedia] [Ops] Caching API responses

[Federico Leva (Nemo)]

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 at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/multimedia
>