unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Alex Vong <alexvong1995@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
	Guix-devel <guix-devel-bounces+me=tobias.gr@gnu.org>,
	help-guix <help-guix@gnu.org>
Subject: Re: Language tag for traditional Chinese
Date: Wed, 7 Mar 2018 22:34:22 +0100	[thread overview]
Message-ID: <20180307213422.GA7706@jurong> (raw)
In-Reply-To: <87y3j59yal.fsf@gmail.com>

Hello,

On Tue, Mar 06, 2018 at 08:35:46PM +0800, Alex Vong wrote:
> I also want to add tranditional Chinese translation to guix in the
> future (after I figure out how to use handwriting recognition). I think
> I will still use the zh_TW since I think it is an established convention
> for distro. But I am not sure if the same convention holds for web
> page.

if you look at the web page of the Translation Project, the two Chinese
language codes seem to be zh_CN and zh_TW:
   https://translationproject.org/team/index.html
There is also zh_HK, but no translation team is referenced for it.

Andreas

  reply	other threads:[~2018-03-07 21:34 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 16:02 Posts in languages other than English on help-guix? Ludovic Courtès
2018-03-02 16:47 ` ng0
2018-03-02 20:07   ` Andreas Enge
2018-03-02 20:23     ` Catonano
2018-03-03 11:00   ` Catonano
2018-03-02 20:03 ` Andreas Enge
2018-03-02 20:31   ` ng0
2018-03-03 10:00     ` Andreas Enge
2018-03-03 10:37       ` ng0
2018-03-03 15:25       ` Ricardo Wurmus
2018-03-05  8:57         ` Ludovic Courtès
2018-03-05  9:42           ` julien lepiller
2018-03-05 14:14             ` Ludovic Courtès
2018-03-05 15:22               ` julien lepiller
2018-03-10 15:19                 ` Ludovic Courtès
2018-03-19 15:20                   ` julien lepiller
2018-03-19 16:43                     ` Ludovic Courtès
2018-03-03 10:45     ` Hartmut Goebel
2018-03-03 10:52       ` Hartmut Goebel
2018-03-03 11:48         ` Konrad Hinsen
2018-03-02 20:32   ` Gábor Boskovits
2018-03-02 22:18     ` Ludovic Courtès
2018-03-02 22:17   ` Ludovic Courtès
2018-03-03 10:27 ` Clément Lassieur
2018-03-03 14:50 ` Marco van Hulten
2018-03-03 20:06   ` Marius Bakke
2018-03-04  8:39     ` Marco van Hulten
2018-03-03 18:35 ` Leo Famulari
2018-03-03 20:24 ` Alex Vong
2018-03-05  8:45   ` Ludovic Courtès
2018-03-05 15:05     ` Language tag for traditional Chinese (was: Posts in languages other than English on help-guix?) Tobias Geerinckx-Rice
2018-03-06 12:35       ` Language tag for traditional Chinese Alex Vong
2018-03-07 21:34         ` Andreas Enge [this message]
2018-03-07 22:39         ` Ludovic Courtès
2018-12-07  9:04           ` Alex Vong
2018-03-05  0:17 ` Posts in languages other than English on help-guix? Eric Bavier
2018-03-07  9:46 ` Oleg Pykhalov
2018-03-08 20:56   ` Alex Kost
2018-03-10 10:39     ` Oleg Pykhalov
2018-03-10 15:11       ` Ludovic Courtès
2018-03-10 15:15   ` Ludovic Courtès
2018-03-17 18:48 ` Chris Marusich
2018-03-17 20:19   ` Chris Marusich
2018-03-19 16:44     ` Ludovic Courtès
2018-03-22  3:22       ` Chris Marusich
2018-03-26 12:49         ` Ludovic Courtès

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180307213422.GA7706@jurong \
    --to=andreas@enge.fr \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel-bounces+me=tobias.gr@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).