Source strings

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

Strings status

Strings Words Characters
83 1,486 9,696
All strings Browse Translate Zen
83 1,486 9,696
Read-only strings Browse Translate Zen
1 13 88
Strings with any failing checks Browse Translate Zen
1 13 88
Failing check: Ellipsis Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
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 ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files b38d9c201
♪ I'm a bot, bot, bot ♪ authored 9 days ago
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 May 30, 2024, 10:45 p.m.
Last author None
9 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 83 1,486 9,696
Translated 100% 83 100% 1,486 100% 9,696
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 83 100% 1,486 100% 9,696
Failing checks 1% 1 1% 13 1% 88
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 19 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 46 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

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

Trends of last 30 days

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

Resource updated

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
The “pot/master/pages/Emacs.pot” file was changed. 9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
Determining the Required Emacs version at package build time
Determining the Required Emacs version at package build time
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
The main package and subpackages will need to have appropriately versioned Requires to ensure that a recent enough version of Emacs is installed. Emacs byte compiled lisp is usually forward compatible with later Emacs versions, but is frequently not compatible with earlier versions of Emacs.
The main package and subpackages will need to have appropriately versioned Requires to ensure that a recent enough version of Emacs is installed. Emacs byte compiled lisp is usually forward compatible with later Emacs versions, but is frequently not compatible with earlier versions of Emacs.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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.
9 days ago
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Emacs
  3. English
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).
9 days ago
Browse all translation changes