[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] Coordination on standardizing gettext() in future POSI

From: Joerg Schilling
Subject: Re: [bug-gettext] Coordination on standardizing gettext() in future POSIX
Date: Fri, 10 Aug 2018 13:35:15 +0200
User-agent: Heirloom mailx 12.5 7/5/10

Hi all,

I am happy that we have an agreement to standardize gettext() in POSIX.

We may need to agree on a way to do the discussion. Using the Austin Mantis may 
be an option but I am not sure whether this is the best idea.

Eric Blake <address@hidden> wrote:

> Hello GNU gettext folks,
> Jörg Schilling is interested in standardizing gettext() and friends in a 
> future version of POSIX (as a replacement to the hard-to-use catgets() 
> that is currently standardized).  See 
> http://austingroupbugs.net/view.php?id=1122
> While there are probably things in GNU gettext that won't be 
> standardized (for example, xgettext(1) has some long-only options, but 
> POSIX will only standardize short options), it is worth coordinating the 
> bare minimum set of features that are portable across GNU and other 

Related to xgettext(1) I see a chance to standardize something better than 
currently exist, since I have problems with both xgettext(1) and gxgettext(1).

Regarding a bare minimum, it seems that all options supported by xgettext(1)
are also supported by gxgettext(1). So maybe we start with this and discuss 
whether there should be more in the standard.

> implementations of gettext, as well as any wording changes that need to 
> be added (such as documenting thread-safety, locale interactions, 
> whether bindtextdomain() can only safely be used once prior to creating 
> threads, and so on) in order to actually be included in the standards.
> Thus, this email is more of an introduction to make sure everyone 
> interested in the project is aware of where to write/review any wording 
> proposals for accomplishing the addition into POSIX.

>From looking at the current manuals available on Linux systems, I propose to 
start with the manual pages from OpenSolaris since these manual pages seem to 
be closer from being complete enough for the POSIX standard.

Let me give the list of man pages I have in mind. If you find something that is 
missing, please report.




Since these man pages are not yet from a Solaris version that has been verified 
against the current Issue 7 standard, we need to add text to explain the 
behavior for thread specific locales and we need to add text related to thread 

For the same reason, I believe that we need to add various *_l() function 
interfaces that allow to have versions that may be used with a locale_t 
argument from newlocale() or duplocale().

My proposal is to first agree on a set of man pages for UNIX use and later make 
changes from "... is ..." to "... shall be ..." as in the standard.


 EMail:address@hidden                    (home) Jörg Schilling D-13353 Berlin
    address@hidden (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'

reply via email to

[Prev in Thread] Current Thread [Next in Thread]