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/31057] 'How to use "gettext" in GUI programs' could mention pgettext()
Date: Mon, 13 Nov 2023 00:55:04 +0000	[thread overview]
Message-ID: <bug-31057-131-76qS1jYKTt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31057-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31057

--- Comment #2 from Sebastian Carlos <sebaaa1754 at gmail dot com> ---
(In reply to Andreas Schwab from comment #1)
> pgettext is not part of glibc.

Point taken.

Nevertheless, this section of the manual makes several mentions of GNU gettext.
An example would be "The ‘gettext’ approach has some advantages but also some
disadvantages.  Please see the GNU ‘gettext’ manual for a detailed discussion
of the pros and cons."

In light of that, I suggest a small mention of the GNU gettext function, given
the length to which this functionality is described in the glibc manual.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-11-13  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 13:30 [Bug manual/31057] New: " sebaaa1754 at gmail dot com
2023-11-12 16:29 ` [Bug manual/31057] " schwab@linux-m68k.org
2023-11-13  0:55 ` sebaaa1754 at gmail dot com [this message]

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-31057-131-76qS1jYKTt@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).