Hi Hoxp18, [email protected] schreef op za 15-06-2019 om 01:15 [+0900]: > Dear Frans Spiesschaert, > > > [email protected] schreef op vr 14-06-2019 om 23:43 [+0900]: > > > > > > Oops? (I am afraid it, too. Apologies anyway.) > > > > Apologies accepted. > > How merciful you are. Thank you.
No thanks needed. After all we all try to be as cooperative as we can be, each of us at his own way. > From me, weblate shows old version yet, 1. As far as I can see debian-edu-buster-manual.ja.po on weblate has POT-Creation-Date: 2019-05-16 08 and PO-Revision-Date: 2019-06-08 This is normal as once a week the weblate files are being updated to the changes that occurred in the templates file during that week. Usually this happens on Saturday. > > and there are one "FIXME untranslated" section only > as "Strings needed action" on weblate. Indeed 2. And as far as I can see debian-edu-buster-manual.ja.po on salsa has POT-Creation-Date: 2019-06-12 PO-Revision-Date: 2019-06-08 and one fuzzy and one untranslated message. 3. As this translation is ahead of the translation on weblate for templates 2 and 18, I think it's better that I deactivate Japanese on weblate right now. It would be a small regression for Japanese if I would merge the version in weblate into the version on salsa tomorrow. > > > So, how about this way in this case? > > 1. After your "weblate-to-salsa" commit, > 2. I check salsa directly, and update/commit/push it ASAP. > 3. It's okay to drop some of my recent updates; I have rendered HTML > locally. > This is a cooperative proposal, but given the actual situation, it looks to me to be better not to merge the weblate Japanese buster file into salsa tomorrow. Acting this way nothing of your work will be lost. -- Kind regards, Frans Spiesschaert
