Last modified: 2013-11-12 09:20:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50496, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48496 - Allow multiple user languages in preferences
Allow multiple user languages in preferences
Status: NEW
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-15 05:20 UTC by Matthew Flaschen
Modified: 2013-11-12 09:20 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Matthew Flaschen 2013-05-15 05:20:20 UTC
It would be useful to have an ordered list of user languages in preferences, rather than just one.

This would particularly help on wikis with more than one content language, such as Wikidata or Commons.  Pages, watchlists, recent etc. could optionally show all the users' languages, while hiding ones the user didn't select.

For the interface itself, it could use the first language then fallback through the others in some order (this is a bit complicated since the languages themselves have fallbacks).
Comment 1 Nemo 2013-05-15 05:34:04 UTC
For comparison, Translate adds by itself a preference containing a list of languages, for the assistant languages features.
Bug 41686 should probably be implemented as part of CleanChanges, used for the same purpose on Translate wikis.
Comment 2 MZMcBride 2013-05-16 00:50:00 UTC
I don't understand this bug. The language in preferences is currently only used for the site interface, as I understand it. (Is this correct?)

What would allowing more than one language to be selected accomplish?
Comment 3 Matthew Flaschen 2013-05-16 01:12:28 UTC
(In reply to comment #2)
> I don't understand this bug. The language in preferences is currently only
> used for the site interface, as I understand it. (Is this correct?)

No, it's also used for content.  For example, https://meta.wikimedia.org/wiki/Meta:Language_select will filter the category descriptions on a page like https://commons.wikimedia.org/wiki/Category:Earth .

You can override it to show all languages, or an arbitrary one.  But it defaults to your preference language.

Same for https://www.wikidata.org/wiki/Q2 (Earth at Wikidata).  All the labels are localized, using your preferences by default.

> What would allowing more than one language to be selected accomplish?

I gave clear examples in the report, such as filtering your watchlist and recent changes.  Look at https://www.wikidata.org/wiki/Special:RecentChanges for example.  It would be nice to only see the label changes for languages in my preferences.
Comment 4 Matthew Flaschen 2013-05-16 01:15:25 UTC
Actually, Language select may default to your browser language.  Either way, the point about the watchlist, recent changes, etc. applies.
Comment 5 MZMcBride 2013-05-16 01:33:25 UTC
(In reply to comment #3)
> I gave clear examples in the report, such as filtering your watchlist and
> recent changes.  Look at https://www.wikidata.org/wiki/Special:RecentChanges
> for example.  It would be nice to only see the label changes for languages in
> my preferences.

Obviously I didn't find the examples in comment 0 very clear; that's why I asked for a clarification. Thanks for the links.

You should file separate bugs about each individual component that you think should have a language selector (Special:Watchlist, Special:RecentChanges, etc.). This bug would be a blocker or a dependency of those bugs.
Comment 6 Matthew Flaschen 2013-05-16 01:35:59 UTC
Bug 41686 (listed in the see also) is about watchlist and RC filtering.  That can work even if there's only one language, but it's more useful to multi-lingual people if this is also implemented

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links