From: Bruno Haible <bruno@clisp.org>
To: linux-man@vger.kernel.org
Subject: POSIX conformance document
Date: Fri, 31 May 2024 23:21:28 +0200 [thread overview]
Message-ID: <12722244.etNSJPHsjv@nimes> (raw)
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
next reply other threads:[~2024-05-31 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 21:21 Bruno Haible [this message]
2024-05-31 23:27 ` POSIX conformance document Alejandro Colomar
2024-06-02 13:31 ` Bruno Haible
2024-06-01 15:15 ` Brian Inglis
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=12722244.etNSJPHsjv@nimes \
--to=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.