-
-
Notifications
You must be signed in to change notification settings - Fork 993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search who translates the same language #2241
Comments
Sounds like this could build some community. Is this potentially a GDPR issue though? Right now you can effectively work it out by amalgamating the history which goes back (at present) 5 years. Would be nice with the statistics and info-page the whole platform has for every language. For Norwegian Bokmål we have an IRC-channel, and a dictionary. |
Tthe history for nb_NO is short because of changing the language codes (see #2051), you will find rest of the history under nb. We currently do no history pruning. |
Okay, I understand. Best Regards |
You can use history to look for these: https://hosted.weblate.org/changes/?project=weblate&lang=cs&action=2 We probably could add language filtering to user listing (https://hosted.weblate.org/user/), but that will certainly not have the period. |
It is based on the same parser as searching for strings. Issue WeblateOrg#2241
It is based on the same parser as searching for strings. Issue WeblateOrg#2241
It is based on the same parser as searching for strings. Issue #2241
Thank you for your report; the issue you have reported has just been fixed.
|
Reason :
I want to know how many people translate the same language.
And who is it?
I also want to specify the range of the period.
Solution :
Display the number of translators in the same language in "Translation status".
And, click on the number of translators to display a list of translators of the same language.
Next to the name of a person, how many translations were made.
Add start and end of period to search function.
Best Regards
Kyotaro
The text was updated successfully, but these errors were encountered: