My concern is that we are very few contrib, and the work is giant. Many packages, but also many movements in packages (descriptions updats, additional packages, etc). I do not see how human beings can hope to translate all the packages descs in such conditions someday and for how
long. Also because there as much work for translating as reviewing.
Le 10/10/2019 à 19:55, s3v a écrit :
Hi,
#860386 [1] could be a good starting point to make the
translation process faster and give Translation Teams the ability
to find untranslated descriptions (>2000 for German Team and Japanese
Team, >1500 for Spanish Team, >1000 for Russian Team and so on...)
which are almost identical to the (already translated) previous ones.
A good example is python3-alembic package which has 3 descriptions:
131737: Translated in 6 languages [2]
229048: Translated in 6 languages [3]
269405 (active): Translated in 2 languages [4]
but the diff is minimal [5].
That patch could be further improved by providing a link
to the diff between current untranslated description and last
translated description; however that diff can be easily retrieved
by visiting http://ddtp2.debian.net/ddt.cgi?package=packagename page
(eg. [6]) without making a larger (and slower) query against the
database (but maybe this is not a problem, I don't know).
Once identified this kind of repeat, how would be applied the "common" translation? Automatically?
Regards
My 2??.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860386
[2] http://ddtp2.debian.net/ddt.cgi?desc_id=131737
[3] http://ddtp2.debian.net/ddt.cgi?desc_id=229048
[4] http://ddtp2.debian.net/ddt.cgi?desc_id=269405
[5] http://ddtp2.debian.net/ddt.cgi?diff1=269405&diff2=229048
[6] http://ddtp2.debian.net/ddt.cgi?diff1=34849&diff2=15229
Once identified this kind of repeat, how would be applied the "common" translation? Automatically?
Hoi,
Interesting idea. I'm willing to apply the patch, though we'd need
some better name than "something".
allneartranslatedpackages
allpreviouslytranslatedpackages
Other ideas?
On Sat, 12 Oct 2019 at 12:45, Jean-Philippe MENGUAL
<jpmengual@debian.org> wrote:
Once identified this kind of repeat, how would be applied the "common" translation? Automatically?
In situations like the first where the change is an additional
paragraph, once done all descriptions where the same paragraph is
added would be automatically complete.
Groet,
--
Martijn van Oosterhout <kleptog@gmail.com> http://svana.org/kleptog/
yes, s3v idea is very good. I think the system calls incomplete
descriptions "partially translated". So maybe "allpartiallytranslatedpackages"? (this is different of course from "allpreviouslytranslated")
Hoi,
On Tue, 15 Oct 2019 at 18:39, Beatrice Torracca <beatricet@libero.it> wrote:
yes, s3v idea is very good. I think the system calls incomplete
descriptions "partially translated". So maybe
"allpartiallytranslatedpackages"? (this is different of course from
"allpreviouslytranslated")
So I went with allpartiallytranslatedpackages, for example:
http://ddtp2.debian.net/ddt.cgi?allpartiallytranslatedpackages=nl
Try this, see if it works as expected or if it needs some tweaks.
Groet,
a) python-* and python3-* have the same descs. We should be able to
translate both python and python3 translating one of them.
b) linux-*-dbg: the string is similar, the translation should be
automated, optionally put in the reviewing string for safety
Hi,
I believe automation requires a lot of work. We have:
- many languages
- many grammars
- many syntactic rules
- few contributors (none?)
- no top-level rules (e.g. policies to advice maintainers to write descriptions
using some schemas/variables).
Furthermore, avoiding an automatic (and never reviewed!) mistake by DDTP is better than a bunch of automatic translation handled properly, IMHO.
Maybe we should concentrate on "easily-to-translate" descriptions instead of automatic translations and addressing little problems
for speeding up translation workflow would be a immediate solution for improving
the "productivity".
Anyway I agree with kleptog: unfortunately DDTP doesn't have active contributors
both for little and big actions.
a) python-* and python3-* have the same descs. We should be able to
translate both python and python3 translating one of them.
python2 packages are going to be removed from sid/bullseye.
Therefore, there is no need to translate them. https://wiki.debian.org/Python/2Removal
b) linux-*-dbg: the string is similar, the translation should be
automated, optionally put in the reviewing string for safety
dforsi from Italian Team wrote a very useful script for translating linux-* packages: https://github.com/dforsi/debian-tools/raw/master/packages/ddtss/linux-packages.user.js
Note that this is on the way to "easily-to-translate" land, so it could not be
what you are looking for.
Kind regards and thanks for throwing a stone in the water.
So I went with allpartiallytranslatedpackages, for example: http://ddtp2.debian.net/ddt.cgi?allpartiallytranslatedpackages=nl
Try this, see if it works as expected or if it needs some tweaks.
Well they should not be fetched then. Could not we filter them to avoid useless work?
How such script could be applied as we have not control on the database?
What is the good workflow?
Hi,
Well they should not be fetched then. Could not we filter them to avoid
useless work?
DDTP fetches descriptions by priority (higher first) and lowering python-* package priority would be a good idea.
Current values:
- python3-* packages have priority 47
- python-* (but not *-doc) packages have priority 47
- python-*-doc packages have priority 46
This snippet:
 # Python2 packages will be removed from bullseye, let's lower their priority
 $prioritize -= 1 if $package =~ /^python-/i && $package !~ /-doc$/i;
added in Packages2db.pl [1] at line 358 (or around it) lowers priority by 1 (46 instead of 47).
Would something like this be useful to accomplish the job?
Please feel free to amend the code or completely change the approach, my
Perl knowledge is quite limited.
How such script could be applied as we have not control on the database?
What is the good workflow?
That is a user-level script for use with Greasemonkey or similar extensions, more context at https://github.com/dforsi/debian-tools/tree/master/packages/ddtss .
Please note that script translations must be updated if maintainer
changes package descriptions (not so often, fortunately).
I don't know how implementing this feature in DDTP and how to maintain it.
Kind Regards.
[1] https://salsa.debian.org/l10n-team/ddtp/blob/master/Packages2db.pl
--
ZE-Light e ZE-Pro: servizi zimbra per caselle con dominio email.it, per tutti i dettagli
Clicca qui http://posta.email.it/caselle-di-posta-z-email-it.php?utm_campaign=email_Zimbra_102014=main_footer/f
Sponsor:
Soluzioni di email hosting per tutte le esigenze: dalle caselle gratuite a quelle professionali su piattaforma Zimbra, da quelle su proprio dominio a quelle certificate PEC. Confronta le soluzioni
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=13326&d=17-10
--
ZE-Light e ZE-Pro: servizi zimbra per caselle con dominio email.it, per tutti i dettagli
Clicca qui http://posta.email.it/caselle-di-posta-z-email-it.php?utm_campaign=email_Zimbra_102014=main_footer/f
Sponsor:
Idee regalo classiche o alternative? Trova l'offerta migliore in un click
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=13327&d=17-10
DDTP fetches descriptions by priority (higher first) and lowering python-* package priority would be a good idea.
Current values:
- python3-* packages have priority 47
- python-* (but not *-doc) packages have priority 47
- python-*-doc packages have priority 46
This snippet:
# Python2 packages will be removed from bullseye, let's lower their priority
$prioritize -= 1 if $package =~ /^python-/i && $package !~ /-doc$/i;
added in Packages2db.pl [1] at line 358 (or around it) lowers priority by 1 (46 instead of 47).
but I believe "allpreviouslytranslated" is more appropriate.
Not *ALL* partially translated packages are listed in that page, but only previously translated ones in a certain language.
And packages listed in that page may be completely untranslated if
maintainer changed all paragraphs of the current description.
Please, can you push these little changes? (Sorry for not providing a patch but
I can't see the commit on Salsa [6])
On Thu, 17 Oct 2019 at 21:15, lorenzo casiello
<lorenzo.casiello@email.it> wrote:
DDTP fetches descriptions by priority (higher first) and lowering python-* >> package priority would be a good idea.
Current values:
- python3-* packages have priority 47
- python-* (but not *-doc) packages have priority 47
- python-*-doc packages have priority 46
This snippet:
# Python2 packages will be removed from bullseye, let's lower their priority
$prioritize -= 1 if $package =~ /^python-/i && $package !~ /-doc$/i;
added in Packages2db.pl [1] at line 358 (or around it) lowers priority by 1 >> (46 instead of 47).
Seems like a good idea, so I did it.
Have a nice day,
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 13:40:22 |
Calls: | 7,505 |
Calls today: | 2 |
Files: | 12,710 |
Messages: | 5,640,571 |
Posted today: | 1 |