For all things related to internationalization (i18n) and localization (l10n).
Dec 9 2018
The biggest difficulty in this idea is that users are able to set their language in MediaWiki, but nothing about the HTTP environment carries forward that language setting, so when an HTTP request is made and hits an error page, there's little-to-nothing to go off of in that request to indicate what the target language should be as it isn't querying their MediaWiki user preferences. When I think of ideas for creating a localized error page in a wiki environment, Wikipedia comes to mind with their localization in the subdomain (e.g. en.wikipedia.org, fr.wikipedia.org, etc), where you could theoretically make an nginx if statement that picks up the subdomain and returns a different error_page directive depending on the subdomain. However on ShoutWiki where the domains don't indicate the site language, that doesn't work. Even if you were to query the site's content-language response header before returning a PHP-based error_page, the site's content-language could be different than the user's customized preferences.
Mar 14 2017
While having this page available in as many languages would be nice, I'm not really sure if it's feasible.
Since 403 and 404 errors are different, I've split them off to T185.
Feb 7 2017
With the DeleteWiki improvements done in rSHWK4107 this is no longer an issue.