From: Kevin Daudt <me@ikke.info>
To: Alangi Derick <alangiderick@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Subject: Re: Improving code base readability
Date: Sun, 3 May 2015 18:11:11 +0200 [thread overview]
Message-ID: <20150503161111.GA28448@vps892.directvps.nl> (raw)
In-Reply-To: <CAKB+oNtUy12qumkE7VAe8_N6aHesJtMqpWNxi3M-7yOviE6BLQ@mail.gmail.com>
On Sat, May 02, 2015 at 08:15:45AM +0100, Alangi Derick wrote:
> I read the po/README and also the po/TEAMS and i can't find English
> there as a language. So what should i do or is it that the english in
> the error messages are not clear that i can work on?
The idea is to find error messages in the code base that are not marked
for translation. That is:
error("Something is wrong");
should be:
error(_("Something is wrong"));
This way, these strings will be extracted for the teams for translation.
There is no english because those messages are already in the code.
prev parent reply other threads:[~2015-05-03 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 15:26 Improving code base readability Alangi Derick
2015-05-01 18:59 ` Jonathan Nieder
2015-05-02 7:00 ` Alangi Derick
2015-05-02 7:15 ` Alangi Derick
2015-05-03 16:11 ` Kevin Daudt [this message]
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=20150503161111.GA28448@vps892.directvps.nl \
--to=me@ikke.info \
--cc=alangiderick@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=sbeller@google.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).