From: Arun Isaac <arunisaac@systemreboot.net>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>,
raamannp@gmail.com, Visuwesh <visuweshm@gmail.com>,
tshrinivasan@gmail.com, jkottalam@gmail.com,
Thanga Ayyanar <thangaayyanar@gmail.com>,
Mohan R <mohan43u@gmail.com>, Iron Man <stark20236@gmail.com>,
"Ashok Ramachandran (via Google Docs)" <ashokramach@gmail.com>
Cc: tamil@systemreboot.net
Subject: Re: An Attempt in Emacs Translation
Date: Fri, 08 Mar 2024 15:45:27 +0000 [thread overview]
Message-ID: <87wmqcpw14.fsf@systemreboot.net> (raw)
In-Reply-To: <87h6hg6f7u.fsf@gmail.com>
Hi Jai,
>> These translations are alright, except for Kill. In Emacs jargon, kill
>> not only means to delete, but also to copy into the kill ring.
>
> “வெட்டு” seems closer to kill’s modern equivalent ‘cut’, but it doesn’t
> seem like an apt translation.
Yes, வெட்டு sounds good.
>> So, kill is really "kill+copy". But, somehow this added meaning has
>> come to be implicit in English usage. Getting the same nuanced
>> translation in Tamil will be very difficult.
>
> I don’t understand the need to imply the exact meaning in the
> translation. When we used Emacs for the first time ourselves, we did not
> know what ‘kill’ meant in Emacs jargon, which was explained later.
>
> So unless we get a better alternative for ‘kill’, the current
> translation should suffice.
Agreed, makes sense.
>> We really need a large body of Tamil Emacs users who are willing to
>> use these words everyday and create the subtle shades of meaning that
>> is so easy in English.
>
> Are there even significant Tamil Gnu/Linux users, let alone Emacs or
> Guix? I’m writing these translations hoping that it serves some future
> user, but currently how widely are our works acknowledged? Are we
> echoing to the void?
Ha ha! That's why translating software stuff to Tamil is so
frustrating. The lines யாருக்காக, இது யாருக்காக, இந்த மாளிகை வசந்த மாளிகை
always come to mind. :-P Most Tamil users of Emacs simply prefer to use
English. Even we are having this conversation in English. So, I really
don't know how to fix this. Being able to see the real-world impacts of
our translation would be very gratifying indeed. Maybe, Shrinivasan is
the right person to talk about this. I know almost nothing about what's
happening in the Tamil computing community.
Regards,
Arun
next prev parent reply other threads:[~2024-03-08 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:13 Jai Vetrivelan
2024-03-01 23:47 ` Shrinivasan T
2024-03-08 13:16 ` Jai Vetrivelan
2024-03-07 21:21 ` Arun Isaac
2024-03-08 13:11 ` Jai Vetrivelan
2024-03-08 15:45 ` Arun Isaac [this message]
2024-03-08 16:41 ` யாருக்காக, இது யாருக்காக (was: An Attempt in Emacs Translation) Jai Vetrivelan
2024-03-08 17:00 ` An Attempt in Emacs Translation Visuwesh
2024-03-08 21:58 ` Jai Vetrivelan
[not found] ` <CAHXK8DaDizLBEDodOYd3KDM1qGtuWka2jXHJ--uiuhQuXd7Sxw@mail.gmail.com>
2024-03-08 13:22 ` Jai Vetrivelan
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=87wmqcpw14.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=ashokramach@gmail.com \
--cc=jaivetrivelan@gmail.com \
--cc=jkottalam@gmail.com \
--cc=mohan43u@gmail.com \
--cc=raamannp@gmail.com \
--cc=stark20236@gmail.com \
--cc=tamil@systemreboot.net \
--cc=thangaayyanar@gmail.com \
--cc=tshrinivasan@gmail.com \
--cc=visuweshm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox