unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Fernando Botelho <Fernando.Botelho@F123.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
	Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: i18n - Revisited
Date: Thu, 27 Apr 2017 09:56:54 -0300	[thread overview]
Message-ID: <2e7fbaec-f580-0560-c526-39c8432aa94d@F123.org> (raw)
In-Reply-To: <E3E7CF1E-F36F-41BD-95FA-D39E85D64F6E@gmail.com>

Thanks Jean-Christophe and Paul for your responses.

It is good to know that the i18n process is on-going. Is this "more 
languages group" operational via e-mail list? how can I join?

I want to ask questions like:

Are there plans for l10n of the interface strings and command names, or 
is this postponed for now because of complexity?

For areas where l10n is already happening, where can I join the effort, 
i.e. are there web interfaces where strings are shown and translations 
entered, or gettext/.POT files on a git repository somewhere?

Are there "how to" guides for non-technical translators who want to help?

I suspect many of my questions are too basic and may irritate people on 
this list.

Best,

Fernando




  reply	other threads:[~2017-04-27 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26 19:32 i18n - Revisited Fernando Botelho
2017-04-26 20:22 ` Paul Eggert
2017-04-27  0:21   ` Jean-Christophe Helary
2017-04-27 12:56     ` Fernando Botelho [this message]
2017-04-27 15:07       ` Jean-Christophe Helary
2017-04-27 16:24         ` Fernando Botelho
2017-04-27 16:33           ` Jean-Christophe Helary
2017-04-27 17:36             ` Fernando Botelho
2017-04-27 20:20           ` Eli Zaretskii
2017-04-27 20:34             ` Fernando Botelho

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=2e7fbaec-f580-0560-c526-39c8432aa94d@F123.org \
    --to=fernando.botelho@f123.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@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://git.savannah.gnu.org/cgit/emacs.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).