public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebaaa1754 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/31029] New: A few paragraphs explaining 'catopen' actually belong in 'catgets'
Date: Fri, 03 Nov 2023 15:32:10 +0000 [thread overview]
Message-ID: <bug-31029-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31029
Bug ID: 31029
Summary: A few paragraphs explaining 'catopen' actually belong
in 'catgets'
Product: glibc
Version: 2.38
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: manual
Assignee: unassigned at sourceware dot org
Reporter: sebaaa1754 at gmail dot com
CC: mtk.manpages at gmail dot com
Target Milestone: ---
The following paragraphs in the body of the 'catopen' function seem to be
erroneously placed, as they actually refer to the following function,
'catgets'. Everything else in this document seems to be correct.
manual/message.texi lines 229 to 260:
> The return value of the function is in any case a valid string. Either
> it is a translation from a message catalog or it is the same as the
> @var{string} parameter. So a piece of code to decide whether a
> translation actually happened must look like this:
>
> @smallexample
> @{
> char *trans = catgets (desc, set, msg, input_string);
> if (trans == input_string)
> @{
> /* Something went wrong. */
> @}
> @}
> @end smallexample
>
> @noindent
> When an error occurs the global variable @code{errno} is set to
>
> @table @var
> @item EBADF
> The catalog does not exist.
> @item ENOMSG
> The set/message tuple does not name an existing element in the
> message catalog.
> @end table
>
> While it sometimes can be useful to test for errors programs normally
> will avoid any test. If the translation is not available it is no big
> problem if the original, untranslated message is printed. Either the
> user understands this as well or s/he will look for the reason why the
> messages are not translated.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2023-11-03 15:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-31029-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 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).