public inbox for binutils-cvs@sourceware.org help / color / mirror / Atom feed
From: Nick Clifton <nickc@sourceware.org> To: bfd-cvs@sourceware.org Subject: [binutils-gdb] Mach-O: i18n enablement on some error messages. Date: Mon, 8 Aug 2022 11:42:11 +0000 (GMT) [thread overview] Message-ID: <20220808114211.5DB9A385829E@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d7872ebb652942b93c9509be7f9f0a06aa47d970 commit d7872ebb652942b93c9509be7f9f0a06aa47d970 Author: Tsukasa OI <research_trasio@irq.a4lg.com> Date: Mon Aug 8 12:41:30 2022 +0100 Mach-O: i18n enablement on some error messages. * config/obj-macho.c (obj_mach_o_get_section_names): Wrap two string literals within with gettext macro. Diff: --- gas/ChangeLog | 5 +++++ gas/config/obj-macho.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/gas/ChangeLog b/gas/ChangeLog index f6b357709b2..23c09c40950 100644 --- a/gas/ChangeLog +++ b/gas/ChangeLog @@ -1,3 +1,8 @@ +2022-08-08 Tsukasa OI <research_trasio@irq.a4lg.com> + + * config/obj-macho.c (obj_mach_o_get_section_names): Wrap two + string literals within with gettext macro. + 2022-08-05 Nick Clifton <nickc@redhat.com> PR 29447 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; }
reply other threads:[~2022-08-08 11:42 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=20220808114211.5DB9A385829E@sourceware.org \ --to=nickc@sourceware.org \ --cc=bfd-cvs@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: linkBe 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).