From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Has anyone looked at Gettext support for Git itself?
Date: Sun, 16 May 2010 13:12:55 +0000 [thread overview]
Message-ID: <AANLkTilWXqXUtDU-r6j6DwBJWK3JoQNwGnnQPHQWhIUF@mail.gmail.com> (raw)
In-Reply-To: <20100516053651.GB17200@dpotapov.dyndns.org>
On Sun, May 16, 2010 at 05:36, Dmitry Potapov <dpotapov@gmail.com> wrote:
> 'echo -n' is not portable, and it is not used in git for this reason.
> If gettext does not add the trailing newline to the message then it is
> clearly not equivalent replacement.
That was just meant to be a non-working example of how we could read
gettext from .sh too. I didn't actually try to run it. Obviously a
real implementation wouldn't use 'echo -n' and wouldn't suffer from
newline issues.
I just wanted to show that regardless of whether the program is in C,
Perl or Shell a gettext implementation can degrade gracefully. That's
all.
next prev parent reply other threads:[~2010-05-16 13:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 22:10 Has anyone looked at Gettext support for Git itself? Ævar Arnfjörð Bjarmason
2010-05-16 0:03 ` Jakub Narebski
2010-05-16 1:12 ` Ævar Arnfjörð Bjarmason
2010-05-16 5:36 ` Dmitry Potapov
2010-05-16 13:12 ` Ævar Arnfjörð Bjarmason [this message]
2010-05-16 16:08 ` Jan Hudec
2010-05-16 17:37 ` Ævar Arnfjörð Bjarmason
2010-05-17 14:32 ` Thomas Rast
2010-05-17 14:53 ` Ævar Arnfjörð Bjarmason
2010-05-17 15:12 ` Thomas Rast
2010-05-17 17:59 ` Jan Hudec
2010-05-17 18:56 ` Will Palmer
2010-05-18 7:51 ` Michael J Gruber
2010-05-18 9:35 ` Thomas Singer
2010-05-18 13:33 ` Will Palmer
2010-05-22 11:01 ` Jan Hudec
2010-05-19 15:43 ` demerphq
2010-05-16 16:53 ` Thomas Singer
2010-05-17 15:04 ` Marc Weber
2010-05-18 7:12 ` Peter Krefting
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilWXqXUtDU-r6j6DwBJWK3JoQNwGnnQPHQWhIUF@mail.gmail.com \
--to=avarab@gmail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).