[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Emacs and the translation domain "gnulib"
From: |
Bruno Haible |
Subject: |
Re: GNU Emacs and the translation domain "gnulib" |
Date: |
Wed, 11 Dec 2024 17:05:00 +0100 |
Hi Paul,
Paul Eggert wrote:
> Although Emacs uses some Gnulib modules, it doesn't use translations or
> the gettext function so it won't use the "gnulib" translation domain.
> Also, Emacs developers prefer using less Gnulib code when possible.
> ...
> With that in mind I am planning to have Emacs avoid gnulib-i18n
That's the correct approach. You can do the same thing in the 'gzip' package
as well (with is also not internationalized).
Note that there will still be a couple of invocations of dgettext("gnulib",...)
at runtime. Since there is no corresponding bindtextdomain("gnulib",...) call
in the code, these dgettext invocations will return the argument string
unchanged. This is not speed-critical, therefore it does not require further
optimization.
> I'd like to install the attached doc patch into Gnulib.
The patch is perfect as well.
Bruno
- Re: Use the translation domain "gnulib", (continued)
- Re: Use the translation domain "gnulib", Bruno Haible, 2024/12/10
- Re: Use the translation domain "gnulib", Bruno Haible, 2024/12/17
- Re: Use the translation domain "gnulib", Jim Meyering, 2024/12/17
- Re: warnings from gzip and diffutils, Bruno Haible, 2024/12/17
- Re: warnings from gzip and diffutils, Paul Eggert, 2024/12/18
- Re: warnings from gzip and diffutils, Bruno Haible, 2024/12/18
- Re: warnings from gzip and diffutils, Simon Josefsson, 2024/12/18
- Re: warnings from gzip and diffutils, Bruno Haible, 2024/12/18
GNU Emacs and the translation domain "gnulib", Paul Eggert, 2024/12/10
- Re: GNU Emacs and the translation domain "gnulib",
Bruno Haible <=