On Sat, 2021-02-13 at 17:04 +0900, Stephen J. Turnbull wrote:
Your English is fine, it was just my lack of imagination: on February 12, I couldn't conceive of February 3 being even a little "old"!
I was not your imagination, it was confussion inserted in the line between brain and fingers and I meant .po and wrote .mo
More important, as long as the .mo file is more recent than the .po file, that's the best the release manager can do. I haven't been involved in the release process, so I can't swear to it personally, but if Mark says that new translations generate a merge request automatically, and we make sure that the translations are merged before release, I believe him. That's optimal as far I am concerned.
But, it seems something did not go well :-(
Perhaps some enterprising soul would be willing to automate production of pip'able packages containing only new translations, but without that, I don't see how to beat our current procedures. (I wouldn't want to use such a thing, though, I'd be too afraid that one day all the translations would be replaced with Dril tweets!)
Fully agreed. I first thought of "language chanpions" that could take care of syncing the .po files from Weblate to the replease repository. But then, that involves human availability, which is not an abundant asset in open source projects.
Then, my brains went into "crazy mode", why do notuse the power of Python and the net. Maybe we can get someone (GSoC student) to write code that, given a .po file uses Google translation to check that the resulting string in the target language means more or less the same as the original English string on the .po file?
Crazy-tinking-ly, Victoriano.
-- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN
Note: signature.asc is the electronic signature of present message A: Yes.
Q: Are you sure ?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting annoying in email ?