Hi,
Il 20/10/19 12:12, Martijn van Oosterhout ha scritto:
> On Thu, 17 Oct 2019 at 21:15, lorenzo casiello
> wrote:
>> DDTP fetches descriptions by priority (higher first) and lowering python-*
>> package priority would be a good idea.
>> Current values:
>>
>> - python3-* packages have priority
On Thu, 17 Oct 2019 at 19:56, lorenzo casiello
wrote:
> 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
On Thu, 17 Oct 2019 at 21:15, lorenzo casiello
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-
Hi,
Le 17/10/2019 à 20:59, lorenzo casiello a écrit :
> 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:
>
>
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) package
Hi,
first of all, thank you for all your work in DDTP and for taking care
of this feature.
> So I went with allpartiallytranslatedpackages, for example:
> http://ddtp2.debian.net/ddt.cgi?allpartiallytranslatedpackages=nl
I'm very sorry for my intervention (I really didn't want to have to do this
Le 16/10/2019 à 15:41, s3v a écrit :
> 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 sche
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 nev
Hi,
Many thanks. It gives good idea of things. I thought mor French
packages were affected, but I see only 900 packages with a not complete
translation. On the other hand I guess that when we translate one
Python-xx or some bindings or python3, it will be easier to identify the
potential duplicat
Hoi,
On Tue, 15 Oct 2019 at 18:39, Beatrice Torracca 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 allpa
Hi,
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")
I did not check the bug/patch so I am not sure which of the 2 cases it
covers, or if it
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
wrote:
>
> Once identified this kind of repeat, how would be ap
For such devs like ddtp-ng, couldn't we submit a project for gsoc?
Regards
Jean-Philippe MENGUAL
Le 12/10/2019 à 12:45, Jean-Philippe MENGUAL a écrit :
>
> Le 10/10/2019 à 19:55, s3v a écrit :
>> Hi,
>>
>> #860386 [1] could be a good starting point to make the
>> translation process faster an
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 Tea
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 (
Hoi Jean,
On Sat, 5 Oct 2019 at 11:27, Jean-Philippe MENGUAL wrote:
> 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 al
Le 05/10/2019 à 11:27, Jean-Philippe MENGUAL a écrit :
> Hi,
>
> I have been a regular translator on the ddtp for some months, and had
> dialogs with the French team since the Marseille Minidebconf on May.
> Thanks to them for their support and motivation.
>
> My concern is that we are very few c
Hello Jean-Philippe,
Just some quick & partial answers.
Dixit Jean-Philippe MENGUAL, le 05/10/2019 :
>I have been a regular translator on the ddtp for some months, and had
>dialogs with the French team since the Marseille Minidebconf on May.
>Thanks to them for their support and motivation.
>
>My
18 matches
Mail list logo
