Hi Wolfgang, Thank you for all your work on this.
Wolfgang Schweer schreef op vr 21-08-2020 om 20:55 [+0200]: > > Yes; looking at the translated content as a whole seems to be a good way > to get an impression. Are important parts of the content translated? > Does the translation still make sense if single sentences are showing up > in English? Any choice is arbitrary to some extent. What I appreciate in this approach is that you try to put a focus on the question if in the first place a given translation is (still) meaningful. > > > After some percentage re-calculation now that the filtering is showing > effect and a look at the actual translation content, a value of 40-45% > seems to be adequate. (Audacity and ITIL 45%, the other ones 40% - this > is the k param value in po4a.cfg, the real percentage is higher because > of a smaller divisor.) As I understand it correctly, after the transition to two binary packages we would keep about the same situation in terms of generated manuals as before. Perhaps this is not that bad as an approach, and later on, after having had an evaluation of the new situation, we could still make adjustments if they seem preferable. > > > On the other hand, I would be inclined to be much more sloppy when it > > comes > > to more volatile media, such as debian-edu-doc at jenkins.debian.net, > > because users there could easily understand that this is work in > > progress. > > Therefore their expectations would be less high, I guess. Here we could > > for > > instance stick to the threshold of 15%, i.e. all translations that have > > entered the master branch. > > As far as I know, the content showing up at jenkins.d.n can't be > different. Holger would know better... I see. So let's drop that idea. > > All that said, with the k values from above, these packages with useful > content would be built (only legacy-pl and legacy-pt-br are really new): > > debian-edu-doc-da > debian-edu-doc-de > debian-edu-doc-en > debian-edu-doc-fr > debian-edu-doc-it > debian-edu-doc-ja > debian-edu-doc-nb-no > debian-edu-doc-nl > debian-edu-doc-zh-cn > > debian-edu-doc-nb - transitional package for debian-edu-doc-nb-no > debian-edu-doc-zh - transitional package for debian-edu-doc-zh-cn > > debian-edu-doc-legacy-en > debian-edu-doc-legacy-fr > debian-edu-doc-legacy-ja > debian-edu-doc-legacy-nb-no > debian-edu-doc-legacy-nl > debian-edu-doc-legacy-pl > debian-edu-doc-legacy-pt-br > debian-edu-doc-legacy-zh-cn > > First block: All packages contain Buster and Bullseye manuals > > Legacy block: > en, nb-no, nl: Audacity, ITIL and Rosegarden manuals > fr: Audacity and Rosegarden manuals > ja, pl, pt-br, zh-cn: Audacity manual Shouldn't "sv" be added here too? (49 translated strings out of 86 for audacity and 239 translated strings out of 598 for rosegarden) > > Please note that debian-edu-doc-es isn't contained in the list, a look > at the content as a whole confirmed me that the Spanish translations > (Buster, Bullseye) are no longer useful indeed - please check it > yourself on jenkins.debian.net. This is a bit sad, because in general the Debian Spanish localization team is doing a rather good job. I remember that back in 2019 I tried to give an extra impuls to translations that were lagging behind a bit ( https://lists.debian.org/debian-edu/2019/02/msg00065.html). The last Spanish translator (Rafael Rivas) replied in a positive way, but no updated Spanish translation was eventually submitted. Probably Rafael is too busy with other things. Because a concurrent translation update of a same language via different ways (e.g. a wihslist bug, git, weblate) eventually leads to chaos, Spanish is currently disabled on weblate. Perhaps I'd better enable Spanish on weblate from now on. I am unsure. For da, it, fr and ja we surely need to prepare a similar effort as back in 2019, timely before the freeze of bullseye. > > Any proposals how to proceed? Since no one objected and Holger expressed himself in favour of a split up into two binary packages, this split up probably can already be prepared and implemented. Some questions remain, though: Is it expected that these legacy manuals will ever get updated again or is it rather expected that they will only lead a dormant existence from now on, to disappear completely eventually? Does it still makes sense to have those manuals translatable on weblate? If so, I would definitely be in favour of splitting up the weblate translation effort in two separate projects too. If we do not want to make a definite decision now about how long we want to keep those legacy manuals alive, within what time frame do we want to reconsider the question whether keeping them alive still makes sense? -- Kind regards, Frans Spiesschaert
