I would like access to translatewiki.net so that the Android team should has (at least) one person with the capability to fix and update localizations used in our app.
Here is my public key
| cooltey | |
| Sep 15 2017, 11:20 PM |
| F9567382: wikimedia.pub | |
| Sep 15 2017, 11:20 PM |
I would like access to translatewiki.net so that the Android team should has (at least) one person with the capability to fix and update localizations used in our app.
Here is my public key
In previous discussions this was deemed unnecessary. Has something changed? Regular user account is enough to make changes to translations in translatewiki.net and you will get patches two times a week.
The Android team is in a period of transition, currently with two new engineers coming up to speed, and @Niedzielski (who used to take care of this) having left to work on the Readers web team.
I am following the process here: https://www.mediawiki.org/wiki/Translation_of_app_string_resources
If it's changed, that doesn't appear to be documented anywhere.
@Niedzielski: do you have time for a chat with @cooltey and me sometime this week about what the current process is? He will be taking this over going forward.
o/ @Mholloway, AFAIK @Nikerabbit now does all the TWN syncs. When there's a breaking issue, the change can be amended prior to committing to master. The wiki page documents the old manual process of performing a sync but it was no longer necessary for Android and iOS after we added support to l10n-bot for GitHub and opening a Gerrit patch without auto-+2ing. If you'd like to chat about the process, I'm happy to, but I suspect the TWN folks will be able to answer questions with more detail.
OK, let's close this as declined, then.
I surmised that some additional step must be needed because we've been getting a substantial number of translations for strings that have been deleted from the default and -qq files, necessitating translation cleanup patches like this:
https://gerrit.wikimedia.org/r/#/c/378342/
https://gerrit.wikimedia.org/r/#/c/368840/
(@Nikerabbit, you commented that deleted strings are synced "only if some other change triggers an update of a translation file" but I'm not sure what this means. What additional step(s) do we need to take beyond deleting the string in the default (and -qq) language in order to prevent them from continuing to be translated?)
Thankfully, this morning's L10n-bot patch appears not to have introduced any additional unused translations.
If you are seeing new or changed translation for deleted strings, that is a bug.
Here is an example timeline:
If language breceives any update, the translation for the deleted string will then get removed on next export.
This is not intentionally so, it is just side effect of our performance optimizations and nobody has looked whether that could be easily fixed.
Thanks, @Nikerabbit, for the explanation of the process! I'll keep on lookout for new/changed translations for deleted strings and let you know if any additional instances occur.