git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Kevin Daudt <me@ikke.info>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] commit-template: change a message to be more intuitive
Date: Wed, 13 Sep 2017 17:59:03 +0530	[thread overview]
Message-ID: <1d400615-be2c-7ed7-9687-d78ab163eaea@gmail.com> (raw)
In-Reply-To: <20170913102915.GA21499@alpha.vpn.ikke.info>

On Wednesday 13 September 2017 03:59 PM, Kevin Daudt wrote:
> Touching something can also mean to disturb or change something, which
> is the meaning being used here, so it is not an incorrect use of the
> word.

I do get your point but I should have been clearer in my commit message 
about the
fact that it's a word that could be misinterpreted.

>> So, make the sentence more intuitive.
> I can understand however that it might be not so clear for people with
> less fluency in English.

Not just that, it could also make the translations a little unclear. 
i.e., the when the words that convey
clear meaning in a particular context in english speaker get translated 
"as such" to another language,
they might turn out to become unclear or might even convey a totally 
different meaning. I'm not sure
if is currently happening as I am not familiar with any languages for 
which translations are currently
available but I'm pretty sure that the sentence "Do not touch the line 
above." would not give a clear
meaning when it gets translated "as such" to my native language (Tamil). 
Of course, it's only a problem
if the sentences get translated "as such" but I'm not sure if 
translators (human/non-human) try do
meaningful translations or try to preserve a one-to-one relationship 
with the words in the source
language, either.

---
Kaartic

  parent reply	other threads:[~2017-09-13 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 10:55 [PATCH] commit-template: change a message to be more intuitive Kaartic Sivaraam
2017-09-13 10:29 ` Kevin Daudt
2017-09-13 11:20   ` Jeff King
2017-09-13 12:31     ` Kaartic Sivaraam
2017-09-13 13:05       ` [PATCH v2] " Kaartic Sivaraam
2017-09-13 12:29   ` Kaartic Sivaraam [this message]
     [not found] <<e656d1b4-c95e-e51d-5f48-bb3450580fa4@gmail.com>
2017-09-13 13:05 ` Kaartic Sivaraam
2017-09-14  7:36   ` Michael J Gruber
2017-09-14 14:17     ` Kaartic Sivaraam
2017-09-14 14:41       ` Jeff King
2017-09-15  2:18         ` Junio C Hamano
2017-09-15  4:50           ` [PATCH v3] " Kaartic Sivaraam
2017-09-15 10:00             ` Michael J Gruber
2017-09-15 12:39               ` Kaartic Sivaraam
2017-09-15  1:58     ` [PATCH v2] " Kaartic Sivaraam

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=1d400615-be2c-7ed7-9687-d78ab163eaea@gmail.com \
    --to=kaarticsivaraam91196@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ikke.info \
    /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).