From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tristan Gingold <tgingold@free.fr>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 0/2] gas: Minor strings fix on June 2022 (Mach-O and RISC-V)
Date: Sun, 12 Jun 2022 18:28:36 +0900 [thread overview]
Message-ID: <26b9f9e6-2d0c-e8e2-01ae-6de3ae6eb5ed@irq.a4lg.com> (raw)
In-Reply-To: <EB479A95-4E69-42C4-8A27-9F5DCDE5C003@free.fr>
On 2022/06/12 13:12, Tristan Gingold wrote:
> For me, the mach-o part is OK.
> I am not sure I would translate section or segment as they are technical words, but you are the native speaker!
At least, I think most of Binutils users understand what English words
"section" and "segment" mean (even if they are not non-English
speakers). The reason I sent this patch is words "section" and
"segment" are translated in other messages. In that sense, it's also
about consistency.
next prev parent reply other threads:[~2022-06-12 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 10:00 Tsukasa OI
2022-06-10 10:00 ` [PATCH 1/2] Mach-O: i18n enablement on some error messages Tsukasa OI
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 [this message]
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=26b9f9e6-2d0c-e8e2-01ae-6de3ae6eb5ed@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--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).