Page MenuHomePhabricator

add the option to have favorite languages in the app
Closed, DuplicatePublic

Description

From mobile-l:

It would be great if two preferred languages could be defined (e.g. German and English) together with a swap button for fast switch.


Version: Unspecified
Severity: enhancement
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=71136

Details

Reference
bz34100
TitleReferenceAuthorSource BranchDest Branch
Hide editing and commenting for merged commits in Diffusionrepos/phabricator/phabricator!39aklapperT361006wmf/stable
builds-api: bump to 0.0.136-20240410072458-06de24b4repos/cloud/toolforge/toolforge-deploy!239project_1317_bot_df3177307bed93c3f34e421e26c86e38bump_builds-apimain
dev: add AGPL-3.0-or-later licenserepos/cloud/toolforge/builds-api!83sstefanovaslavina/add-licensemain
Customize query in GitLab

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:13 AM
bzimport set Reference to bz34100.
bzimport added a subscriber: Unknown Object (MLST).

wikimedia.x.0x wrote:

Fast switching between languages of the currently displayed article or the setting that affects what language edition Wikipedia is searched? (if latter then I am all for it :)

We definitely want something like this -- should be somewhere in our queue for the new app.

Preferred languages would likely default to 'system UI language', 'user wiki UI language if logged in', and maybe other frequently used items (or english).

  • Bug 32908 has been marked as a duplicate of this bug. ***

Note that this is a very popular request from users of the new app as well.

One additional feature request (not quite sure if this should be a new bug): it would also be very convenient to see the current language selected in the search interface. This morning i was searching for five minutes for an article in the English Wikipedia until i found out that the language was set to Dutch...

(In reply to Hay Kranen from comment #5)

One additional feature request (not quite sure if this should be a new bug):
it would also be very convenient to see the current language selected in the
search interface. This morning i was searching for five minutes for an
article in the English Wikipedia until i found out that the language was set
to Dutch...

This is closely related.

I now recall how I reported the original bug, which arrived as a feedback email.

I don't know how will it be resolved. It requires design and may have some surprising technical implications on the search engines but the important part is that the app badly needs to be less oriented to a single language.

(In reply to Amir E. Aharoni from comment #6)

may have some
surprising technical implications on the search engines

ElasticSearch already supports crosswiki searches: currently they're only used inter-project, inter-language is possible as well.
And of course we already have an interface for Wikidata crosswiki search: https://en.wikipedia.org/wiki/MediaWiki_talk:Wdsearch.js

The default search in the apps is using prefixsearch ("Titles"). If the user then goes to full text search ("Within articles") we use ElasticSearch.
So, for the first step in the search process (prefixsearch) I don't see an option for crosswiki search.
Maybe once we don't need prefixsearch anymore. In the meantime, I think a fast switch like https://bugzilla.wikimedia.org/show_bug.cgi?id=71136 is the best option.

Please do not limit this to two languages only. I would like three.

For the case where you want to quickly switch between two languages:
The languages list is sorted so that the most recently used languages appear at the beginning of the list.
Would your issue be solved if T73136 / T87154 were implemented? Those look like duplicates to me.

For the case where you want to quickly switch between two languages:
The languages list is sorted so that the most recently used languages appear at the beginning of the list.

I know, but this list's discoverability seems very poor to me. (Do you have usage data about it?)

Would your issue be solved if T73136 / T87154 were implemented? Those look like duplicates to me.

This bug here is a possible solution to these two bugs. If they are resolved in some other way, this bug can probably be closed. (I noticed that design people sometimes create several Phab tasks as ideas for resolving an issue.)

The general problem is that switching between languages is hard, especially for searching.