Domas Mituzas wrote:
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.
Maybe, but it is very much the friction that exists between function and
functionality. When the function, MediaWiki, prevents functionality it
is certainly not a good thing either. There is a need for non default UI
in our projects with Commons as one of the more prominent ones. Here you
have a situation where the size of the content starts to prevent the
discovery of what is looked for. Certainly having English as the default
UI is a good thing, but it does not help a seven year old French girl to
find a picture of a "cheval".
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.
So it does cost but is
there an alternative, an alternative that
provides us with the required functionality ??
Thanks,
GerardM