From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: jean.christophe.helary@gmail.com, emacs-devel@gnu.org
Subject: Re: Before l10n, better practices for (message) ?
Date: Fri, 26 May 2017 22:00:21 +0300 [thread overview]
Message-ID: <831srbjvei.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8VjGD+KK33RCG=Pzw+-TwFKYOLeFFdbMEWBu96Mky7SAw@mail.gmail.com> (message from Yuri Khan on Sat, 27 May 2017 01:08:20 +0700)
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Sat, 27 May 2017 01:08:20 +0700
> Cc: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
> Emacs developers <emacs-devel@gnu.org>
>
> (require 'gettext)
>
> (message (dgettext "hello" "Hello World!"))
>
> Gettext also has a helper function named gettext and aliased _, which
> use the domain set by an earlier invocation of textdomain(). In Elisp,
> it seems most natural to express that like this:
>
> (defun hello-_ (key)
> (dgettext "hello" key))
> (message (hello-_ "Hello World!"))
>
> The function hello-_ would be defined once in the hello package and
> then used throughout it. Another package would define its own wrapper
> around dgettext, with a different domain.
>
>
> Inside, dgettext could consult a two-level hashtable, first keyed by
> domain, second by key. Alternatively, a domain could be a hashtable
> variable; in the latter case:
>
> ;; in hello.el
> (defvar hello-domain nil)
> (defun hello-_ (key)
> (dgettext hello-domain key))
> (message (hello-_ "Hello World!"))
>
> ;; in gettext.el
> (defun dgettext (domain key)
> (gethash key domain key))
Why not hide all this ugliness inside 'message'?
next prev parent reply other threads:[~2017-05-26 19:00 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
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 [this message]
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=831srbjvei.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=yuri.v.khan@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).