From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@talktalk.net>
Cc: Andrew Janke <floss@apjanke.net>,
git@vger.kernel.org, Jiang Xin <worldhello.net@gmail.com>
Subject: Re: gettext, multiple Preferred languages, and English
Date: Mon, 22 Apr 2019 08:44:19 +0900 [thread overview]
Message-ID: <xmqqbm0yappo.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <bd5ee770-a213-b663-208c-c9980a738fe9@talktalk.net> (Philip Oakley's message of "Sun, 21 Apr 2019 13:59:48 +0100")
Philip Oakley <philipoakley@talktalk.net> writes:
> On 21/04/2019 12:08, Andrew Janke wrote:
> https://public-inbox.org/git/d001a2b5-57c3-1eb3-70fd-679919bb2eb6@apjanke.net/
>> I don't think it would even have
>> to be actively maintained, because for new message strings that aren't
>> included in the .po file, it would fall back to the non-translated input
>> strings, which are in English anyway, which is the desired behavior.
> Given the above comment, could the en.po file
> (https://github.com/apjanke/git/blob/english-dummy-translation/po/en.po)
> be some very very short version with only one 'translated' string?
Or use LC_ALL=C and be done with it?
> This may be a way-off comment, but if it could be such a simple
> maintenance free file then that sounds sensible.
>
> also adding in Jiang Xin <worldhello.net@gmail.com>, the coordinator
> for extra comment.
>
> Philip
next prev parent reply other threads:[~2019-04-21 23:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 11:08 gettext, multiple Preferred languages, and English Andrew Janke
2019-04-21 12:59 ` Philip Oakley
2019-04-21 13:27 ` Andrew Janke
2019-04-22 1:33 ` Andrew Janke
2019-04-21 23:44 ` Junio C Hamano [this message]
2019-04-22 0:35 ` Duy Nguyen
2019-04-22 0:57 ` Andrew Janke
2019-04-22 17:47 ` Ævar Arnfjörð Bjarmason
2019-04-23 11:45 ` Andrew Janke
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=xmqqbm0yappo.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=floss@apjanke.net \
--cc=git@vger.kernel.org \
--cc=philipoakley@talktalk.net \
--cc=worldhello.net@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).