All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] po/hi.po: Add Hindi Translation
Date: Mon, 6 Sep 2010 09:59:45 +0530	[thread overview]
Message-ID: <20100906042942.GA32387@kytes> (raw)
In-Reply-To: <AANLkTinGvySGu=rQxccCJ6v3ct6s6kf3butEcZvSMPpB@mail.gmail.com>

Hi Sitaram,

Sitaram Chamarty writes:
> looks OK to me.  Some of those words will never be encountered in
> colloquial Hindi (I had to think for a bit on निर्देशिका and
> प्रतीकात्मक लिंक!) , but that's the way it always is.  We end up just
> using the English word within Hindi/Telugu/whatever :-)

Thanks for the feedback. Yes, that's true- even among my friends, only
a few expert Hindi speakers were able to follow hindi.po
completely. However, I figured that only those people who are more
comfortable in Hindi than English will actually use hindi.po, so we
might as well do it right :)

I also discovered another thing- even expert Hindi speakers don't seem
to understand Hindi grammar very well :p After a few hours of
studying, I was able to correct a few more mistakes that others
weren't able to spot. Here's the diff.

Junio: Please squash this into the first revision of the patch.

diff --git a/po/hi.po b/po/hi.po
index d31e60b..a5464b3 100644
--- a/po/hi.po
+++ b/po/hi.po
@@ -12,11 +12,11 @@ msgstr ""
 
 #, c-format
 msgid "Could not make %s writable by group"
-msgstr "%s को समूह द्वारा लिखने योग्य नहीं बना सके"
+msgstr "%s को समूह द्वारा लिखने की इजाज़त नही दे सके"
 
 #, c-format
 msgid "insanely long template name %s"
-msgstr "टेम्पलेट का नाम बहुत लंबा है: %s"
+msgstr "टेम्पलेट %s का नाम बहुत लंबा है"
 
 #, c-format
 msgid "cannot stat '%s'"
@@ -28,40 +28,40 @@ msgstr "टेम्पलेट '%s' को [stat] नहीं कर सक
 
 #, c-format
 msgid "cannot opendir '%s'"
-msgstr "निर्देशिका नहीं खोल सके: '%s'"
+msgstr "निर्देशिका '%s' नहीं खोल सके"
 
 #, c-format
 msgid "cannot readlink '%s'"
-msgstr "लिंक नहीं पढ़ सके: '%s'"
+msgstr "लिंक '%s' नहीं पढ़ सके"
 
 #, c-format
 msgid "insanely long symlink %s"
-msgstr "प्रतीकात्मक लिंक बहुत लंबा है: %s"
+msgstr "प्रतीकात्मक लिंक %s बहुत लंबा है"
 
 #, c-format
 msgid "cannot symlink '%s' '%s'"
-msgstr "'%s' से '%s' प्रतीकात्मक लिंक नहीं बना सके"
+msgstr "'%s' का प्रतीकात्मक लिंक '%s' में नहीं बना सके"
 
 #, c-format
 msgid "cannot copy '%s' to '%s'"
-msgstr "'%s' का नकल '%s' नहीं बना सके"
+msgstr "'%s' का अनुकृति '%s' में नहीं कर सके"
 
 #, c-format
 msgid "ignoring template %s"
-msgstr "टेम्पलेट को उपेक्षा कर रहे है: %s"
+msgstr "टेम्पलेट %s का उपेक्षा कर रहे है"
 
 #, c-format
 msgid "insanely long template path %s"
-msgstr "टेम्पलेट का आकार बहुत लंबा है: %s"
+msgstr "टेम्पलेट %s का आकार बहुत लंबा है"
 
 #, c-format
 msgid "templates not found %s"
-msgstr "टेम्पलेट नहीं मिला: %s"
+msgstr "टेम्पलेट %s नहीं मिला"
 
 #, c-format
 msgid "not copying templates of a wrong format version %d from '%s'"
-msgstr "'%s' से गलत स्वरूप संस्करण %d का टेम्पलेट नकल नहीं कर रहे है"
+msgstr "'%s' से गलत स्वरूप संस्करण %d के टेम्पलेट्स के नकल नहीं कर रहे है"
 
 #, c-format
 msgid "insane git directory %s"
-msgstr "खराब गिट निर्देशिका %s"
+msgstr "%s खराब गिट निर्देशिका है"

  reply	other threads:[~2010-09-06  4:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05 18:27 [PATCH] po/hi.po: Add Hindi Translation Ramkumar Ramachandra
2010-09-05 19:07 ` Ævar Arnfjörð Bjarmason
2010-09-06  0:54 ` Sitaram Chamarty
2010-09-06  4:29   ` Ramkumar Ramachandra [this message]
2010-09-07  3:44     ` Antriksh Pany
2010-09-07  7:55       ` Ramkumar Ramachandra
2010-09-08 13:53         ` Antriksh Pany
2010-09-08 14:50           ` Ramkumar Ramachandra
     [not found] ` <AANLkTinbbzZWTZcJMTP52Vf0wHixOSE8vYcOCqTQv832@mail.gmail.com>
2010-09-08 15:01   ` Ramkumar Ramachandra

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=20100906042942.GA32387@kytes \
    --to=artagnon@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sitaramc@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.