Re: systemd-boot-installer_0.7_source.changes ACCEPTED into unstable
Hi,
Cyril Brulebois <kibi@debian.org> wrote (Thu, 26 Dec 2024 11:38:55 +0100):
> Debian FTP Masters <ftpmaster@ftp-master.debian.org> (2024-12-26):
> > systemd-boot-installer (0.7) unstable; urgency=medium
[...]
> I failed to spot this initially while having a look at this package, but
> it seems to me sl3 is not appropriate here: that's a package that
> doesn't show up in a default install, and yet it was penalizing a bunch
> of languages, leading to the “this translation is incomplete are you
> sure you want to proceed?” prompt right after language selection.
Hmm, according to https://d-i.debian.org/doc/i18n-guide/ch01s04.html#sublevels
sublevel3 is for "expert strings (some low priority features such as RAID,
encrypted partitions, etc.)" - aka not for default install.
So sl3 might not be that wrong.
However, sublevel4 is "specific to less-popular arches (such as powerpc, mips
or sparc) or used in experimental features".
That leads to the decision, which arch is popular and which is not.
But since arm64 is somewhat new, we could count that to the "not popular"
ones currently, for sure. Thus moving the strings to sl4...
But now we are at the point, where I ask myself, why that makes a difference?
Are all strings from sl4 and sl5 generally not considered, when calculating the
translation-status value?
That's at least not documented in the above quoted doc...
> If the level is indeed not appropriate, I'm not sure how transparent it
> is to change it (does it generate an extra burden on the translators?),
> but it'd be great if we could consider tweaking that in further updates.
I have a walk-through for this task, that can be done without problem.
Will do, when alpha1 is out.
(And: No, there's no extra burden or extra work for translators here.)
I should document how to do this in above doc BTW...
Holger
--
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Reply to: