From: Roland McGrath <mcgrathr@google.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: [COMMITTED PATCH] avoid non-ASCII/non-UTF8 character in string literal in winduni.c
Date: Fri, 11 Oct 2013 17:25:00 -0000 [thread overview]
Message-ID: <CAB=4xhoOREHnwVAeg5EFtm-+6etO7PZ8GRsueQfZDx5B9b09hQ@mail.gmail.com> (raw)
Committed as obvious enough, to trunk and 2.24 branch.
I'm not entirely sure the patch will come through the email without
mangling the character. It's replacing a literal \345 byte in the source
with the octal literal syntax \345. It's just good practice to avoid the
source files having non-UTF8 bytes in them.
Thanks,
Roland
binutils/
* winduni.c (languages): Use \345 (octal syntax) rather than
literal non-ASCII/non-UTF8 character in string literal.
--- a/binutils/winduni.c
+++ b/binutils/winduni.c
@@ -101,7 +101,7 @@ static const wind_language_t languages[] =
{ 0x040D, 862, 1255, "Hebrew", "Israel" }, { 0x040E, 852,
1250, "Hungarian", "Hungary" },
{ 0x040F, 850, 1252, "Icelandic", "Iceland" }, { 0x0410, 850,
1252, "Italian", "Italy" },
{ 0x0411, 932, 932, "Japanese", "Japan" }, { 0x0412, 949,
949, "Korean", "Korea (south)" },
- { 0x0413, 850, 1252, "Dutch", "Netherlands" }, { 0x0414, 850,
1252, "Norwegian (Bokm�l)", "Norway" },
+ { 0x0413, 850, 1252, "Dutch", "Netherlands" }, { 0x0414, 850,
1252, "Norwegian (Bokm\345l)", "Norway" },
{ 0x0415, 852, 1250, "Polish", "Poland" }, { 0x0416, 850,
1252, "Portuguese", "Brazil" },
{ 0x0418, 852, 1250, "Romanian", "Romania" }, { 0x0419, 866,
1251, "Russian", "Russia" },
{ 0x041A, 852, 1250, "Croatian", "Croatia" }, { 0x041B, 852,
1250, "Slovak", "Slovakia" },
reply other threads:[~2013-10-11 17:25 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='CAB=4xhoOREHnwVAeg5EFtm-+6etO7PZ8GRsueQfZDx5B9b09hQ@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=binutils@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).