From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: Linux Man-Pages <linux-man@vger.kernel.org>
Cc: Bruno Haible <bruno@clisp.org>,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: Re: POSIX conformance document
Date: Sat, 1 Jun 2024 09:15:23 -0600 [thread overview]
Message-ID: <bf16e9f9-80ec-4f66-b11f-284ddac1952e@SystematicSW.ab.ca> (raw)
In-Reply-To: <12722244.etNSJPHsjv@nimes>
On 2024-05-31 15:21, Bruno Haible wrote:
> POSIX [1] specifies that conforming implementations shall come with a
> "conformance document" that describes "implementation-defined" characteristics
> [2]. Two such example conformance documents are [3], [4].
>
> For Linux (or any Linux distro), I cannot find such a document on the web.
>
> Is such a document only considered useful for business/marketing purposes?
> Isn't there some value in it also for regular users and developers?
>
> Will there be some effort to create such a document for the upcoming
> POSIX.1-2024 standard, for Linux and the GNU libraries and tools?
>
> I'm asking because I've collected the answers for all *gettext() functions
> and the msgfmt and xgettext programs (that will be part of this new POSIX),
> but I don't know where to best document them. Likely in the manual of
> GNU libc and GNU gettext, right?
>
> Bruno
>
> [1] https://en.wikipedia.org/wiki/POSIX
> [2] https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/basedefs/V1_chap02.html
> [3] https://empyreal96.github.io/nt-info-depot/SourceLevel/base/subsys/posix/pcd.doc
> [4] https://www.qnx.com/developers/docs/6.5.0SP1.update/com.qnx.doc.neutrino_prog/posix_conformance.html
Hi Bruno,
You might want to sign up to the Open Group to access the Austin Group (POSIX)
documents (including latest drafts to update your info and documents), become a
member, email your questions, and participate as a documentor and implementor on
their list:
https://www.opengroup.org/austin/
You can also view their discussions and document defect issues on web archive:
https://www.mail-archive.com/austin-group-l@opengroup.org/
and get updates from an Atom/RSS Feed (e.g. Firefox/Chrome/... bookmark feeds):
https://www.mail-archive.com/austin-group-l@opengroup.org/maillist.xml
without subscribing to their ML.
[Alex has contacted them about POSIX man pages, and hopefully may get info about
updating POSIX man pages to 2024: latest draft standard has been approved by
IEEE and Open Group Board, internal publication of the standard with final front
matter is due 2024-06-14, ISO/IEC ballot closes 2024-06-28.]
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-06-01 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 21:21 POSIX conformance document Bruno Haible
2024-05-31 23:27 ` Alejandro Colomar
2024-06-02 13:31 ` Bruno Haible
2024-06-01 15:15 ` Brian Inglis [this message]
2024-06-01 17:29 ` Alejandro Colomar
2024-06-02 13:37 ` Bruno Haible
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=bf16e9f9-80ec-4f66-b11f-284ddac1952e@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=alx.manpages@gmail.com \
--cc=bruno@clisp.org \
--cc=linux-man@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.