This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --56ad0l7D0cweagR8zLWfuZMr2ZxoAy4HH
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Hi!
Le 08/03/2020 � 09:33, Beatrice Torracca a �crit�:
So far there was no official notification of the system transition done.
It would really be helpful if whoever is taking care of the transition
would inform the translators on how to behave.
It is not much about losing work (which would not be fair... but life
is not fair), but surely not to insert in the database a lot of coding mistakes that can have a big repercussion (if you consider automatic translations of all shared paragraphs).
For the moment, the changes made to ddtp.d.o are not retrieved by ftp
masters to update the package descriptions, so there is no reason to
worry about bad encodings spreading to descriptions.
In my opionion, officially there is a last dump of the old system and
no notification of an official system change. So that dump should be
the starting point of the new system if there is a choice to be made
on what to discard (better yet if everything can be kept! :) ).
What we fed to ddtp.d.o is the exact database dump I retrieved from
ddtp2.d.n. The issue seems to come from how Perl handles encodings. More specifically, the version of Debian running on ddtp2.d.n is quite old
while the one on ddtp.d.o is up to date, and that means that the
versions of Perl and some libraries are different. I'm not a Perl expert
at all, but apparently a lot has changed regarding encoding, which leads
to all the discrepancies you noticed.
We've been running this instance for some months and tried to fix all
the encoding issues we've seen, but clearly we missed some and we're
still working to correct them.
I did not expect it would take so long, apologies for that.
Anyway, that is my opionion and it counts 0. I can live with whatever
other choice is made. But I think it would be fair for translators to
at least know if they have to work on the new system (and try to take measures to save what's lost) or wait.
As a ddtp user, I really understand your frustration. Somehow, it's even
worse to see a (seemingly) working instance of it and not be sure it's
safe to use it than a plain "nothing works" outage. :(
I'm confident we can fix it soon and even correct all the encoding
issues that have been inserted recently, but for the moment, let's say
it's better to wait a little more.
Thomas
--56ad0l7D0cweagR8zLWfuZMr2ZxoAy4HH--
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE04s77v+Xj8bVqh42enSQZNOPEaMFAl5lihMACgkQenSQZNOP EaPuYQ//Tb9dKSsSc0/jGnmedFDwAhUWw9Y6XD8rm2UH+2mC92wDdGkbfq+C6d5g K9avsjZ14c4z3bfal255F3QK4bPUVezx+0kB0V42/PtJP7fREAtjMkp5CDVm0erj iVa1y+y4L9R1ih6Ux/7KxCgJQCgTUTBx5N+3IOSyhXCh/pB0eTTKLroNybOY9woM 7x+6OkGbNPBmaPHEnESvmR+Yet3jLhq326wR1w78ODh0A/c1oT9AyYbGp6VAEAd5 /TexZNGsHW9E3Uz+9HctPafz+HGqmOTcBALgCEB0OBp9SilmK9TNUGlLinOn1uf2 UK5Y8zze8bCRNqHaWSmzWiYg3yu7+bjSyqj8sAYbsq1cULTZjCsydeIEEsLxJrjR ix+5uIHbeoQJ91D+oZfgXnCEyOQBnSKrAQaq1HXHSlRhF1u7F/yvv/AitpFwjW7X kDSxF6XVRftLMZqneT4d6hTGemUnLEODEDkRwFUHAq7QF0dU4CIFG/XSCwu459iw JZsN+1B5mUg3uO40XG6fErveMAddQ5lH+SVifN7MvhToWfsdITqHA4a2fgtJgmhG QmCycx1MVTibfLO3Ww5+YWhBbY8O8lEN1VgrEk2UWoYouTYSBg4vucDrewVihxoN DaCZUU6dN0YmzXO7BZHKUmSip39ngpXBEckPB/5e0jEewPIz8Fw=
=XlLw
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)