From: Karel Zak <kzak@redhat.com>
To: "Mario Blättermann" <mario.blaettermann@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: util-linux v2.39 with translated man pages by default?
Date: Wed, 26 Apr 2023 12:28:06 +0200 [thread overview]
Message-ID: <20230426102806.7w33zaheh3feuohg@ws.net.home> (raw)
In-Reply-To: <CAHi0vA9nvmh7qiWX2oWbOcanCesk2M9dS0Goef6772emz=uy4g@mail.gmail.com>
On Wed, Apr 19, 2023 at 08:24:47PM +0200, Mario Blättermann wrote:
> Hello,
>
> when I run ./configure (without any option) on the current Git content, I get:
>
> Manual pages: yes
> Manual pages translated: no
>
> This means, creating and installing the translated man pages is still
> not enabled by default. What may we expect for v2.39? If this remains
Good point. I have enabled it:
https://github.com/util-linux/util-linux/commit/9acfc349e0ea68a92baf818cc659121f40ab9c04
but as in other cases, the default is "check", and the result depends on
if you have "po4a" installed, and if not installed, you will see a
warning
configure: WARNING: po4a not found; not building translated man pages
but ./configure will success.
> disabled, no downstream packager will notice it, and the effort of the
> translators (6 languages, more than 500 translated *.adoc files) was
> for the trashscan.
I need to think about how to push it to Fedora/RHEL; I'll probably
create a sub-package with the translations, one for all or per
language. Is there any good practice for man pages?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2023-04-26 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 18:24 util-linux v2.39 with translated man pages by default? Mario Blättermann
2023-04-26 10:28 ` Karel Zak [this message]
2023-04-26 19:10 ` Mario Blättermann
2023-05-18 9:55 ` Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230426102806.7w33zaheh3feuohg@ws.net.home \
--to=kzak@redhat.com \
--cc=mario.blaettermann@gmail.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).