Bug#1001908: manpages-de: manpage of "shutdown" not up-to-date

[Mario Blättermann]

Hello all,

Am Fr., 24. Dez. 2021 um 10:27 Uhr schrieb Helge Kreutzmann
<debian at helgefjell.de>:
>
> Hello Mark,
> On Fri, Dec 24, 2021 at 08:13:56AM +0000, Mark Hindley wrote:
> > [Adding CC debian-init-diversity at chiark.greenend.org.uk]
>
> And adding Mario, manpages-l10n upstream maintainer as well.
>
> > Thanks for this.
>
> You are welcome, and thanks for considering.
>
> > On Thu, Dec 23, 2021 at 05:39:20PM +0100, Helge Kreutzmann wrote:
> > > In Debian we have the situation that some man pages are shipped by
> > > several packages. This is fine for the english versions, as there the
> > > alternatives mechanism takes care of this.
> > >
> > > For translated man pages this is not possible (at least currently), so
> > > as manpages-l10n we have to decide which upstream to follow.
> > >
> > > Until now we chose System-V over Systemd. However, this bug report
> > > showed that this causes confusion and I will ask manpage-l10n upstream
> > > to switch Debian to Systemd as well.
> >
> > I see that manpage-l10n upstream switching to the default init makes sense for
> > the majority.
> >
> > > Since all other distributions we support already use the Systemd
> > > version, this means the translations we currently have we vanish for
> > > Sysv-Init users if nothing else happens. (#3 below)
> > >
> > > I can propose three courses of action, in the order of my preference:
> > >
> > > 1. Sysv core adopts po4a and includes the translation framework as
> > >    well as the translations (see below for the overview). I will
> > >    provide you help on this (in January), probably Mario (the upstream
> > >    maintainer of manpage-l10n) might give you some help as well. Then
> > >    the man pages will keep up to date (see rationale in 2) and more
> > >    translators / languages can be easily integrated, if translators
> > >    pop up.
> >
> > Indeed, to me, this seems the cleanest solution in the long run. Thanks for the
> > offer of help.
>
> Yes, this offer stands. I'll can support you in January 2022 on doing
> this, meanwhile Mario, who is helped other projects adopting po4a,
> might give some advice as well.
>
OK, it is in my favor to both keep existing man page translations
alive (acknowledging the work of the previous translators) and
integrate Po4a-based translations into upstream projects, instead of
maintaining them in an external translation project. Give me some days
to prepare a Po4a framework and migrate the existing .po files. I've
already checked out the Git repo at savannah.nongnu.org. I would
create the changes in one single (and quite big) Git diff, is this OK
for you? Or is there even a mirror at Github or Gitlab or wherever
else where I could create a pull request?

Best Regards,
Mario