Hi!
If special page names are dependent on the content language, then messages absolutely must *not* hardcode the *localized* special page names or you'll get broken links when using a non-default UI language.
Yet another argument against non-default UI.
As with namespaces in links, a message should either use the canonical form (which will always work) or a magic variable which will be replaced with the proper localized form.
And add 20% overhead to page execution on default installs.