What is the current status of the ongoing
transition?
I can help somehow to move forward and fix
remaining issues?
Thanks a lot for taking care of this job.
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
The current status is: needing motivation. :)
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)
I can help somehow to move forward and fix
remaining issues?
Well, first, thanks for the ping and the help offer! :)
Thanks a lot for taking care of this job.
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.
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.
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.
good day,
beatrice
Ps. writing from phone.
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.
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.
Andrey and I have started to review all of them and we're reopening translations for review when we find encoding issues.
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
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
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
>>> - translations accepted between roughly mid-march and mid-april may<br clear="none">>>> contain badly encoded accented characters, they all need to be<br clear="none">>>> reviewed and fixed (probably manually)<br clear="none">>><br clear="none">>> Is there an (easy) way for you to have a list of them? Not the wrong<br clear="none">>> ones, all the translations accepted in that problematic time<br clear="none">>> interval. Each language
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
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:Yes indeed. I know how such long breaks can be demotivating.
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?
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
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 oldtranslation 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, onddtp2.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,
lost,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
didbut some contributors continued to provide translations (maybe they
onenot see the warning) and I did not want to have them loose more than
translations,month of work, so the goal then became to fix all broken
work.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
Yes indeed. I know how such long breaks can be demotivating.
I imagine I should change the warning then. Any suggestion?
Simply remove it?
it
So, to sum up:
- ddtp.d.o seems to be working fine now and all translations done on
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
--
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 11:44:27 |
Calls: | 7,504 |
Calls today: | 1 |
Files: | 12,710 |
Messages: | 5,640,355 |