Hello David,
Am Sun, Feb 09, 2025 at 04:32:15PM +0100 schrieb David Kalnischkies:
> Am Sat, Feb 08, 2025 at 11:12:21AM +0000, schrieb Helge Kreutzmann:
> > there are three long standing open bugs with German translation
> > updates. I haven't seen any activity from Chris as well. Thus the
> > German translation shipped is quite outdated.
>
> Sorry! Looks like the first two never reached my inbox while the third
> did, but I seem to have mentally ticked it off as done as I saw Julian
> had merged a German translation update not noticing that those were
> different ones…
No problem. It's similar for me - for those project where I'm not in a
tight loop, I simply fire off the translation once reviewed and then
don't trace it in detail - only once in a while I look at the overview
pages. (And simply wondered about apt, for other projects, having them
in the BTS for months/years is not uncommon). And where it bothers me,
I perform l10n NMUs.
> I have to say that I hardly look at the BTS, just trying to keep up with
> what comes in as new and I doubt Julian is much different in this aspect,
> and we still manage to constantly accumulate more and more open bugs…
> So if something falls through the cracks… summary: if you haven't got
> a reply in lets say a week its unlikely you will get any without a ping.
Good to know. Then I will add this to my mental model for apt.
> Now that I looked, I see a few other updates linger there…
> As I accept that as my fault I will see about redemption.
I't not about fault, it's about finding a good procedure working for
everyone.
> > I would like to have a good/complete German translation of apt in
> > Trixie.
>
> Agreed, not only because I see lots of those strings as a LANG=de_DE.
>
>
> So, how are we proceeding?
>
>
> For po/de.po you are the last translator – I just merged the two strings
> from back then.
I'm in the process of performing the final review on the new strings,
so I expect to send you an updated po/de.po quite soon.
So for the procedure:
I will monitor the release package or the git at
https://salsa.debian.org/apt-team/apt.git
(whatever you prefer) and when I see de.po in need for an update, I
will pick it up, update the translation, get the review and then
submit it as a bug and ping you ~ 1 week if nothing has happened[1].
Is this the best procedure for you?
> For doc/po/de.po Chris is, but the last mail I got from him is from
> 2020 (he usually sent me the po via private mail). So, I would say
> we give him a chance to reply for a bit longer and otherwise I will see
> about merging them ~ next week otherwise.
Chris is MIA, I haven't seen a mail from in in a long time on
debian-l10n-german@lists.debian.org. I'm in the process of updating
the man page translation and will submit it as well. In case Chris
should return, I gladly hand it back to him, of course. I cannot give
you a deadline, though, atm.
> > David has tooling
>
> Not really. At least, I wouldn't call my script that gets a mail on
> stdin and does things based on the contents "tooling" as it mostly
> just (optionally) unpacks and moves the po file to the right place
> on disk, runs `msgfmt --check` and `msgmerge --previous` and commits
> them with a standard message and the translator as author. The "real"
> work of doing some plausibility checks like if it went to the l10n team
> is done manually…
That's similar to several projects I'm working on. For Dpkg, I use
Guillems script, otherwise I have my own.
> Personally, I prefer it this way as not every translator is comfortable
> with git and the various tools interacting with po files seem to have
> different formatting rules (and of course different versions of the same
> tool) so "manually" merging them prevents a reflow festival that is
> annoying to look at – and I like looking at translation diffs even if
> I don't understand a word as that occasionally spots an issue in the
> translation ~ or with the msgids.
I very well concur. As maintainer of manpages-l10n, I regularly spot
things as well and fix issues in languages I don't speak. Also the
reformatting is not nice, having people with different versions of
involved tools (on different distros), well - I wish gettext/po4a
would be more stable.
In manpages-l10n I simply rebuild the entire stack (around 12114 po
files) every night and fix the errors the next morning.
> Anyway, Julian does deal with MRs for folks who prefer that so either
> works and I have no problem with keeping my end up, although I should
> look into perhaps proactively find issues in mail delivery.
I'm quite contrary, working with diff, git and so on is fine, running
through MR is not my favorite work flow (i.e. I try to avoid this).
But the most important thing is to get the translations recompleted,
and I think at least for German we are on the right track. (And I
really like your support for translators - should I provide feedback
on this in bug reports or by direct mail?).
Greetings
Helge
[1] As stated, I'm monitoring several projects and the last step is
usually that I commit the updated file somewhere, but I learned
that this is not the desired workflow for apt.
--
Dr. Helge Kreutzmann debian@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
Attachment:
signature.asc
Description: PGP signature