public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Tristan Gingold <tgingold@free.fr>,
	Nelson Chu <nelson.chu@sifive.com>
Cc: binutils@sourceware.org
Subject: [PATCH 1/2] Mach-O: i18n enablement on some error messages
Date: Fri, 10 Jun 2022 19:00:18 +0900	[thread overview]
Message-ID: <26f2b8bffaa3446c425a9a7f1457c8d9ad58145f.1654855051.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1654855051.git.research_trasio@irq.a4lg.com>

This commit now wraps two string literals with _() for i18n support
enablement.  They are used in the collect_16char_name function to form
localized error messages that contain "%s name".

gas/ChangeLog:

	* config/obj-macho.c (obj_mach_o_get_section_names): Wrap two
	string literals within with gettext macro.
---
 gas/config/obj-macho.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gas/config/obj-macho.c b/gas/config/obj-macho.c
index f055aeadafb..119f2fd1356 100644
--- a/gas/config/obj-macho.c
+++ b/gas/config/obj-macho.c
@@ -141,7 +141,7 @@ obj_mach_o_get_section_names (char *seg, char *sec,
   /* Zero-length segment and section names are allowed.  */
   /* Parse segment name.  */
   memset (seg, 0, segl);
-  if (collect_16char_name (seg, "segment", 1))
+  if (collect_16char_name (seg, _("segment"), 1))
     {
       ignore_rest_of_line ();
       return 0;
@@ -150,7 +150,7 @@ obj_mach_o_get_section_names (char *seg, char *sec,
 
   /* Parse section name, which can be empty.  */
   memset (sec, 0, secl);
-  collect_16char_name (sec, "section", 0);
+  collect_16char_name (sec, _("section"), 0);
   return 1;
 }
 
-- 
2.34.1


  reply	other threads:[~2022-06-10 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 10:00 [PATCH 0/2] gas: Minor strings fix on June 2022 (Mach-O and RISC-V) Tsukasa OI
2022-06-10 10:00 ` Tsukasa OI [this message]
2022-06-10 10:00 ` [PATCH 2/2] RISC-V: Fix inconsistent error message (range) Tsukasa OI
2022-06-22 10:36   ` Nelson Chu
2022-06-12  4:12 ` [PATCH 0/2] gas: Minor strings fix on June 2022 (Mach-O and RISC-V) Tristan Gingold
2022-06-12  9:28   ` Tsukasa OI
2022-07-13  3:23   ` Tsukasa OI
2022-08-07  7:40 ` [RESEND PATCH 0/1] gas: Minor strings fix on June 2022 (Mach-O part) Tsukasa OI
2022-08-07  7:40   ` [RESEND PATCH 1/1] Mach-O: i18n enablement on some error messages Tsukasa OI
2022-08-08 11:42     ` Nick Clifton

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=26f2b8bffaa3446c425a9a7f1457c8d9ad58145f.1654855051.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=nelson.chu@sifive.com \
    --cc=tgingold@free.fr \
    /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).