[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs i18n
From: |
Paul Eggert |
Subject: |
Re: Emacs i18n |
Date: |
Tue, 26 Mar 2019 18:35:43 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 |
On 3/26/19 4:16 PM, Juri Linkov wrote:
> I'll start writing documentation. Is it allowed to make references
> from the Elisp manual to the Gettext Info manual? I see in (info
> "(gettext) elisp-format") a reference back to the Elisp manual is a
> web link, not an Info reference.
>
Thanks for taking this on. Yes, you can do cross-references; e.g.,
files.texi has this:
@xref{File permissions,,, coreutils, The @sc{gnu} @code{Coreutils}
Manual}
> It seems most of these needs could be covered by adding two optional
> arguments DOMAIN and CATEGORY to ngettext (where the default domain
> "emacs" will be hard-coded).
>
This appears to be what CLISP does; see:
https://sourceforge.net/p/clisp/clisp/ci/default/tree/modules/i18n/i18n.lisp
https://clisp.sourceforge.io/impnotes.html#i18n-mod
> As a convenience not to require a package to add its domain to every
> ngettext call, maybe when something like 'defdomain' is declared at
> the beginning of the package, its value should affect the domain
> within the package scope.
>
Would this be done statically or dynamically? Preferably the former but
I don't exactly see how it would work, and even dynamically the details
are not obvious to me.
For example, would you have to do something like the following?
(define mymodule--ngettext (n sing-msgid pl-msgid) (ngettext n
sing-msgid pl-msgid "mymodule"))
(defun report-items (n) (message (mymodule--ngettext n "%d item" "%d
items") n))
(defun report-keystrokes (n) (message (mymodule--ngetext n "%d keystroke
received." "%d keystrokes received.") n))
Something like this would work, but it looks pretty annoying....
- Re: Emacs i18n, (continued)
- Re: Emacs i18n, Paul Eggert, 2019/03/26
- Re: Emacs i18n, Eli Zaretskii, 2019/03/26
- Re: Emacs i18n, Clément Pit-Claudel, 2019/03/28
- Re: Emacs i18n, Eli Zaretskii, 2019/03/28
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/26
- Re: Emacs i18n, Juri Linkov, 2019/03/26
- Re: Emacs i18n,
Paul Eggert <=
- Re: Emacs i18n, Eli Zaretskii, 2019/03/24
- Re: Emacs i18n, Jean-Christophe Helary, 2019/03/25
- Re: Emacs i18n, Juri Linkov, 2019/03/25
- Re: Emacs i18n, Eli Zaretskii, 2019/03/25
- Re: Emacs i18n, Richard Stallman, 2019/03/27
- Re: Emacs i18n, Mattias Engdegård, 2019/03/25
- Re: Emacs i18n, Eli Zaretskii, 2019/03/25
- Re: Emacs i18n, Juri Linkov, 2019/03/25
- Re: Emacs i18n, Mattias Engdegård, 2019/03/25
- Re: Emacs i18n, Juri Linkov, 2019/03/27