public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Anadon <joshua.r.marshall.1991@gmail.com>
Cc: bug-gettext@gnu.org, libc-help@sourceware.org
Subject: Re: How to get argp to print standard fields in the target language?
Date: Sun, 21 May 2023 15:01:23 +0200	[thread overview]
Message-ID: <4435690.Wku2Vz74k6@nimes> (raw)
In-Reply-To: <CAFkJGReQGRL_hvfio+wtAgbeJSVPcWUZtKfjKKrPUqS3GP9Ejw@mail.gmail.com>

Anadon wrote:
> Since all usage of argp has the same translation strings, they could
> be a part of files distributed as a package with the OS.

No, it would not help if, say, glibc would include these strings in the
libc.pot file. That's because there are other platforms (*BSD, mingw, etc.)
that don't have this .pot file and its translations.

Therefore these strings from argp-help.c need to be either in your
package's .pot file, or in a gnulib.pot file. There was an experimental
gnulib.pot file many years ago, but it was too cumbersome to keep up-to-date.
Therefore the only good option is to have these strings in your
package's .pot file.

> From my current
> understanding, this does not work with gettext as implemented because
> simultaneous domains as described in
> https://www.gnu.org/software/gettext/manual/gettext.html#Triggering do
> not seem to be supported.

Simultaneous gettext domains are supported. GNU clisp uses this feature,
as it has 2 gettext domains.

Bruno




      reply	other threads:[~2023-05-21 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFkJGRetOSo6VqLRoMOUKKASk5WxQwQeTqtNp16R5sBrmqCYFA@mail.gmail.com>
     [not found] ` <1710975.uacIGzncQW@nimes>
2023-05-21  4:25   ` Anadon
2023-05-21 13:01     ` Bruno Haible [this message]

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=4435690.Wku2Vz74k6@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gettext@gnu.org \
    --cc=joshua.r.marshall.1991@gmail.com \
    --cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).