From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Before l10n, better practices for (message) ?
Date: Tue, 23 May 2017 10:18:46 +0900 [thread overview]
Message-ID: <DAC9C410-0C71-44EB-B8BD-A09C5B410A2E@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1705230958420.24939@calancha-pc>
> On May 23, 2017, at 9:59, Tino Calancha <tino.calancha@gmail.com> wrote:
> On Tue, 23 May 2017, Jean-Christophe Helary wrote:
>
>> I just bumped into an English/code bug this morning. In package.el, when 1 package is not needed anymore, the message is:
>>
>> "Package menu: Operation finished. 1 packages are no longer needed, type ‘M-x package-autoremove’ to remove them"
...
>> So I'm asking whether do we have "best practices" for using messages...
> This was discussed in
> https://lists.gnu.org/archive/html/emacs-devel/2016-09/msg00502.html
>
> I proposed to add a simple function `string-plural-s' to standarize those
> plurarizations.
Yes, but no.
As a person who pays his bills doing translation and l10n, I would *never* recommend to create UI strings programatically based on *grammatical* assumptions. In fact I would forbid that if I could :) And I think that should be an Emacs policy for all UI strings...
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.".
The packages.el authors have created incredible messages where "ing" is replaced by "ed" depending on whether the process is running or completed, just so as to save a few lines of static strings. Of course, the code is very clever, but if we want to create a base for l10n one day, all these clever grammatical hacks must permanently go away...
So, as I just wrote, I'm working on package.el right now and I'll submit a patch, and when I'm done, I'd like to see what kind of mechanisms we have (or we need to create) to extract strings and use localized ressources.
Jean-Christophe
next prev parent reply other threads:[~2017-05-23 1:18 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 [this message]
2017-05-23 2:55 ` Eli Zaretskii
2017-05-23 3:38 ` Jean-Christophe Helary
2017-05-23 18:36 ` Eli Zaretskii
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=DAC9C410-0C71-44EB-B8BD-A09C5B410A2E@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=emacs-devel@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.
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).