From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Frederik Schwarzer <schwarzerf@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: i18n: Avoid sentence puzzles
Date: Mon, 30 Jan 2012 18:46:52 +0700 [thread overview]
Message-ID: <CACsJy8CUXSSvToPrx9aW5a76BV=g7OTrWLZ2MQ6xDTpDSLpPeA@mail.gmail.com> (raw)
In-Reply-To: <201201301231.21090.schwarzerf@gmail.com>
On Mon, Jan 30, 2012 at 6:31 PM, Frederik Schwarzer
<schwarzerf@gmail.com> wrote:
> Hi,
>
> in order to enable translators to prepare proper translations,
> sentence puzzles have to be avoided. While it makes perfect sense for
> English, some languages may have to separate those words to sound or
> even be correct.
>
> The attached patch demonstrates a change to achive that.
> ...
> So my question would be: Is it considered worth it to extend the code
> for translators' and translations' sake? If so, I would be glad to
> help with that.
As a translator (though not git's because my time is limited and GUI
apps have my priority), I completely agree and support this. There are
other places where a sentence is broken down into many short phrases.
It's hard for a translator to find a good translation in such cases.
I remember there was also a patch about "1 file vs 2 files" in diff
summary, which was rejected because it would break scripts. I think
grammar patches should be allowed at least for interactive use (i.e.
either pager is on, or std{out,err} is tty).
--
Duy
next prev parent reply other threads:[~2012-01-30 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 11:31 i18n: Avoid sentence puzzles Frederik Schwarzer
2012-01-30 11:46 ` Nguyen Thai Ngoc Duy [this message]
2012-01-30 18:57 ` Junio C Hamano
2012-01-30 21:12 ` Ævar Arnfjörð Bjarmason
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='CACsJy8CUXSSvToPrx9aW5a76BV=g7OTrWLZ2MQ6xDTpDSLpPeA@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=schwarzerf@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;
as well as URLs for NNTP newsgroup(s).