Forum: >>> Magnum BBS <<<

Ris: ddtp2.d.n down again but that's ok!

From Thomas Vincent@21:1/5 to All on Tue Jun 9 00:50:01 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --H3pLqHMLHexH2pgedaqSj72wDn1JcuJzp
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi!

Le 04/06/2020 à 13:23, s3v a écrit :

What is the current status of the ongoing
transition?

The current status is: needing motivation. :)

Following the announcement in March that the migration was in progress
and required some validation before we could make it official, it was
found that new translations could be broken by an encoding issue.
Fixing this issue led to another one and I think Andrey managed to have everything solved by the middle of April.

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost,
but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one
month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it
will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)
- we won't ask ftp masters to retrieve the new state of the translations
until all those translations have been checked

I can't give you an estimate of when it will be done, we don't even know
how many translations are affected.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

If you know perl/postgresql, you can come talk with us on #ddtp on IRC.
If you don't, you can still come talk with us on #ddtp on IRC. :D

Thanks a lot for taking care of this job.

:)

Kind regards,
Thomas

Kind Regards

-------- Messaggio originale --------
Oggetto: ddtp2.d.n down again but that's ok!
Da: Thomas Vincent
A: Debian I18n ,Debian L10N Development
CC:

Hello all,

We were planning to send you a message tonight announcing that we would
be migrating the DDTSS service next weekend, with a proper timeline,
etc. but ddtp2.d.n tried to catch us by surprise and went down again.

Luckily, I have retrieved the last available version of the database
backup yesterday evening, so that means that at worst we don't have the
last day of contributions on DDTSS (I don't know at what time DB daily
backups are prepared).

So, what I propose to you instead is that we start the migration process
tonight and let you know when ddtp.d.o is ready to be used (hopefully
tomorrow morning).

Cheers,
Thomas

--H3pLqHMLHexH2pgedaqSj72wDn1JcuJzp--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7ewCEACgkQenSQZNOP EaPPZRAA1z9FqOIjrz28fd1KNgPP1TURhanFTZlsDY47nfCzHkbtFFF+qMqQVgM2 BIpMSpB8KrJ59qYZU42pKKrOEeMbUl0/lOCIO/1wUpxPKDtqmjgGRYcX1qNtobzP V30dtDac1Rvo7k/YSBGw0kp1yVyy5b+TanBON8K3TkPu2ZFS/+TSBZ3OHiN1gv5S j/vsEhmbWasf4XOAmGJBw4+hzRzwhz7XfpsLCJE1mp/mDKwEWZA7fyQieHxqDdYs W3zLHlp9HnfTXNCl/0OGyL7E5/qLa5JuYw2vDk2VSQaEihNCayCQ4GvzxKv7DWVS uL66sGMgBlceQtKVQO/STTQBQmV5iUIN8/255F/p0PIoCP9ufElpV9q+hwAagAxs rgSnvxw9TEqKbOxdpZ6XL9YVFiZ2OZ46ZM0C24036Ct90dT4zPPHNJjzVeFODIW0 xOHdF4dwaBzRvgv1PvPZKzgpYV0jvc1cDvEPrFU0l1izVX5xvvCQV8WFbKa+yu0U AlWzSvZxh8tnyEK660ell5VLettF11scDL1VoMKaeulaR+cBr0/Z/Ybg4RyUDwrZ XmxUW4ET4GeLVhpG/sbVWXEFIsVgj2akJ6O73uXsbLySj+6EXnmM3UqqhyHAwLDY hcwQWRSVyti2T3NXuRVco/ov81fa05qVZaKj4CxSqNm2YrSMkRs=
=yPy/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Beatrice Torracca@21:1/5 to Thomas Vincent on Tue Jun 9 13:20:01 2020

On marted� 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

Hi!

The current status is: needing motivation. :)

That is understandable... we are all volunteers

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost,
but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

I imagine I should change the warning then. Any suggestion?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it
will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot� for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

beatrice

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEhBuuTqYTMX2CMr6YL+1Y7ldknz8FAl7fbSIACgkQL+1Y7ldk nz/3PA//Xr46ur1HzyBGGT2bmiAd76nj+oEF+Z2k4f5lj+a2SOMB27c15ofQ9LuM uxzKFvOnxmkJX6q+DrMQKcCc6yCXtlx1uuoeBqZ0ltcqimz9ReeqOCkC9fRNvJin Z77LC2OeCqYuPz3NnGO9SzZZnG/h+M5JYV0vJLW7/d/qQpMSdKDSY0T4cW+Vb5Ar Qbvp9b+x46k3H21Yjsc/+1t+bo/4b50RgbMYHetYp5Nx4L1CNk+zNqjSNBZLi0Ov 9/WqFUM90s6YkJmnQQa82tKb3kZVoDWgLRIWNZfLSZDxgzajMe4vPH4kXPQSt3SY gdB6ZY0ry1XpHO7SMKgL0KdKxFnTW/g8ro6Xr7FLp9VfGVtMoQXd6a885hKbNkl+ XhaB/dlgL1jg09hz0Wmd6ostl840USN44tpqTgpt1Cwq46r0QOvDiQqO1JWVOwD8 fOE/EV0ZFUUqEcMhBsI7lbDKrGrmW3pqrifLm9lXG/Oa9+FKCO7CbjXnL2zEuOyb FcyZrc//QizXKqV824keLssOoWEd056MPGRWWlgZvfbyLRkvBItOhnztsInKglp9 1a3jvUWF1roSx4flrfamFLqZPHjpA0aFxZWaPyhVL/tb5W/vy/Bom1j5dfJZAdVv TnkGkGUwWuiNQnNSUOC+uP6IU41XFBVsAPXvyMJphU13R6qCLTM=
=H7dy
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Thomas Vincent@21:1/5 to All on Wed Jun 10 01:50:02 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jMiHqBJZL1OdsBGTMR6HPpYkuOFh5sk76
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

Le 09/06/2020 � 13:06, Beatrice Torracca a �crit�:

On marted� 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost,
but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one
month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it
will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot� for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

--jMiHqBJZL1OdsBGTMR6HPpYkuOFh5sk76--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7gH4cACgkQenSQZNOP EaOiVhAAxzO/ih8L+zXymdvTsr64ReLwMpy3WSBONsNXrRCjzvRN2LK3sLWXsWAR nHdUAqR3Rm2oseUXNSS9oqYKXOsJh/xA9z7srNxpT5ffdqY9aUpbCgJ7Z74KdFAr TzKXmWCmtUHJ6H04Ew33qsOrXYFWrDFUC5bl7VbOHLHdhIYXbvbvAbczswmSz5ms ehhoF5DbQtXUsEOs1rs7hZjDh8Dp0Vhrtz0GT+339mEpQYJHGu5WiKk2mI//ogIq 3vxlumDYb6qaJeyfW+eaFUQRqHQ+9DTgAL9Fpbkj2tTwpRzA5bwapJanRvMiZMP1 vKMAwMFSd0PePbMjG0hVsLeQaq7IeAD+WdP96O4u7iGyw5lvPP6e4OvhV54/Er/+ y/L5++YGQi1mb1d7l68PLIHlmEX2cpi9NbWf9YCDSZTdHXgCokT+QvvPWXI4pyks 5d93EXndv2zRvi1PnyoV0JK7MoQOVWK6EYd3KoaGcZ9biJ+R9QXLx/bcqQlgCFS2 aX5F3x3jaBQkxOu6DabGIEHVcRkr1gJaWNiPUOMObf/K8mSAiMZq5zPuLk7MNJRO YEFU4W5bbcmk8ld1rJgEr1Mq0GBnYzuQTlNv+BeGi21L7J8p4UoU9R5dXOzuplIX q9LiQzTrMj4XsE2O5z+2iUPbeEn9DSF3kN3s3Yxn62qG7eX+4DI=
=jnNE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Beatrice Torracca@21:1/5 to All on Wed Jun 10 06:10:01 2020

aGkuwqAKRnJvbTogVGhvbWFzIFZpbmNlbnQgPHRob21hc0B2aW5jLW5ldC5mcj4gRGF0ZTogNi8x MC8yMCAgMDE6NDggIChHTVQrMDE6MDApIFRvOiBkZWJpYW4taTE4bkBsaXN0cy5kZWJpYW4ub3Jn IFN1YmplY3Q6IFJlOiBSaXM6IGRkdHAyLmQubiBkb3duIGFnYWluIGJ1dCB0aGF0J3Mgb2shID4+ ID4+IEkgaW1hZ2luZSBJIHNob3VsZCBjaGFuZ2UgdGhlIHdhcm5pbmcgdGhlbi4gQW55IHN1Z2dl c3Rpb24/PlNpbXBseSByZW1vdmUgaXQ/b2suIEkgd2lsbCBkby4+IEkgcmV0cmlldmVkIGEgbGlz dCBvZiBhbGwgdHJhbnNsYXRpb25zwqA+IGFjY2VwdGVkIGJldHdlZW4gTWFyY2ggMXN0IGFuZD4g QXByaWwgMTV0aCBoZXJlOsKgPiBodHRwczovL3N0b3JtLmRlYmlhbi5uZXQvZ3JhaW4vSnhLZFRS U3hHSGtCd3o0WHp6YzlFdz4gQW5kcmV5IGFuZCBJIGhhdmUgc3RhcnRlZCB0byByZXZpZXcgYWxs IG9mPiB0aGVtIGFuZCB3ZSdyZSByZW9wZW5pbmc+wqB0cmFuc2xhdGlvbnMgZm9yIHJldmlldyB3 aGVuIHdlIGZpbmQ+IGVuY29kaW5nIGlzc3Vlcy5JIGRvbnQgaGF2ZSBwZXJtaXNzaW9ucyB0byBz ZWUgdGhlIGdyYWluLiBJIGFtIG5vdCBhIERNLsKgIEkgd291bGQgZ2xhZGx5IGhlbHAgd2l0aCB0 aGUgcmV2aWV3LCBpZiB0aGVyZSdzIGEgd2F5LiBNYXliZSBzZW5kIG1lIGEgaGFyZCBjb3B5IGFu ZCBJIGNhbiB3b3JrIGZyb20gdGhlIGJvdHRvbSB1cD8gb3IgYW55IG90aGVyIHdheSB5b3UgbWln aHQgdGhpbmssIGlmIGl0IGNhbiBiZSB1c2VmdWwgYW5kIG5vdCBvbmUgbW9yZSBoaW5kcmFuY2Uu Z29vZCBkYXksYmVhdHJpY2VQcy4gd3JpdGluZyBmcm9tIHBob25lLg==

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPmhpLiZuYnNwOzxk aXY+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMDAlO2NvbG9yOiMwMDAwMDAiIGRp cj0iYXV0byI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+PGRpdj48YnI+PC9kaXY+PGRpdj5Gcm9t OiBUaG9tYXMgVmluY2VudCAmbHQ7dGhvbWFzQHZpbmMtbmV0LmZyJmd0OyA8L2Rpdj48ZGl2PkRh dGU6IDYvMTAvMjAgIDAxOjQ4ICAoR01UKzAxOjAwKSA8L2Rpdj48ZGl2PlRvOiBkZWJpYW4taTE4 bkBsaXN0cy5kZWJpYW4ub3JnIDwvZGl2PjxkaXY+U3ViamVjdDogUmU6IFJpczogZGR0cDIuZC5u IGRvd24gYWdhaW4gYnV0IHRoYXQncyBvayEgPC9kaXY+PGRpdj48YnI+PC9kaXY+PC9kaXY+Jmd0 OyZndDsgPGJyIGRpcj0iYXV0byI+Jmd0OyZndDsgSSBpbWFnaW5lIEkgc2hvdWxkIGNoYW5nZSB0 aGUgd2FybmluZyB0aGVuLiBBbnkgc3VnZ2VzdGlvbj88YnIgZGlyPSJhdXRvIj48YnIgZGlyPSJh dXRvIj4mZ3Q7U2ltcGx5IHJlbW92ZSBpdD88YnIgZGlyPSJhdXRvIj48YnIgZGlyPSJhdXRvIj5v ay4gSSB3aWxsIGRvLjxiciBkaXI9ImF1dG8iPjxiciBkaXI9ImF1dG8iPiZndDsgSSByZXRyaWV2 ZWQgYSBsaXN0IG9mIGFsbCB0cmFuc2xhdGlvbnMmbmJzcDs8ZGl2IGRpcj0iYXV0byI+Jmd0OyBh Y2NlcHRlZCBiZXR3ZWVuIE1hcmNoIDFzdCBhbmQ8L2Rpdj48ZGl2IGRpcj0iYXV0byI+Jmd0OyBB cHJpbCAxNXRoIGhlcmU6Jm5ic3A7PC9kaXY+PGRpdiBkaXI9ImF1dG8iPiZndDsgaHR0cHM6Ly9z dG9ybS5kZWJpYW4ubmV0L2dyYWluL0p4S2RUUlN4R0hrQnd6NFh6emM5RXc8YnIgZGlyPSJhdXRv Ij48YnIgZGlyPSJhdXRvIj4mZ3Q7IEFuZHJleSBhbmQgSSBoYXZlIHN0YXJ0ZWQgdG8gcmV2aWV3 IGFsbCBvZjwvZGl2PjxkaXYgZGlyPSJhdXRvIj4mZ3Q7IHRoZW0gYW5kIHdlJ3JlIHJlb3Blbmlu ZzwvZGl2PjxkaXYgZGlyPSJhdXRvIj4mZ3Q7Jm5ic3A7dHJhbnNsYXRpb25zIGZvciByZXZpZXcg d2hlbiB3ZSBmaW5kPC9kaXY+PGRpdiBkaXI9ImF1dG8iPiZndDsgZW5jb2RpbmcgaXNzdWVzLjxi ciBkaXI9ImF1dG8iPjxiciBkaXI9ImF1dG8iPkkgZG9udCBoYXZlIHBlcm1pc3Npb25zIHRvIHNl ZSB0aGUgZ3JhaW4uIEkgYW0gbm90IGEgRE0uJm5ic3A7IEkgd291bGQgZ2xhZGx5IGhlbHAgd2l0 aCB0aGUgcmV2aWV3LCBpZiB0aGVyZSdzIGEgd2F5LiBNYXliZSBzZW5kIG1lIGEgaGFyZCBjb3B5 IGFuZCBJIGNhbiB3b3JrIGZyb20gdGhlIGJvdHRvbSB1cD8gb3IgYW55IG90aGVyIHdheSB5b3Ug bWlnaHQgdGhpbmssIGlmIGl0IGNhbiBiZSB1c2VmdWwgYW5kIG5vdCBvbmUgbW9yZSBoaW5kcmFu Y2UuPC9kaXY+PGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48ZGl2IGRpcj0iYXV0byI+Z29vZCBk YXksPC9kaXY+PGRpdiBkaXI9ImF1dG8iPjxicj48L2Rpdj48ZGl2IGRpcj0iYXV0byI+YmVhdHJp Y2U8L2Rpdj48ZGl2IGRpcj0iYXV0byI+PGJyPjwvZGl2PjxkaXYgZGlyPSJhdXRvIj5Qcy4gd3Jp dGluZyBmcm9tIHBob25lLjwvZGl2PjwvYm9keT48L2h0bWw+

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Thomas Vincent@21:1/5 to All on Wed Jun 10 21:10:01 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WHdEyeeJ0iWwTpXrXLr6RFJKkoupEpb6K
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

Le 10/06/2020 à 06:04, Beatrice Torracca a écrit :

I dont have permissions to see the grain. I am not a DM. I would gladly help with the review, if there's a way. Maybe send me a hard copy and I
can work from the bottom up? or any other way you might think, if it can
be useful and not one more hindrance.

I'm really sorry, I sent the wrong link. Here is a correct one: https://storm.debian.net/shared/hD6Wh9itnIsQtrSJIg-T-uKi6tonzgkKdGWJZliYmdH

Thomas

good day,

beatrice

Ps. writing from phone.

--WHdEyeeJ0iWwTpXrXLr6RFJKkoupEpb6K--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7hLwsACgkQenSQZNOP EaNssxAA0PoRA5lI2pBizWdM+Hbb3seS/PwCUWabVWkCisg8zcTswUVeqBNhvcoQ fRoAaITL87XavRIkMlY/rDD3pwrJQhzN5oVBRRCKPHz1hWekZqXk/yRnQaYq86dT mG+zDg9hND7I3ALO+daWtA4sYsktFfuYZ78AobwHtRm1iat+EVvzKrO2BNuS/4pW SMgnBS+QiUoM+6oUpm1CF8XQWwUsZ6xRIbduugsFOjd0i7+9BmGhf/cvmQXU8E/d 6Nydh+ewvSQ/cJl/81PVl5i/St3fV/ytEiBr2G2g8jAbajyYjxi6JNPh68Gt50uH azsleHd5ScLot+2+3Sx0gd7SYKEa/1oZp6cjIWxaG75lUbT8zALwZ+CKaWNWEWG8 2kr3KfPQTK7uKinLbEehUVNHc2qxoKsOVRDuC2JytLUXm5KSHcblqupiYQHh7t2/ AKSqa9rgMPORKdGI+gYdtZmFjLqNpKbgnR4/HIehQTmYoEe0qzD6pGeT1bR/f4DA IlNM56zvlXTQ4l1qSD8C/lfrThHWZKF+TpDyq0pk+d2CzohRN57CRceGc+m0BQVa Rc5l7ShOAxUKq3M4Q9J+mt60aTehekkzZZUPcFcetXvdWSl3NIIo3kH23Oxk7bsa Lygldv7aCWVw0XWWlXr+hv36O4FEClGEmWjc6GW0SsN6U926lgk=
=HedR
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Joe Dalton@21:1/5 to All on Sat Jun 13 21:20:01 2020

Hi have we lost the functionality where the old translations was shown in the bottom?
if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 à 13:06, Beatrice Torracca a écrit :

On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost,
but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one
month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it
will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

<div> Hi have we lost the functionality where the old translations was shown in the bottom? if yes, that is a serious setback. and is https://ddtp.debian.org/ the new official place to make translations? bye 
Joe </div> <div class="yahoo_quoted" style="margin:10px 0px 0px 0.8ex;border-left:1px solid #ccc;padding-left:1ex;"> <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#
26282a;"> <div> Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>: </div> <div> </div> <div> </div>
<div><div dir="ltr">Hi, Le 09/06/2020 à 13:06, Beatrice Torracca a écrit : > On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote: > >> In
the meantime, Beatrice added a warning on ddtp.d.o pages to state >> that it was still a testing instance and that all work done may be lost, >> but some contributors continued to provide translations (maybe
they did >> not see the warning) and I did not want to have them loose more than one >> month of work, so the goal then became to fix all broken translations, >> and we're still at that
step, unfortunately. :( > > Maybe (next time) it would be enough to comunicate this kind of > decision on the list (unless I missed it, and I apologize if I > did). We (Italian
team) followed rules and missed a lot of months of work. Yes indeed. I know how such long breaks can be demotivating. > > I imagine I should change the warning then.
Any suggestion? Simply remove it? > >> So, to sum up: >> - ddtp.d.o seems to be working fine now and all translations done on it >>  will be kept >> - translations accepted between roughly mid-march and mid-april may >>  contain badly encoded accented characters, they all need to be >> 
reviewed and fixed (probably manually) > > Is there an (easy) way for you to have a list of them? Not the wrong > ones, all the translations accepted in that problematic time >
interval. Each language could review their own translations. I surely > can do it for Italian, maybe other languages too. I retrieved a list of all translations accepted between March 1st and April 15th here: <a shape="rect" href="https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew" target="_blank">https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew</a> Andrey and I have started to review all of them
and we're reopening translations for review when we find encoding issues. > >>> I can help somehow to move forward and fix >>> remaining issues? >> >> Well, first, thanks for the ping and the help offer! :) > > Yes, thanks a lot to s3v for the ping. I planned to do it for a long > time and never did.
I apologize with the Italian team for that. I > stalled their work long enough. > >>> Thanks a lot  for taking care of this job. > > +1 Thanks a
lot for the work on this. It is indeed much appreciated. Thanks for the thanks. :)<div class="yqt1547452285" id="yqtfd35996"> Thomas </div></div></div> </div>
</div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Daniele Forsi@21:1/5 to All on Sat Jun 13 22:20:01 2020

Il giorno mer 10 giu 2020 alle ore 01:48 Thomas Vincent ha scritto:

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

How do you find those with encoding issues?
Do you have a way to fix them automatically?

I think you can fix them using iconv, for example from the terminal,
this fixes the "è" and the "ù":

wget "https://ddtp.debian.org/ddt.cgi?language=it&desc_id=273173" --output-document=273173.orig
iconv -f utf-8 -t latin1 273173.orig --output=273173.txt

--
Daniele Forsi

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Thomas Vincent@21:1/5 to All on Sun Jun 14 19:20:01 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oxRN1jWF7tq7dqYeYJ1uDD77bwD3DUqGG
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi Joe,

Le 13/06/2020 à 21:18, Joe Dalton a écrit :

Hi have we lost the functionality where the old translations was shown
in the bottom?

Thanks for the report!
Do you have an example of this?

The translation/review page is probably looking for the former
translation/diff at the wrong location (for instance, on ddtp2.debian.net).
We are currently looking into this issue and may have fixed some of its occurrences thanks to the patch provided by s3v.

Best regards,
Thomas

if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe
Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 à 13:06, Beatrice Torracca a écrit :

On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost, >>> but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one >>> month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it >>> will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

--oxRN1jWF7tq7dqYeYJ1uDD77bwD3DUqGG--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7mWbsACgkQenSQZNOP EaNjiQ//dr25fi2u9GQWL5iT7BItg8veqAVwQXkb6eLkjtvoXBZqDdAkAmXM58Si AMv8dJdMHNh99GkfGZpSSJaqUYEmDncsV3wZiHPona8Kt1Zp3oy92UGWmwT5OXSP fafW80Pe1+2LAUPAykbeb40UygLy1feMVv3KMBkmqIaTZQOT33nHRH06niF9zEO0 chZUOSrTxUUaV/lkOwmhczzFa5O8yZvfJ7N5rwQ/J1u8+V/+nbEr2K55KG4Mqeaw 1Muh1jjZV67Sx+xSSZr7CGgoeCI2HCU6M+HLYEoHoHUgSURIR6Tw7BMP2MR6/r5T g95E9XCzcr71yjiKIiM7GmCfE8krJa2VK4/y2mrWlQW/7iCx5TNkO68+3/Bllp3t I9MwJ65VMfwINcQJe+HCXTIFP7C56i2d/92eHpcj3oKukYIujJLCJesEsQhSe2bI LIn0It4MqmhHY75zPTF1u9YR/piX60v/z4x9kbcvGlD7jRPZILf0Mkler8CdtuNM 8AiSwsSSUPrwNtqHhtvz3+GKCNsKV6CCWrkNU5lvTfdp+x6yXi9Y8qIDQ3Dqfuns vtEsEtgWhnRACaaMk1AdOKM6TwFdFUrkE84Fppw7SaTw0d6BXBK0z2TP9QSlPpNP PTcGIFBLM9fIcpUz3FtA0korNY8hPT90QTOSTAdY/KQYyNzl8ks=
=60Jk
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Thomas Vincent@21:1/5 to All on Sun Jun 14 19:40:01 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --BwsdKUTKr4ernGt8s9MYmDaotya4Lsovh
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi Daniele,

Le 13/06/2020 à 22:14, Daniele Forsi a écrit :

Il giorno mer 10 giu 2020 alle ore 01:48 Thomas Vincent ha scritto:

Andrey and I have started to review all of them and we're reopening
translations for review when we find encoding issues.

How do you find those with encoding issues?

I just read the descriptions, but I know that Andrey and s3v used
scripts to automatically detect errors.

Do you have a way to fix them automatically?

In most languages affected, a manual correction is enough, given the low
number of packages affected.
In Italian, all the translations we fetched seem to be already in
review, so I assume you found an efficient way to deal with them. :)

I think you can fix them using iconv, for example from the terminal,
this fixes the "è" and the "ù":

wget "https://ddtp.debian.org/ddt.cgi?language=it&desc_id=273173" --output-document=273173.orig
iconv -f utf-8 -t latin1 273173.orig --output=273173.txt

That's super useful, thanks!

Thomas

--
Daniele Forsi

--BwsdKUTKr4ernGt8s9MYmDaotya4Lsovh--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7mX7QACgkQenSQZNOP EaPbRA//fY1PaHl+eHIq5DuesHMSzqnhKvkAjE6EQJbaEmeuOzFFm9OqDa+JBquQ bk2Hv2pxUezfT2DMkXwOHU/tuyEsrKL6P6eIpHjOxMau5Exi70d63y8N59qmAe9F JQANN19KcrBVSW7Jx1ibSeqnhT4WWm9N8jMYmPB0ISEVHnOPfMiVVRxR0f89cb7T cGJFTJqDEQksueRmX1yhJm9bHXnFUapyxYooHDd6k4C10ueQC/QY6p+i4grIcxjN 7zU7KLDCG8l7nJfEso+drBBjb/gAM/fE/ZoaUNR/Mdp124lYEDL4xZOeIJ/J5R6q hQGQ6+ff7/qdgxvhPnvQDvScKP1cF6KGW2+3skHeI5g0TUIxsZMHhNncCnqolj+Q KLUlcJk3sBliFYLrA4igTpYXZ44Y8RoC0B+s0IcGs5usn7EKwxYZXVXIx0ULZXNs 5H0jT/IB1DRBYmSsqNWdbST5DOyBlrh8isUM5+ifD+lK5vBy7/ae81yrHDgqvfld mB7IhJS0jBXUKg4zDLC1VqqxVOAiKh+Ow4+6zWojG07kmX9ke4RZjfmwkLkME9Ix KgC/K3+PfImHvEUq9Ovwyu8N59Ejd+ewVngDzKPoc8X7hqgIEnYHlYEgTcUy+GmM hnVBKjMyhVqZ4UseBFBOhgM5XG45nV8fN7YIqDp6vyjx3waY6ys=
=OXn+
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Joe Dalton@21:1/5 to All on Sun Jun 21 13:40:03 2020

Hi Thomas, I can confirm that the issue is now solved. I have the old translation now.
thanks
Joe

Den søndag den 14. juni 2020 19.10.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi Joe,

Le 13/06/2020 à 21:18, Joe Dalton a écrit :

Hi have we lost the functionality where the old translations was shown
in the bottom?

Thanks for the report!
Do you have an example of this?

The translation/review page is probably looking for the former
translation/diff at the wrong location (for instance, on ddtp2.debian.net).
We are currently looking into this issue and may have fixed some of its occurrences thanks to the patch provided by s3v.

Best regards,
Thomas

if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe
Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 à 13:06, Beatrice Torracca a écrit :

On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost, >>> but some contributors continued to provide translations (maybe they did
not see the warning) and I did not want to have them loose more than one >>> month of work, so the goal then became to fix all broken translations,
and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it >>> will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

<div> Hi Thomas, I can confirm that the issue is now solved. I have the old translation now. thanks Joe </div> <div class="yahoo_quoted" style="margin:10px 0px 0px 0.8ex;border-left:1px solid #
ccc;padding-left:1ex;"> <div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"> <div> Den søndag den 14. juni 2020 19.10.20 CEST
skrev Thomas Vincent <thomas@vinc-net.fr>: </div> <div> </div> <div> </div> <div><div dir="ltr">Hi Joe, Le 13/06/2020 à 21:18, Joe Dalton a écrit&
nbsp;: > Hi have we lost the functionality where the old translations was shown > in the bottom? Thanks for the report! Do you have an example of this? 
 The translation/review page is probably looking for the former translation/diff at the wrong location (for instance, on ddtp2.debian.net). We are currently looking into this issue and may have fixed some
of its occurrences thanks to the patch provided by s3v. Best regards, Thomas<div class="yqt8596575413" id="yqtfd96250"> > if yes, that is a serious
setback. > > and is > <a shape="rect" href="https://ddtp.debian.org/" target="_blank">https://ddtp.debian.org/</a> > > the new official place to make
translations? > bye > > Joe > Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent > <<a shape="rect" ymailto="mailto:thomas@vinc-net.fr" href="
mailto:thomas@vinc-net.fr">thomas@vinc-net.fr</a>>: > > > Hi, > > Le 09/06/2020 à 13:06, Beatrice Torracca a écrit : >> On
martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote: >> >>> In the meantime, Beatrice added a warning on ddtp.d.o pages to state >>> that it was still a testing instance
and that all work done may be lost, >>> but some contributors continued to provide translations (maybe they did >>> not see the warning) and I did not want to have them loose more than one 
>>> month of work, so the goal then became to fix all broken translations, >>> and we're still at that step, unfortunately. :( >> >> Maybe (next time) it would be enough to
comunicate this kind of >> decision on the list (unless I missed it, and I apologize if I >> did). We (Italian team) followed rules and missed a lot of months of work. > >
Yes indeed. I know how such long breaks can be demotivating. > >> >> I imagine I should change the warning then. Any suggestion? > > Simply remove it? > >> >>> So, to sum up: >>> - ddtp.d.o seems to be working fine now and all translations done on it >>>  will be kept >> - translations accepted between roughly mid-march and mid-april may >>>  contain badly encoded accented characters, they all need to be >>>  reviewed and fixed (probably manually) >> >> Is there an (easy) way for you to have a list of them? Not the wrong >> ones, all the translations accepted in that problematic time >> interval. Each language
could review their own translations. I surely >> can do it for Italian, maybe other languages too. > > I retrieved a list of all translations accepted between March 1st and >
April 15th here: <a shape="rect" href="https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew" target="_blank">https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew</a> > > Andrey and I have started to review all of
them and we're reopening > translations for review when we find encoding issues. > >> >>>> I can help somehow to move forward and fix >>>>
remaining issues? >>> >>> Well, first, thanks for the ping and the help offer! :) >> >> Yes, thanks a lot to s3v for the ping. I planned to do it for a long >> time and never did. I apologize with the Italian team for that. I >> stalled their work long enough. >> >>>> Thanks a lot  for taking care of this job. >> >> +1 Thanks a lot for the work on this. It is indeed much appreciated. > > Thanks for the thanks. :) > > >
Thomas </div></div></div> </div> </div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Beatrice Torracca@21:1/5 to Joe Dalton on Sun Jun 21 15:30:01 2020

Hi all,

indeed the diff frame is now back and working, but it seems to fetch the wrong old description sometimes.

For instance here
https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils

it shows the diff with version 815 (very old) instead of 276327 which is the previous one, as one can see here:

https://ddtp.debian.org/ddt.cgi?desc_id=277359

Personally I have not pinpoint how/when this happens, maybe keep an
eye on the issue or investigate how the code decide what diff to show.

I am really happy to see the whole DDTSS system get back in track for good.

In the past days I checked the Etherpad with list of character-coding
affected description and I annotated all the fixed ones I found with a
"FIXED" at the end of the line. Italian is all fixed now, as most
other languages. As far as I can see there are less than an handful of
fr translations to fix and then everything should be without issues.

Thanks again a lot to all who worked on this,

beatrice

On domenica 21 giugno 2020, at 11:32 +0000, Joe Dalton wrote:

Hi Thomas, I can confirm that the issue is now solved. I have the old translation now.
thanks
Joe

Den s�ndag den 14. juni 2020 19.10.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi Joe,

Le 13/06/2020 � 21:18, Joe Dalton a �crit�:

Hi have we lost the functionality where the old translations was shown
in the bottom?

Thanks for the report!
Do you have an example of this?

The translation/review page is probably looking for the former translation/diff at the wrong location (for instance, on ddtp2.debian.net). We are currently looking into this issue and may have fixed some of its occurrences thanks to the patch provided by s3v.

Best regards,
Thomas

if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe
Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 � 13:06, Beatrice Torracca a �crit�:

On marted� 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state
that it was still a testing instance and that all work done may be lost, >>> but some contributors continued to provide translations (maybe they did >>> not see the warning) and I did not want to have them loose more than one >>> month of work, so the goal then became to fix all broken translations, >>> and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it >>>� will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot� for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

--

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEhBuuTqYTMX2CMr6YL+1Y7ldknz8FAl7vXoUACgkQL+1Y7ldk nz8z+BAAm2MH1OEnMEFiFJrVkIzpONSY3S8XdzcWZb4f9xz/S1znJHz3I57ACWXB TalU9dI+qgVGQ85QCa701moH0yCraTpcyd9s2MXDuJnIKGUDeZhbPP/u+ShkVpKy AbbYOgzrGA9CiUbs0Na6LgmWyovRDlQeP4QYqjHHr4SmiMqBfJ43xgfHk0ucwB3q ipX0KvCUDHvw8cklG+pFKrM6Jy9IenHWlF4ybR7OJCSO2nkMUC0BndDbnsypdwlo vrIB1xw2klipTgIMWYUMzXMJRZko02nSZTZr9f1yIzNYmtjoQ77X1TC7MxLYsPOw yrK8a/ogCCEH0HQ2J1K0vCq6wbTbTKOUT2WXO+e7zXMKgaTnGWneTUagvDb+HyQC SRp/CO4PaRzcT/PUmspMQxzfP3MpGNgmlbzIo3PNzmGRrqxOYgKyK0LB/CtMlk6f RUSx3tzb0Gz43Mh9+W/lQr4L6yRS5kyYjyN8EEmyM/xaIjEWKmKfpMdWJxwoygBb TXeiwl35oFVXHSQ0qe4wOlT63urInUrfUeVvvebTtHDF8f0l934MulOUoVZSZVy0 +gXT7n/0cwobbQlUnqs2YrQ1VMjLna+khkdJede2MceIgNTsU+2vjnZK4tpNmZal RhgZCStJUwSR1H0NseSKanFh03qoSMtPrbJMqhFyzBLxMmOvZOw=
=2BU1
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Thomas Vincent@21:1/5 to All on Sun Jun 21 17:00:01 2020

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9mkhsXBqFMxZNxprQPiAn40cpNJiMNghZ
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi !

Le 21/06/2020 � 15:20, Beatrice Torracca a �crit�:

indeed the diff frame is now back and working, but it seems to fetch the wrong old description sometimes.

For instance here https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils

it shows the diff with version 815 (very old) instead of 276327 which is the previous one, as one can see here:

https://ddtp.debian.org/ddt.cgi?desc_id=277359

Personally I have not pinpoint how/when this happens, maybe keep an
eye on the issue or investigate how the code decide what diff to show.

s3v reported the issue earlier this week and we just updated trabaci
with a fix.

I re-fetched bsdutils in italian and the diff now looks ok. Please let
us know if you see other issues.

I am really happy to see the whole DDTSS system get back in track for good.

So are we!

In the past days I checked the Etherpad with list of character-coding affected description and I annotated all the fixed ones I found with a "FIXED" at the end of the line. Italian is all fixed now, as most
other languages. As far as I can see there are less than an handful of
fr translations to fix and then everything should be without issues.

Yes, some of the french translations got hit with an other encoding
issue, so it delayed a little their resolution. I believe that they are
now all fixed, I just need to double check them.

The next step is to get in touch with the ftp masters so they now
retrieve the translations from ddtp.d.o instead of ddtp2.d.n.
I'll post an update when we know more about this.

Thanks again a lot to all who worked on this,

Thank you and all the translators who helped us review 700+ descriptions
and fix all the broken ones. :)

Thomas

beatrice

On domenica 21 giugno 2020, at 11:32 +0000, Joe Dalton wrote:

Hi Thomas, I can confirm that the issue is now solved. I have the old translation now.
thanks
Joe

Den s�ndag den 14. juni 2020 19.10.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi Joe,

Le 13/06/2020 � 21:18, Joe Dalton a �crit�:

Hi have we lost the functionality where the old translations was shown
in the bottom?

Thanks for the report!
Do you have an example of this?

The translation/review page is probably looking for the former
translation/diff at the wrong location (for instance, on ddtp2.debian.net). >> We are currently looking into this issue and may have fixed some of its
occurrences thanks to the patch provided by s3v.

Best regards,
Thomas

if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe
Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent
<thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 � 13:06, Beatrice Torracca a �crit�:

On marted� 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state >>>>> that it was still a testing instance and that all work done may be lost, >>>>> but some contributors continued to provide translations (maybe they did >>>>> not see the warning) and I did not want to have them loose more than one >>>>> month of work, so the goal then became to fix all broken translations, >>>>> and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of work. >>>

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on it >>>>> � will be kept
- translations accepted between roughly mid-march and mid-april may
� contain badly encoded accented characters, they all need to be
� reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and
April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening
translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot� for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

--9mkhsXBqFMxZNxprQPiAn40cpNJiMNghZ--

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl7vdBcACgkQenSQZNOP EaMgAw/9Fnm6qJTpSbGO1OOTtf52r7caygUqNQxJbUxeDQUQ0lsFs7q6ng72k/YH fuRfEFwEVx1TVub5s+oX7abhdiLBirQvNgqP8d9G2I1FDuTeDGb5Gp+AoToJCtUL 9U/UTP2RZ/MeJGrdRnsx0gDwXkWAiMGk3SA/aHjvhsahVJewMKsgBLA5NEsSNKGL nQhd1nSYV2Pko4uclShPesxlnrKtGqA7cDifoUwJPOra4vwANY1gVXUKJnMTweCi j5ItXHuhpzfDFYH4zyt7JFQMvanoJGD3b8msPP3kJyds/3M+4wtoHseIPDyKfA2m gktW5vZ5qCBc337i62HUktfYQ9R4WRS7c3f3g8SsWDO7cwFUDE45ZJtslOESpj94 N4CH6lO/pEJY3NqG/FOpGuXDZuV34zEW0/3eU3IQTV0H25uWNEK48tOdZAgDIQXD 7aPAuuOwNqwbWQqMC7LPdNqBMg4/veMME+43iLyWxptp0Bl88VjkpqLX8e55i0Xl rSQ4JLxsZvdrQaQJlQQ6DG7qmcqf70kqzJReq0IJ7i8Zl6DaLhv1qhcuXVeOjGHp JuFJIGsgymtwvgqKEsCfnr4Xf1jwSGU4XH2wrS9NiA9L+ZT03ge0YibKOaTnPmRw Ya6CWpzU1Mks8tWs/9Lc8FHf3DNS1JccAkxAZiHfq4YeOq5y5w4=
=gP2S
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Andrey Skvortsov@21:1/5 to All on Sun Jun 21 16:50:01 2020

Hi Beatrice,

Thank you for the feedback. Thomas fixed that problem today, just have not pushed the production server. Now it's out and diff should be made against
the latest description.
Now forreview looks ok, IMHO. https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils

On Sun, Jun 21, 2020 at 4:20 PM Beatrice Torracca <beatricet@libero.it>
wrote:

Hi all,

indeed the diff frame is now back and working, but it seems to fetch the wrong old description sometimes.

For instance here https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils

it shows the diff with version 815 (very old) instead of 276327 which is
the previous one, as one can see here:

https://ddtp.debian.org/ddt.cgi?desc_id=277359

Personally I have not pinpoint how/when this happens, maybe keep an
eye on the issue or investigate how the code decide what diff to show.

I am really happy to see the whole DDTSS system get back in track for good.

In the past days I checked the Etherpad with list of character-coding affected description and I annotated all the fixed ones I found with a "FIXED" at the end of the line. Italian is all fixed now, as most
other languages. As far as I can see there are less than an handful of
fr translations to fix and then everything should be without issues.

Thanks again a lot to all who worked on this,

beatrice

On domenica 21 giugno 2020, at 11:32 +0000, Joe Dalton wrote:

Hi Thomas, I can confirm that the issue is now solved. I have the old

translation now.

thanks
Joe

Den søndag den 14. juni 2020 19.10.20 CEST skrev Thomas Vincent <

thomas@vinc-net.fr>:

Hi Joe,

Le 13/06/2020 à 21:18, Joe Dalton a écrit :

Hi have we lost the functionality where the old translations was shown
in the bottom?

Thanks for the report!
Do you have an example of this?

The translation/review page is probably looking for the former translation/diff at the wrong location (for instance, on

ddtp2.debian.net).

We are currently looking into this issue and may have fixed some of its occurrences thanks to the patch provided by s3v.

Best regards,
Thomas

if yes, that is a serious setback.

and is
https://ddtp.debian.org/

the new official place to make translations?
bye

Joe
Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent <thomas@vinc-net.fr>:

Hi,

Le 09/06/2020 à 13:06, Beatrice Torracca a écrit :

On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote:

In the meantime, Beatrice added a warning on ddtp.d.o pages to state >>> that it was still a testing instance and that all work done may be

lost,

but some contributors continued to provide translations (maybe they

did

not see the warning) and I did not want to have them loose more than

one

month of work, so the goal then became to fix all broken

translations,

and we're still at that step, unfortunately. :(

Maybe (next time) it would be enough to comunicate this kind of
decision on the list (unless I missed it, and I apologize if I
did). We (Italian team) followed rules and missed a lot of months of

work.

Yes indeed. I know how such long breaks can be demotivating.

I imagine I should change the warning then. Any suggestion?

Simply remove it?

So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on

it

will be kept
- translations accepted between roughly mid-march and mid-april may
contain badly encoded accented characters, they all need to be
reviewed and fixed (probably manually)

Is there an (easy) way for you to have a list of them? Not the wrong
ones, all the translations accepted in that problematic time
interval. Each language could review their own translations. I surely
can do it for Italian, maybe other languages too.

I retrieved a list of all translations accepted between March 1st and April 15th here: https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew

Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.

I can help somehow to move forward and fix
remaining issues?

Well, first, thanks for the ping and the help offer! :)

Yes, thanks a lot to s3v for the ping. I planned to do it for a long
time and never did. I apologize with the Italian team for that. I
stalled their work long enough.

Thanks a lot for taking care of this job.

+1 Thanks a lot for the work on this. It is indeed much appreciated.

Thanks for the thanks. :)

Thomas

--

<div dir="ltr"><div>Hi Beatrice,</div><div> </div><div>Thank you for the feedback. Thomas fixed that problem today, just have not pushed the production server. Now it's out and diff should be made against the latest description.</div><div>Now
forreview looks ok, IMHO. </div><div><a href="https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils">https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils</a></div><div> </div></div> <div class="gmail_quote"><div dir="ltr" class="
gmail_attr">On Sun, Jun 21, 2020 at 4:20 PM Beatrice Torracca <<a href="mailto:beatricet@libero.it">beatricet@libero.it</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);
padding-left:1ex">Hi all, 

indeed the diff frame is now back and working, but it seems to fetch the wrong old description sometimes. 

For instance here 
<a href="https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils" rel="noreferrer" target="_blank">https://ddtp.debian.org/ddtss/index.cgi/it/forreview/bsdutils</a> 

it shows the diff with version 815 (very old) instead of 276327 which is the previous one, as one can see here: 

<a href="https://ddtp.debian.org/ddt.cgi?desc_id=277359" rel="noreferrer" target="_blank">https://ddtp.debian.org/ddt.cgi?desc_id=277359</a> 

Personally I have not pinpoint how/when this happens, maybe keep an 
eye on the issue or investigate how the code decide what diff to show. 

I am really happy to see the whole DDTSS system get back in track for good. 

In the past days I checked the Etherpad with list of character-coding affected description and I annotated all the fixed ones I found with a "FIXED" at the end of the line. Italian is all fixed now, as most other languages. As far as I can see there are less than an handful of 
fr translations to fix and then everything should be without issues. 

Thanks again a lot to all who worked on this, 

beatrice 

On domenica 21 giugno 2020, at 11:32 +0000, Joe Dalton wrote: 
> 
> 
> Hi Thomas, I can confirm that the issue is now solved. I have the old translation now. 
> thanks 
> Joe 
> 
> Den søndag den 14. juni 2020 19.10.20 CEST skrev Thomas Vincent <<a href="mailto:thomas@vinc-net.fr" target="_blank">thomas@vinc-net.fr</a>>: 
> 
> Hi Joe, 
> 
> Le 13/06/2020 à 21:18, Joe Dalton a écrit : 
> > Hi have we lost the functionality where the old translations was shown 
> > in the bottom? 
> 
> Thanks for the report! 
> Do you have an example of this? 
> 
> The translation/review page is probably looking for the former 
> translation/diff at the wrong location (for instance, on <a href="http://ddtp2.debian.net" rel="noreferrer" target="_blank">ddtp2.debian.net</a>). 
> We are currently looking into this issue and may have fixed some of its 
> occurrences thanks to the patch provided by s3v. 
> 
> Best regards, 
> Thomas 
> 
> > if yes, that is a serious setback. 
> > 
> > and is 
> > <a href="https://ddtp.debian.org/" rel="noreferrer" target="_blank">https://ddtp.debian.org/</a> 
> > 
> > the new official place to make translations? 
> > bye 
> > 
> > Joe 
> > Den onsdag den 10. juni 2020 01.48.20 CEST skrev Thomas Vincent > > <<a href="mailto:thomas@vinc-net.fr" target="_blank">thomas@vinc-net.fr</a>>: 
> > 
> > 
> > Hi, 
> > 
> > Le 09/06/2020 à 13:06, Beatrice Torracca a écrit : 
> >> On martedì 09 giugno 2020, at 00:47 +0200, Thomas Vincent wrote: 
> >> 
> >>> In the meantime, Beatrice added a warning on ddtp.d.o pages to state 
> >>> that it was still a testing instance and that all work done may be lost, 
> >>> but some contributors continued to provide translations (maybe they did 
> >>> not see the warning) and I did not want to have them loose more than one 
> >>> month of work, so the goal then became to fix all broken translations, 
> >>> and we're still at that step, unfortunately. :( 
> >> 
> >> Maybe (next time) it would be enough to comunicate this kind of 
> >> decision on the list (unless I missed it, and I apologize if I 
> >> did). We (Italian team) followed rules and missed a lot of months of work. 
> > 
> > Yes indeed. I know how such long breaks can be demotivating. 
> > 
> >> 
> >> I imagine I should change the warning then. Any suggestion? > > 
> > Simply remove it? 
> > 
> >> 
> >>> So, to sum up: 
> >>> - ddtp.d.o seems to be working fine now and all translations done on it 
> >>> will be kept 
> >>> - translations accepted between roughly mid-march and mid-april may 
> >>> contain badly encoded accented characters, they all need to be 
> >>> reviewed and fixed (probably manually) 
> >> 
> >> Is there an (easy) way for you to have a list of them? Not the wrong 
> >> ones, all the translations accepted in that problematic time > >> interval. Each language could review their own translations. I surely 
> >> can do it for Italian, maybe other languages too. 
> > 
> > I retrieved a list of all translations accepted between March 1st and 
> > April 15th here: <a href="https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew" rel="noreferrer" target="_blank">https://storm.debian.net/grain/JxKdTRSxGHkBwz4Xzzc9Ew</a> 
> > 
> > Andrey and I have started to review all of them and we're reopening 
> > translations for review when we find encoding issues. 
> > 
> >> 
> >>>> I can help somehow to move forward and fix 
> >>>> remaining issues? 
> >>> 
> >>> Well, first, thanks for the ping and the help offer! :) > >> 
> >> Yes, thanks a lot to s3v for the ping. I planned to do it for a long 
> >> time and never did. I apologize with the Italian team for that. I 
> >> stalled their work long enough. 
> >> 
> >>>> Thanks a lot for taking care of this job. 
> >> 
> >> +1 Thanks a lot for the work on this. It is indeed much appreciated. 
> > 
> > Thanks for the thanks. :) 
> > 
> > 
> > Thomas 
> 
> 

-- 
</blockquote></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

From Beatrice Torracca@21:1/5 to Thomas Vincent on Tue Jul 7 13:20:01 2020

On domenica 21 giugno 2020, at 16:52 +0200, Thomas Vincent wrote:

The next step is to get in touch with the ftp masters so they now
retrieve the translations from ddtp.d.o instead of ddtp2.d.n.
I'll post an update when we know more about this.

I think all translations, including the last French ones are now
ok. Any news on this following step of the process?

Thanks,

beatrice

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEhBuuTqYTMX2CMr6YL+1Y7ldknz8FAl8EWdQACgkQL+1Y7ldk nz9fRQ//VKUW2KK8ZnkR85/PbVz0LRjJa+UlS6n1Ye353eQBbnOmIai/XF9f0QQr geur0cWxS0853EkkVA0wozyx/qGxV4k0qfkNHCPeoqImenr+dLaz6eEsrqbZGRh0 t7ptHuNLXcq/t1+n91EnECmbe1GizZC1SrhqHr5Mt2+YdYBkeP9BkYs5lTaNf1JE 8DbaMWMswq+6hMQNnFOnB1WXyR4Di/ePsq9jkOEkHAnmooz80gtYSBnVoXgwVI2J AD8o04hQMD006ZUZqiI63AKTt0YyXtXktLYmufHEYxPa+RL0xPMT7byxFpCZPW+w jtpuesosx/1OfSJvTbgm/ttaG/Alt5gXN28N7wpnaVofICnkVQGRFnvv1jybvuKy EmdoAAUCmn5JhWagfdc2XCw5Ek8a8tgEWk03q3Z9hUoLNzJ7Fo2bMitZ1KBMnE5u 50Sj3Vg0EeTGrsZNJLuzwCNnhuhFut6SDPTaoJ5umbckJtnt6nCPwlZzWY/qsMLG ggWjsfTBy3KfbVKFbeTcsIEkVHcdT+rSTonRT4erB2EXS06RZaus3cBFtfgRKwq+ c8qtVKSdhwm8m9eMJh+VB+1oMsKKrFBgAZpE77fDoR7gRk/8G627Af+wlgDmwefu AdwjDu919XWyY7D35EWhRzRUXA9wU4aqCLFtSH3nk6BOzX7NVEg=
=3SQL
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Who's Online
Recent Visitors
- Guest
  Tue Jan 28 06:40:34 2025
  from /bin/busybox Cat /proc/self/ex via Raw
- Gwylbert
  Tue Jan 28 04:48:36 2025
  from Sydney, Nsw via Telnet
- Guest
  Tue Jan 28 03:02:48 2025
  from /bin/busybox Cat /proc/self/ex via Raw
- Keyop
  Tue Jan 28 00:51:06 2025
  from Huddersfield, West Yorkshire via SSH
- Keyop
  Tue Jan 28 00:50:25 2025
  from Huddersfield, West Yorkshire via SSH
- Keyop
  Tue Jan 28 00:49:39 2025
  from Huddersfield, West Yorkshire via SSH
- Guest
  Mon Jan 27 22:26:23 2025
  from /bin/busybox Cat /proc/self/ex via Raw
- Bob Worm
  Mon Jan 27 21:08:12 2025
  from Wales, Uk via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	407
Nodes:	16 (2 / 14)
Uptime:	14:07:32
Calls:	8,554
Calls today:	6
Files:	13,219
Messages:	5,925,565

Ris: ddtp2.d.n down again but that's ok!

Who's Online

Recent Visitors

System Info