Source strings

83 Strings
100%
Browse Translate
1,486 Words
100%
9,903 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
83 1,486 9,903
All strings Browse Translate Zen
83 1,486 9,903
Read-only strings Browse Translate Zen
10 47 498
Strings with any failing checks Browse Translate Zen
1 13 88
Failing check: Ellipsis Browse Translate Zen
9 34 410
Failing check: Multiple failing checks Browse Translate Zen

Summary

Project website forge.fedoraproject.org
Instructions for translators

Mailing list for translators: trans@lists.fedoraproject.org
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://forge.fedoraproject.org/localization-docs/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files 1ab5f59a9
♪ I'm a bot, bot, bot ♪ authored 05/31/2026
Last commit in Weblate Translated using Weblate (Spanish) 42369b243
User avatar vareli authored 06/14/2026
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Emacs.po
Translation file Download pot/master/pages/Emacs.pot
Last change Nov. 24, 2025, 10:16 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
05/19/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 83 1,486 9,903
Translated 100% 83 100% 1,486 100% 9,903
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 83 100% 1,486 100% 9,903
Failing checks 12% 10 3% 47 5% 498
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 28 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

1,486
Hosted words
83
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “pot/master/pages/Emacs.pot” file was changed. 11/24/2025
User avatar None

String added in the repository
It is often the case that a software package, while not being primarily an Emacs add-on package, will contain components for Emacs. For example, the Gnuplot program contains some elisp files for editing Gnuplot input files in GNU Emacs and running Gnuplot from GNU Emacs. In this case, we want to enable the Emacs support IF Emacs is installed, but we don't want to mandate the installation of Emacs on installation of this package since Emacs is not required for providing the core functionality of the package. To enable this, the `+emacs-filesystem+` sub-package was created which owns the `+/usr/share/emacs/site-lisp+` directory. A package can then Require the `+emacs-filesystem+` package in order to install its Elisp files without pulling in Emacs and its dependency chain.
It is often the case that a software package, while not being primarily an Emacs add-on package, will contain components for Emacs. For example, the Gnuplot program contains some elisp files for editing Gnuplot input files in GNU Emacs and running Gnuplot from GNU Emacs. In this case, we want to enable the Emacs support IF Emacs is installed, but we don't want to mandate the installation of Emacs on installation of this package since Emacs is not required for providing the core functionality of the package. To enable this, the `+emacs-filesystem+` sub-package was created which owns the `+/usr/share/emacs/site-lisp+` directory. A package can then Require the `+emacs-filesystem+` package in order to install its Elisp files without pulling in Emacs and its dependency chain.
11/24/2025
User avatar None

String added in the repository
It is recommended to derive greater-than-or-equal-to valued versioned dependencies from the version of Emacs used to byte-compile the package at package build time. The `+emacs-common+` package includes `+/usr/lib/rpm/macros.d/macros.emacs+` which defines a `+%{_emacs_version}+` macro containing the version of Emacs installed.
It is recommended to derive greater-than-or-equal-to valued versioned dependencies from the version of Emacs used to byte-compile the package at package build time. The `+emacs-common+` package includes `+/usr/lib/rpm/macros.d/macros.emacs+` which defines a `+%{_emacs_version}+` macro containing the version of Emacs installed.
11/24/2025
User avatar None

String added in the repository
So let's say I byte-compile a package into `+*.elc+` with Emacs 29.3. Elisp package `_quux_` checks if the `_foo-bar_` function is available in the Emacs being used to byte-compile it. Yes, it is, so the internal backwards compat version of `_foo-bar_` included in `_quux_` does not end up in the `+*.elc+`. Now, let's assume `_foo-bar_` was added in Emacs 29.3 and didn't exist in 29.2 and we're trying to run the `+*.elc+` with 29.2 -> boom, `_foo-bar_` is not available. Note: this wouldn't happen if only `+*.el+` were shipped - `+*.elc+` are the potential and likely problem. Requiring >= version of the Emacs used to byte-compile the `+*.elc+` is not the only solution (nor enough for all corner cases), but is the best one we currently have available.
So let's say I byte-compile a package into `+*.elc+` with Emacs 29.3. Elisp package `_quux_` checks if the `_foo-bar_` function is available in the Emacs being used to byte-compile it. Yes, it is, so the internal backwards compat version of `_foo-bar_` included in `_quux_` does not end up in the `+*.elc+`. Now, let's assume `_foo-bar_` was added in Emacs 29.3 and didn't exist in 29.2 and we're trying to run the `+*.elc+` with 29.2 -> boom, `_foo-bar_` is not available. Note: this wouldn't happen if only `+*.el+` were shipped - `+*.elc+` are the potential and likely problem. Requiring >= version of the Emacs used to byte-compile the `+*.elc+` is not the only solution (nor enough for all corner cases), but is the best one we currently have available.
11/24/2025
User avatar None

String added in the repository
Many elisp packages aim for backwards source level compatibility by checking whether some features exist in the Emacs in use when the package is being run or byte-compiled. If yes, they use what's available. If no, they provide their own versions of missing functions, macros etc. This propagates into `+*.elc+` during byte compilation, and quite a few functions do get added between upstream Emacs releases.
Many elisp packages aim for backwards source level compatibility by checking whether some features exist in the Emacs in use when the package is being run or byte-compiled. If yes, they use what's available. If no, they provide their own versions of missing functions, macros etc. This propagates into `+*.elc+` during byte compilation, and quite a few functions do get added between upstream Emacs releases.
11/24/2025
User avatar None

String added in the repository
If the package ONLY works with GTK support built into Emacs, then the package should have `+Requires: emacs+`. This is very uncommon.
If the package ONLY works with GTK support built into Emacs, then the package should have `+Requires: emacs+`. This is very uncommon.
11/24/2025
User avatar None

String added in the repository
Assuming your add-on package will work in both a windowed and a console Emacs session, it is wrong to have `+Requires: emacs+` as that would pull in a dependency on GTK even if the console variant of Emacs is installed. Rather you should use Requires: `+emacs(bin)+` for GNU Emacs add-on packages.
Assuming your add-on package will work in both a windowed and a console Emacs session, it is wrong to have `+Requires: emacs+` as that would pull in a dependency on GTK even if the console variant of Emacs is installed. Rather you should use Requires: `+emacs(bin)+` for GNU Emacs add-on packages.
11/24/2025
User avatar None

String added in the repository
The emacs, `+emacs-gtk+x11+`, `+emacs-lucid+`, and `+emacs-nw+` packages all have a virtual Provides: `+emacs(bin)+`.
The emacs, `+emacs-gtk+x11+`, `+emacs-lucid+`, and `+emacs-nw+` packages all have a virtual Provides: `+emacs(bin)+`.
11/24/2025
User avatar None

String added in the repository
The `+emacs+`, `+emacs-gtk+x11+`, `+emacs-lucid+`, and `+emacs-nw+` packages all have Requires: emacs-common.
The `+emacs+`, `+emacs-gtk+x11+`, `+emacs-lucid+`, and `+emacs-nw+` packages all have Requires: emacs-common.
11/24/2025
User avatar None

String added in the repository
The `+emacs-nw+` package is built without GUI support. It is suitable for running in a terminal.
The `+emacs-nw+` package is built without GUI support. It is suitable for running in a terminal.
11/24/2025
Browse all translation changes