Description of problem:
Most translators master their mother languages better than others. One project may have many languages to be translated; however, zanata should display translators' preferred/main languages first before others to save the time to search for those preferred/main languages.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
0. Log in as a non-English translator, for example, zh-Hant
1. Enter one project page, for example, fonts-tweak-tool
https://translate.zanata.org/zanata/project/view/fonts-tweak-tool
2. Enter one version page, for example, master
https://translate.zanata.org/zanata/iteration/view/fonts-tweak-tool/master?cid=195174
3. Languages showed to be translated
Actual results:
Languages showed to be translated, sorted by Alphabet
==> Afrikans > Albanian > Amharic...
Expected results:
Suggested as below,
Languages showed to be translated, preferred/main languages first, followed by others which may be later sorted by Alphabet
==> Chinese (Traditional, Taiwan) [translator's main language] ==> Chinese (Taiwan) [translator's main language] ==> Chinese (Simplified) [translator's reference language/preferred language] ==> Japanese [translator's reference language] | Afrikans > Albanian > Amharic...
Additional info:
Carlos Munoz commented:
There is a workaround for the moment:
On the project page, each version on the list has a drop-down which will take the user directly to the document list for a language. This drop-down only shows the list of languages the user belongs to.
Two options for solving this:
A Separate list of user languages
A new sort order choice that puts the user's languages first (this would be the default). There would be some identifying features to highlight the user's languages.
An option to always show your languages first no matter what the sort order is.
Carlos Munoz commented:
For last option: The toggle would be disabled or hidden for users with no languages.
This would still be a great UX feature, very personal and providing a streamlined workflow
We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.