Translation status

83 Strings 0%
Browse Translate
1,486 Words 0%
9,696 Characters 0%

Strings status

Strings Words Characters
83 1,486 9,696
All strings Browse Translate Zen
83 1,486 9,696
Unfinished strings Browse Translate Zen
83 1,486 9,696
Untranslated strings Browse Translate Zen
2 4 43
Strings with suggestions Browse Translate Zen
81 1,482 9,653
Unfinished strings without suggestions 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 7660837d1
♪ I'm a bot, bot, bot ♪ authored 24 minutes ago
Last commit in Weblate Update translation files 59fcabe17
Weblate authored 28 minutes ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Emacs.po
Translation file Download po/zh_Hans/master/pages/Emacs.po
Last change July 19, 2024, 5:48 a.m.
Last change made by Weblate Translation Memory
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Number of speakers 1,286,095,292
Number of plurals 1
Plural type None
Plurals
Plural formula 0
21 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 83 1,486 9,696
Translated 0% 0 0% 0 0% 0
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 2% 2 1% 4 1% 43
Untranslated strings 100% 83 100% 1,486 100% 9,696
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 46 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

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

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
—
—
Contributors
—
User avatar mt:weblate-translation-memory

Suggestion added
%prep
%autosetup
%prep
%autosetup
5 months ago
User avatar mt:weblate-translation-memory

Suggestion added
%changelog
%autochangelog
%changelog
%autochangelog
5 months ago
User avatar None

Resource updated
The “po/zh_Hans/master/pages/Emacs.po” file was changed. 6 months ago
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.
 
6 months ago
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.
 
6 months ago
User avatar None

String added in the repository
Determining the Required Emacs version at package build time
 
6 months ago
User avatar None

String added in the repository
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.
 
6 months ago
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.
 
6 months ago
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.
 
6 months ago
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.
 
6 months ago
Browse all translation changes