From: Benno Schulenberg <bensberg@justemail.net>
To: "Util-Linux" <util-linux@vger.kernel.org>
Subject: [patch] hwclock: gettextize interface phrases
Date: Mon, 27 Jan 2014 20:08:31 +0100 [thread overview]
Message-ID: <1390849711.26603.75936773.1466C128@webmail.messagingengine.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi,
When using the --debug option with hwclock, the phrase that denotes
the interface being used isn't getting localized, because it isn't
gettextized. Attached patch fixes this in a translator-friendly way:
making the announcements into whole sentences.
Regards,
Benno
--
http://www.fastmail.fm - The professional email service
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-hwclock-internationalizing-the-message-of-the-used-i.patch --]
[-- Type: text/x-patch; name="0001-hwclock-internationalizing-the-message-of-the-used-i.patch", Size: 2220 bytes --]
From cff0a5a06e3a4e4bcdb6e32a1534ab0bb93ca04e Mon Sep 17 00:00:00 2001
From: Benno Schulenberg <bensberg@justemail.net>
Date: Sun, 26 Jan 2014 22:32:15 +0100
Subject: [PATCH] hwclock: internationalizing the message of the used interface
In addition, do it in a single sentence instead of in two fragments.
Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
---
sys-utils/hwclock-cmos.c | 2 +-
sys-utils/hwclock-kd.c | 2 +-
sys-utils/hwclock-rtc.c | 2 +-
sys-utils/hwclock.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/sys-utils/hwclock-cmos.c b/sys-utils/hwclock-cmos.c
index 58b3ea5..7ffbf95 100644
--- a/sys-utils/hwclock-cmos.c
+++ b/sys-utils/hwclock-cmos.c
@@ -649,7 +649,7 @@ static int get_permissions_cmos(void)
}
static struct clock_ops cmos = {
- "direct I/O instructions to ISA clock",
+ N_("Using direct I/O instructions to ISA clock."),
get_permissions_cmos,
read_hardware_clock_cmos,
set_hardware_clock_cmos,
diff --git a/sys-utils/hwclock-kd.c b/sys-utils/hwclock-kd.c
index 8e67009..3dac707 100644
--- a/sys-utils/hwclock-kd.c
+++ b/sys-utils/hwclock-kd.c
@@ -143,7 +143,7 @@ static int get_permissions_kd(void)
}
static struct clock_ops kd = {
- "KDGHWCLK interface to m68k clock",
+ N_("Using the KDGHWCLK interface to m68k clock."),
get_permissions_kd,
read_hardware_clock_kd,
set_hardware_clock_kd,
diff --git a/sys-utils/hwclock-rtc.c b/sys-utils/hwclock-rtc.c
index a22ce4c..78f42aa 100644
--- a/sys-utils/hwclock-rtc.c
+++ b/sys-utils/hwclock-rtc.c
@@ -397,7 +397,7 @@ static int get_permissions_rtc(void)
}
static struct clock_ops rtc = {
- "/dev interface to clock",
+ N_("Using the /dev interface to the clock."),
get_permissions_rtc,
read_hardware_clock_rtc,
set_hardware_clock_rtc,
diff --git a/sys-utils/hwclock.c b/sys-utils/hwclock.c
index 5dd7919..30660d4 100644
--- a/sys-utils/hwclock.c
+++ b/sys-utils/hwclock.c
@@ -1140,7 +1140,7 @@ static void determine_clock_access_method(const bool user_requests_ISA)
if (debug) {
if (ur)
- printf(_("Using %s.\n"), ur->interface_name);
+ puts(_(ur->interface_name));
else
printf(_("No usable clock interface found.\n"));
}
--
1.7.0.4
next reply other threads:[~2014-01-27 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 19:08 Benno Schulenberg [this message]
2014-02-10 17:42 ` [patch] hwclock: gettextize interface phrases Karel Zak
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=1390849711.26603.75936773.1466C128@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--cc=util-linux@vger.kernel.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