Last modified: 2014-11-17 10:34:44 UTC
This is not about a bug! I just follow the guidelines at Wikipedia Village Pump about proposals for changes in the software and post this here.
I just have a suggestion of a very general type: Would it be possible to add a means to switch language from every Wikimedia page? Some pages contain the possibility to switch to another language, but some have not. I am multilingual, and therefore would need such a feature quite frequently. If there is no link to other languages, or the language I want to go to is not listed, it is always quite awkward to restart from scratch at the homepage.
What about a multilingual search? Would also be handy...
Deassigning myself, leaving this for the general queue after we mull over some stuff.
This will be solved by [[mw:Universal_Language_Selector]], you might want to add your feedback there.
(In reply to comment #3)
> This will be solved by [[mw:Universal_Language_Selector]], you might want to
> add your feedback there.
Switching from LATER to the second most relevant resolution for fear of information loss. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65116
(Should probably be marked duplicate of some tracking bug for ULS deployment now.)
Since I couldn't find a deployment tracker, converting this one to it.
Also adding a handful of bugs I think are blockers. Selected based on their bug titles only (looked specifically for quality and usability).
If some are less important, please remove them with rationale. And add more as needed.
Clarifying summary: this is not a tracking bug for regular i18ndeploy requests (shell requests for WebFonts/Narayam/ULS on individual wikis).
*** Bug 34982 has been marked as a duplicate of this bug. ***
This is nearly done, see
(In reply to comment #8)
> This is nearly done, see
That was completed on 2013-07-09 as planned, but I don't think that fixes this bug yet because language selection is for logged-in users only; blocker bug 42186 is still open.
Ops have not yet come up with a solution for that, so no plans exist and there are no useful bug reports, but as soon as they exist they should be added as blockers of this bug.
See Erik's bug 46306 comment 115 for the current status of plans.