|09:28, 16 February 2011||Yurchor||New reply created||(Reply to Recent edit of KonsoleDevelpment)|
|09:21, 16 February 2011||Claus chr||New reply created||(Reply to Recent edit of KonsoleDevelpment)|
|21:48, 15 February 2011||Yurchor||New reply created||(Reply to Recent edit of KonsoleDevelpment)|
|21:35, 15 February 2011||Claus chr||New thread created|
I don't understand your comment. Surely, KonsoleDevelopment is the original page - or am I missing something?
Consider the following situation:
1) User read the instruction and want to follow it. 2) He clicks the link and opens localized page (with Special:myLanguage). 3) He notice that the missing new "Bla-bla" section of Configuration.
Question: How to add the description of "Bla-bla" on localized page? Answer: The section should be added to the original page.
So what is the point to send the user to the localized page, right?
I get your point. However, a user who knows enough to make additions to a page probably also knows how to navigate to the original page. On the other hand, a more casual user who perhaps doesn't even speak English might still be able to provide valuable suggestions on the Talk page.
I don't think that leaving out Special:myLanguage is going to be a problem to anyone - navigating to the translation of choice is easy enough; but I wonder if it is not a good idea to remain consistent even in special cases like this.