From: Lauri Nurmi <lanurmi@iki.fi>
To: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 2/5] hwclock: clean up message periods/full stops
Date: Sat, 25 Oct 2014 00:57:10 +0300 [thread overview]
Message-ID: <544ACB36.6050906@iki.fi> (raw)
In-Reply-To: <544A4817.3070406@gmx.com>
24.10.2014, 15:37, JWP kirjoitti:
> On 10/24/2014 07:33 AM, Benno Schulenberg wrote:
>> On Fri, Oct 24, 2014, at 04:49, JWP wrote:
>>> This is unsightly and difficult to read.
>> Ehm... I would think the lack of periods would make things
>> more difficult to read.
> Agreed. However, having 2/3 of the messages without and 1/3 with
> makes no sense at all.
Of course it makes sense e.g. if 1/3 of the messages are sentences and
2/3 are not.
>>> - ("The value of the --date option is not a valid date.\n"
>>> - "In particular, it contains quotation marks."));
>>> + ("The value of the --date option is not a valid date\n"
>>> + "In particular, it contains quotation marks"));
>> This is ugly. Two lines of text and it's unclear that the first
>> sentence ends at the end of the line. If you absolutely want
>> to get rid of the period, put a semicolon after "valid date" and
>> lowercase "in particular".
> That would not make sense to me. Either we use punctuation or we don't.
"We use punctuation where appropriate" is not an option? If you feel
that way, maybe it would be better not to touch the messages.
> I am no grammar expert, but if two sentences was originally correct then
> it should still be correct.
A sentence ends in a period. You removed the period. Now they are
sentences missing a period.
>
>> All just cosmetic changes, invalidating all the translations.
>> Not nice.
> My sincere oligopolies to translators, but hwclock is slated for refactoring
> and I expect many message changes will be included.
Then it is completely unnecessary and silly to introduce this kind of
nonsensical changes at this point. It leads to translators needing to
update the translations not only once, but twice.
BR,
(Mr) Lauri Nurmi
a translator
prev parent reply other threads:[~2014-10-24 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 2:49 [PATCH 2/5] hwclock: clean up message periods/full stops JWP
2014-10-24 11:33 ` Benno Schulenberg
2014-10-24 12:37 ` JWP
2014-10-24 12:59 ` Karel Zak
2014-10-24 16:07 ` JWP
2014-10-24 20:58 ` Benno Schulenberg
2014-10-27 10:59 ` Karel Zak
2014-10-27 10:55 ` Karel Zak
2014-10-24 21:57 ` Lauri Nurmi [this message]
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=544ACB36.6050906@iki.fi \
--to=lanurmi@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).