Last modified: 2013-06-18 16:38:00 UTC
Hoi, The code for the Danish language is da. The code for Danmark is dk. These codes are codes of completely different standards. The ISO-639 and the relevant RFC do not allow for the creation of codes that are wrong. Having a referral of dk to da is wrong. Please remove all the referrals in DNS of dk to da. Thanks, GerardM
Helping users by redirecting them to where they probably meant to go is a nice thing to do, as previously explained to you.
Please don't close this bug just yet, it's meant as a better place for discussion than the previous bug. I'd like not to have another WONTFIX->REOPEN war here. I agree that redirecting users to the right place is much nicer than a confusing error message, and also nicer than the alternative of showing them a "Did you mean da.wikipedia.org" page.
Resolving INVALID rather than WONTFIX as the stated issue simply is wrong. We have always, and always will, use compatibility redirects -- that's pretty much by definition. If someone wants to discuss the of whether redirecting on the web to avoid hurting users is good or not, feel free, but this isn't an appropriate place for it.
There were NEW redirect added and I was told that I should add a new bug in order to raise the issue that these should not have been added. As it is we have many redirects that are wrong and they are not considered either for rectification because of the work involved, because of it would not be "nice" to users. We have Wikipedias that have a name that is not acceptable by any standard but perseverance of past mistakes. Using standards and conforming standards is a technical issue and adding either WONTFIX or INVALID ignores the issues involved. As a consequence this IS the right place because any other place is irrelevant. Thanks, GerardM
Compatibility redirects *are* how we change old wrong things to comply to the standards without breaking old links. Resolving INVALID.
The point here is that the dk redirects were recently introduced and consequently were not necessary in the first place AND they are wrong. Compatibility redirects to solve old wrongs is different from introducing new wrongs. Thanks, GerardM
We want to keep the convenient redirects around, so we are not going to remove the dk.<project domain> DNS entries nor the redirects to their da.<project domain> equivalent.
