The following issue has been SUBMITTED.
==
https://austingroupbugs.net/view.php?id=1554
==
Reported By:andras_farkas
Assigned To:
The following issue has been SUBMITTED.
==
https://austingroupbugs.net/view.php?id=1553
==
Reported By:andras_farkas
Assigned To:
Historically, gettext domains are process wide, making use in multi-threaded
apps problematic to begin with. The *_l versions only partially address this.
The uselocale() interface is included there for the cases where a locale is
used by both a uselocale() and one or more of the *_l versions,
[First sent on 2021-05-03. Resending because it has not been handled.]
https://posix.rhansen.org/p/gettext_draft
says (line 358):
"The returned string may be invalidated by a subsequent call to
bind_textdomain_codeset(), bindtextdomain(), setlocale(),
textdomain(), or uselocale()."
[First sent on 2021-05-03. Resending because it has not been fully handled.]
https://posix.rhansen.org/p/gettext_draft
says (line 343..345)
"For each locale name in LANGUAGE, or if LANGUAGE is not set or is
empty, or no suitable messages object is found in processing LANGUAGE,
the
Hi,
Eric Blake wrote:
> The Austin Group (the standards body in charge of the POSIX document)
> is trying to standardize the gettext(3) family of functions, as well
> as command line tools such as gettext(1) and xgettext(1). You can
> track the efforts here, and if you have comments, I'm happy
Op 14-08-18 om 17:21 schreef Stephane Chazelas:
Hi, the spec for the "allexport" (set -a) shell option says:
POSIX2018> When this option is on, the export attribute shall
POSIX2018> be set for each variable to which an assignment is
POSIX2018> performed; see XBD Variable Assignment. If the
