public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: "Jan Beulich" <jbeulich@suse.com>, "Arsen Arsenović" <arsen@aarsen.me>
Cc: Iain Sandoe <iain@sandoe.co.uk>,
	gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Fri, 29 Sep 2023 17:58:15 +0200	[thread overview]
Message-ID: <2191135.CQOukoFCf9@nimes> (raw)
In-Reply-To: <864jjhrm73.fsf@aarsen.me>

Arsen Arsenović wrote:
> Building without gettext in-tree or on the system
> should result in a working build with no localization, with gettext
> in-tree and on the system it should result in the usage of the system
> gettext, with gettext on the tree but _not_ on the system, it should
> result in a new (static) copy being built and linked into the tools,
> with working localization, and with no gettext in tree but in system
> (either in libc or in libintl) should result in a localized build using
> the system gettext facilities.
> 
> The behavior for the in-tree but also on the system case (e.g. building
> with gettext in-tree on a GNU system) can be overridden with
> --with-included-gettext (which is a configure flag for gettext-runtime,
> and was a configure flag for intl/ before that).

This information is more intelligible when presented as a table. I think
the table is like this, right?

                 Situation                                 ||   Effect
                                                           ||
gettext  |  libintl  | libc has   |         Option         ||   Working
sources  | installed | *gettext() |--with-included-gettext || Localization
in-tree  | on system | functions  |                        ||
---------+-----------+------------+------------------------++----------------------
   -     |     -     |     -      |       (ignored)        ||     No
   -     |     -     |     Y      |       (ignored)        ||  Yes (libc)
   -     |     Y     |     -      |       (ignored)        ||  Yes (libintl)
   -     |     Y     |     Y      |       (ignored)        ||  Yes (libintl)
   Y     |     -     |     -      |           -            ||  Yes (static libintl)
   Y     |     -     |     -      |           Y            ||  Yes (static libintl)
   Y     |     -     |     Y      |           -            ||  Yes (libc)
   Y     |     -     |     Y      |           Y            ||  Yes (static libintl)
   Y     |     Y     |     -      |           -            ||  Yes (libintl)
   Y     |     Y     |     -      |           Y            ||  Yes (static libintl)
   Y     |     Y     |     Y      |           -            ||  Yes (libintl)
   Y     |     Y     |     Y      |           Y            ||  Yes (static libintl)
---------+-----------+------------+------------------------++----------------------

In all of these cases, the localization can be turned off through the
configure option --disable-nls or by the user, at runtime, by choosing the
"C" locale.

I would find it useful to add this table to the documentation or
at least as some internal comments.

Bruno




  parent reply	other threads:[~2023-09-29 15:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26  0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26  0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26  2:12   ` Kevin Buettner
2023-09-26  7:03   ` Jan Beulich
2023-09-26  7:54     ` Iain Sandoe
2023-09-26 14:44     ` Arsen Arsenović
2023-09-27  7:11       ` Jan Beulich
2023-09-27 13:06         ` Arsen Arsenović
2023-09-27 15:19         ` Nick Clifton
2023-09-27 17:43           ` Arsen Arsenović
2023-09-28  9:43             ` Nick Clifton
2023-09-29 15:58       ` Bruno Haible [this message]
2023-09-29 16:27         ` Arsen Arsenović
2023-11-20 16:42   ` Kévin Le Gouguec
2023-11-20 20:30     ` Arsen Arsenović
2023-11-20 21:28       ` Bruno Haible
2023-09-26  0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21   ` Nick Clifton

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=2191135.CQOukoFCf9@nimes \
    --to=bruno@clisp.org \
    --cc=arsen@aarsen.me \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=iain@sandoe.co.uk \
    --cc=jbeulich@suse.com \
    /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).