Change Details

Please document a ''translations for editors'' in a hurry and on a mission, such as suitable for the likes of Help:Editing (or a link to there). Translations markings make editing very difficult because, and //only// because, there is no documentation for translations whose audience is editors, not translations administrators, not translation extension managers, and not translations applications for translators. For example, I've finally had to remove translations from Help:CirrusSearch because Search documentation there has been lacking in content and structure for years, and as a result Help:Searching on Wikipedia has little or nothing on CirrusSearch. This may be tolerable in a volunteer environment, perhaps expected. But what is wrong is the barrier to remedying the festering problem by making "a wiki not anybody can edit". I believe there was a general principle being violated at Help:CirrusSearch: never keep translations markings on a page that is either highly active or nowhere near completely finished. The problems //seems// to be that CirrusSearch is an abandoned ghost town on MediaWiki and Wikipedia, and that no one edits those pages because Search documentation is not needed or cared about, but the real problem just may be Translations Markup for editors is not documented at or linked to Help:Editing at MediaWiki. If there were such a page, I could then easily care enough to actually learn the whole page, and I'm guessing that would benefit all of us working with translations markings. I personally, at this time, can't care about other MediaWiki extensions above and having priority over caring for the CirrusSearch extension, unless investing in Help:Editing pages will enable me to edit a wiki "anyone can then edit". As it was, I felt translations at Help:CirrusSearch was just making unnecessary work for everyone. That page could hardly be evolved because of the translations markings and the inability to master them by any means except by some initiation ceremony into adminship. My criterion for removing them were these priorities: 1) Editing ability 2)Searching ability 3)Translations.

Please requisition a new document ''How to edit a page with translations". Current documentation is oriented towards translations administrators, translation extension managers, and translations applications for translators. - It should be compact and concentrate on the syntax and grammar of <translate> <tvar>, <!--T:##--> and other translations markup. - It should focus on the needs of editors. Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. - It should bring pages such as Help:CirrusSearch, back to life, "edited by anyone, mercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, perhaps as a result of Help:CirrusSearch paralysis. As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. Documenting how to edit a page with translations will prove that translations and translators care about editing, not just translations.

Please document a ''translations for editors'' in a hurry and on a mission, such as suitable for the likes of Help:Editing (or a link to there). Translations markings make editing very difficult because, and //only// because, there is no documentation for translations whose audience is editors, notrequisition a new document ''How to edit a page with translations". Current documentation is oriented towards translations administrators, not translation extension managers, and not translations applications for translators. For example- It should be compact and concentrate on the syntax and grammar of <translate> <tvar>, I've finally had to remove translations from Help:CirrusSearch because Search documentation there has been lacking in content and structure for years,<!--T:##--> and other translations markup. - It should focus on the needs of editors. and as a result Help:Searching on Wikipedia has little or nothing on CirrusSearch.Perhaps a section in Help:Editing. Translations markings on a page discourage editing. There is no documentation for translations whose audience is editors. - It should bring pages such as Help:CirrusSearch, This may be tolerable in a volunteer environmentback to life, perhaps expected."edited by anyone, But what is wrong is the barrier to remedying the festering problem by making "a wiki not anybody can edit". I believe there was a general principle being violated at Help:CirrusSearch: never keep translations markings on a page that is either highly active or nowhere near completely finished. The problems //seems// to be that CirrusSearch is an abandoned ghost town on MediaWiki and Wikipedia, and that no one edits those pages because Search documentation is not needed or cared aboutmercilessly" as the proven saying goes. Help:CirrusSearch is a ghost town, yet Search is a hot technology -- you can get a college degree in it -- and Elastica is a hot open source movement. Help:Searching on Wikipedia has little or nothing on CirrusSearch, but the real problem just may be Translations Markup for editors is not documented at or linked to Help:Editing at MediaWikiperhaps as a result of Help:CirrusSearch paralysis. If there were such a page, I could then easily care enough to actually learn the whole page, and I'm guessing that would benefit all of us working with translations markings. I personally, at this time, can't care about other MediaWiki extensions above and having priority over caring for the CirrusSearch extension, unless investing in Help:Editing pages will enable me to edit a wiki "anyone can then edit". As it was,As an editor at Help:CirrusSearch I struggled with 1) the documentation on translations and 2) with unresponsive translations "editors" for months before becoming fed up with it and removing it. I feltDocumenting how to edit a page with translations at Help:CirrusSearch was just making unnecessary work for everyone.will prove that translations and translators care about editing, That page could hardly be evolved because of the translations markings and the inability to master them by any means except by some initiation ceremony into adminship. My criterion for removing them were these priorities: 1) Editing ability 2)Searching ability 3)Tnot just translations.