-
Notifications
You must be signed in to change notification settings - Fork 42
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
replicate i18n_tool.py list-translators
in continuous-localization workflow
#1280
Comments
In discussion with @eloquence: Automating this report would be nice, including by contributing the API functionality upstream, when capacity permits, but it's not a priority. In the meantime, maintainers can use the "translator credits" report available in the Weblate UI. |
I'm returning to this for freedomofpress/securedrop#6917. Weblate has been able to generate reports like this one (redacted) since December 2015 (WeblateOrg/weblate@0428d3c).
We added
|
The weblate report format looks good to me, plus post-processing that if we want a different format (not sure we want to promote/advertise everyone's emails like that) seems much simpler than having our own data extraction script. |
Dropping per freedomofpress/securedrop#6917 (comment). |
In #1266, as hoped, Weblate's continuous-localization workflow will allow
securedrop-client
to sidestep much of the Git traversal done bysecuredrop
'si18n_tool.py
. A notable exception isi18n_tool.py
'slist-translators
command, for which there is no Makefile-friendly scripting available:changes
API endpoint will also give us what we want, via e.g.GET /api/translations/securedrop/securedrop/de/changes/?
action=5
. But the results are paginated, which makes them nontrivial to use in a Makefile/shell environment. Even then, some Git operation will be required to replicatelist-translators
's--since
parameter.wlc changes
very kindly traverses Weblate's pagination, but (a) it can't be parameterized on a starting timestamp and (b) its output doesn't include theuser
field we're most interested in.I see two worthwhile approaches here:
wlc changes
). We could do the Git lookup, too, in pure Python via Dulwich. This script might stay here insecuredrop-client
as the guinea pig for continuous localization; or we might find it useful to factor out and make includable elsewhere, especially if the continuous workflow eventually makes its way back tosecuredrop
.Thoughts? Note that this functionality need not be in place to use the continuous-localization workflow, only to properly credit translators in a release.
The text was updated successfully, but these errors were encountered: