unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Before l10n, better practices for (message) ?
Date: Tue, 23 May 2017 21:36:08 +0300	[thread overview]
Message-ID: <83zie3mndz.fsf@gnu.org> (raw)
In-Reply-To: <6BED2506-B1C2-4005-AFDE-2BF04209F16C@gmail.com> (message from Jean-Christophe Helary on Tue, 23 May 2017 12:38:29 +0900)

> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
> Date: Tue, 23 May 2017 12:38:29 +0900
> 
> 
> > On May 23, 2017, at 11:55, Eli Zaretskii <eliz@gnu.org> wrote:
> > 
> >> I'm currently going through package.el and the easiest solution I have for now is replace things like "%d package%s to install" (where %s is "s" depending on whether %d is greater than 1...) into "Number of packages to install: %d.".
> > 
> > Just replace it with 2 different spellings dispatched by the number.
> 
> I know we don't have l10n now, but what you propose is also based on the grammatical assumption that we have only 2 possible forms so I would try to avoid that too.

Having 2 forms is as close to the ideal as we can have, given that we
don't have infrastructure for more complicated cases.  Introducing
functions that will meanwhile do nothing non-trivial doesn't sound a
good idea to me; such functions will only make sense when they
actually support non-trivial plurals (and for that, we need first to
figure out how to select the language into which any given message
needs to be translated).

> > We don't have any mechanisms that I know of, and won't have until the
> > large part of the i10n issues is resolved by motivated individuals.
> 
> I guess I just found something to do in the coming months... :)
> 
> What I'll do is propose a patch for package.el that makes UI strings the most linguistically neutral possible (within my understanding of English), and after discussing the changes, if we can use that as a base to create a list of "best practices", I'll use that to check the other packages included in the distribution.

I'm not sure package.el is a good starting point.  I think a much
better starting point is to design the i10n infrastructure for Emacs.



  reply	other threads:[~2017-05-23 18:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 23:30 Before l10n, better practices for (message) ? Jean-Christophe Helary
2017-05-23  0:59 ` Tino Calancha
2017-05-23  1:18   ` Jean-Christophe Helary
2017-05-23  2:55     ` Eli Zaretskii
2017-05-23  3:38       ` Jean-Christophe Helary
2017-05-23 18:36         ` Eli Zaretskii [this message]
2017-05-23 22:00           ` Jean-Christophe Helary
2017-05-24  2:32             ` Eli Zaretskii
2017-05-24  2:40               ` Jean-Christophe Helary
2017-05-24  4:22                 ` Paul Eggert
2017-05-24  8:08                   ` Jean-Christophe Helary
2017-05-24 19:12                     ` Eli Zaretskii
2017-05-24 21:29                       ` Jean-Christophe Helary
2017-05-26  3:50                         ` Richard Stallman
2017-05-24 22:09                       ` Paul Eggert
2017-05-24 22:35                         ` Jean-Christophe Helary
2017-05-26  8:07                           ` Eli Zaretskii
2017-05-24 23:51                         ` Jean-Christophe Helary
2017-05-23  7:52       ` Jean-Christophe Helary
2017-05-23 18:42         ` Eli Zaretskii
2017-05-23 22:03           ` Jean-Christophe Helary
2017-05-26  8:14             ` Eli Zaretskii
2017-05-26 14:21               ` Jean-Christophe Helary
2017-05-26 14:44                 ` Eli Zaretskii
2017-05-26 18:08                   ` Yuri Khan
2017-05-26 19:00                     ` Eli Zaretskii
2017-05-27  1:52                       ` Jean-Christophe Helary
2017-05-26 18:54               ` Etienne Prud’homme
2017-05-26 19:06                 ` Eli Zaretskii
2017-05-26 19:15                   ` Etienne Prud’homme
2017-05-26 19:27                     ` Eli Zaretskii
2017-05-26 21:57                       ` Etienne Prud’homme
2017-05-27  7:22                         ` Eli Zaretskii
2017-05-27  1:16                 ` Jean-Christophe Helary
2017-05-27  7:43                   ` Eli Zaretskii
2017-05-27  4:08       ` Marcin Borkowski
2017-05-27  7:49         ` Eli Zaretskii
2017-05-28  4:00           ` Marcin Borkowski
2017-05-27 23:27         ` Göktuğ Kayaalp
2017-05-28  0:44           ` Jean-Christophe Helary
2017-05-28 14:44             ` Göktuğ Kayaalp

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=83zie3mndz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).