From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Xudong Guan" <xudong.guan@gmail.com>,
git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
しらいしななこ <nanako3@bluebottle.com>,
"Christian Stimming" <stimming@tuhh.de>
Subject: Re: [PATCH] Initial Chinese translation
Date: Sun, 22 Jul 2007 03:35:19 -0400 [thread overview]
Message-ID: <20070722073519.GV32566@spearce.org> (raw)
In-Reply-To: <7vhcnxtgvw.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <gitster@pobox.com> wrote:
> Xudong Guan <xudong.guan@gmail.com> writes:
>
> > Simplified Chinese, in UTF-8 encoding.
> >
> > Signed-off-by: Xudong Guan <xudong.guan@gmail.com>
> > ---
> > po/zh.po | 250 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 files changed, 250 insertions(+), 0 deletions(-)
>
> This raises another point in the current i18n scheme. How would
> we allow zh_CN and zh_TW to coexist?
They probably should be po/zh_CN.po and po/zh_TW.po. Tcl msgcat
loads the file that best matches the user's local preferences, so
zh.po would be the fallback if neither zh_CN and zh_TW were present,
or if the user was using say zh_US as their preferred local.
--
Shawn.
next prev parent reply other threads:[~2007-07-22 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 0:08 [PATCH] Initial Chinese translation Xudong Guan
2007-07-22 0:32 ` Junio C Hamano
2007-07-22 0:34 ` Johannes Schindelin
2007-07-22 0:54 ` Xudong Guan
2007-07-22 0:35 ` Junio C Hamano
2007-07-22 7:35 ` Shawn O. Pearce [this message]
2007-07-22 8:06 ` Junio C Hamano
2007-07-22 8:53 ` Xudong Guan
2007-07-22 9:06 ` Junio C Hamano
2007-07-22 11:39 ` Johannes Schindelin
2007-07-22 12:04 ` Johannes Schindelin
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=20070722073519.GV32566@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nanako3@bluebottle.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=stimming@tuhh.de \
--cc=xudong.guan@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).