fedora-docs-l10n/packaging-guidelines/master/pages/SourceURL

Source strings

83	Strings		100%	Browse Translate
1,487	Words		100%	Browse Translate

This translation is being used as source strings within this component.

Strings status

83	All strings — 1,487 words	Browse Translate Zen
83	Read-only strings — 1,487 words	Browse Translate Zen
3	Strings with any failing checks — 44 words	Browse Translate Zen
3	Failing check: Ellipsis — 44 words	Browse Translate Zen

Other components

Component	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
master/pages/MPI CC-BY-SA-3.0	0	0	0	0	0	0	0

master/pages/D CC-BY-SA-3.0	0	0	0	0	0	0	0

master/pages/Python CC-BY-SA-3.0	0	0	0	0	26	0	0

master/pages/Golang_advanced CC-BY-SA-3.0	0	0	0	0	0	0	0

master/pages/index CC-BY-SA-3.0	0	0	0	0	14	0	0

master/pages/Tcl CC-BY-SA-3.0	0	0	0	0	1	0	0

master/pages/FontsPolicy CC-BY-SA-3.0	0	0	0	0	0	0	0

master/pages/LibreOfficeExtensions CC-BY-SA-3.0	0	0	0	0	1	0	0

master/pages/Systemd CC-BY-SA-3.0	0	0	0	0	6	0	0

master/pages/Python_Appendix CC-BY-SA-3.0	0	0	0	0	2	0	0

Browse all components

Overview

Project website	pagure.io/fedora-docs-l10n/packaging-guidelines
Instructions for translators	Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Translation license	Creative Commons Attribution Share Alike 3.0 Unported
Source code repository	`ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git`
Repository branch	master
Last remote commit	Update translation files `aae0d5319` Weblate authored 13 hours ago
Last commit in Weblate	Translated using Weblate (Finnish) `00afd6960` copperi authored 3 months ago
Weblate repository	`https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/`
File mask	`po/*/master/pages/SourceURL.po`
Translation file	Download `pot/master/pages/SourceURL.pot`
Last change	None
Last author	None

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		83		1,487		11,259
Translated	100%	83	100%	1,487	100%	11,259
Needs editing	0%	0	0%	0	0%	0
Read-only	100%	83	100%	1,487	100%	11,259
Failing checks	3%	3	2%	44	7%	805
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


Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan

Quick numbers

1,487

Hosted words

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

−1%

Hosted words

—

−2%

Hosted strings

—

Translated

—

+100%

Contributors

—

None Resource update fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	The "`pot/master/pages/SourceURL.pot`" file was changed. 5 days ago
None Resource update fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	The "`pot/master/pages/SourceURL.pot`" file was changed. 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English If you were to build this SRPM from a Fedora 34 host (`rpmbuild -bs mysource.spec`), the resulting SRPM would carry `mysource-old.tar.bz2` and `oldpatch.patch`. However, if you then try to use this SRPM to build for Fedora 35, the operation would fail because `mysource-ng.tar.bz2` is not available. English 300 characters edited Current translation Read only If you were to build this SRPM from a Fedora 34 host (`rpmbuild -bs mysource.spec`), the resulting SRPM would carry `mysource-old.tar.bz2` and `oldpatch.patch`. However, if you then try to use this SRPM to build for Fedora 35, the operation would fail because `mysource-ng.tar.bz2` is not available. 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English When building an SRPM, it is critical that all of the sources are present, irrespective of the platform on which the SRPM is generated. For example, the following code does not work (the way you might expect): English 212 characters edited Current translation Read only When building an SRPM, it is critical that all of the sources are present, irrespective of the platform on which the SRPM is generated. For example, the following code does not work (the way you might expect): 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English Sometimes this does not work because the upstream cgi tries to parse the fragment or because you need to login or fill in a form to access the tarball. In these cases, you have to put just the tarball's filename into the `Source:` tag. To make clear where you got the tarball, you should leave notes in comments above the `Source:` line to explain the situation to reviewers and future packagers. For example: English 412 characters edited Current translation Read only Sometimes this does not work because the upstream cgi tries to parse the fragment or because you need to login or fill in a form to access the tarball. In these cases, you have to put just the tarball's filename into the `Source:` tag. To make clear where you got the tarball, you should leave notes in comments above the `Source:` line to explain the situation to reviewers and future packagers. For example: 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English rpm will then use `+%{name}-%{version}.tar.gz+` as the tarball name. If you use `+spectool -g foo.spec+` to download the tarball, it will rename the tarball for you. English 166 characters edited Current translation Read only rpm will then use `+%{name}-%{version}.tar.gz+` as the tarball name. If you use `+spectool -g foo.spec+` to download the tarball, it will rename the tarball for you. 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English When upstream has URLs for the download that do not end with the tarball name rpm will be unable to parse the tarball out of the source URL. One workaround for many cases is to construct a URL where the tarball is listed in a "URL fragment": English 242 characters edited Current translation Read only When upstream has URLs for the download that do not end with the tarball name rpm will be unable to parse the tarball out of the source URL. One workaround for many cases is to construct a URL where the tarball is listed in a "URL fragment": 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English Using `+%{version}+` in the `Source:` makes it easier for you to bump the version of a package, because most of the time you do not need to edit `Source:` when editing the spec file for the new package. English 202 characters edited Current translation Read only Using `+%{version}+` in the `Source:` makes it easier for you to bump the version of a package, because most of the time you do not need to edit `Source:` when editing the spec file for the new package. 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English Bitbucket uses the `+%{shortcommit}+` identifier as part of the archive directory structure; regardless of whether you use git tag or Commit Revision to retrieve it. This is shown in the %prep section example. English 210 characters edited Current translation Read only Bitbucket uses the `+%{shortcommit}+` identifier as part of the archive directory structure; regardless of whether you use git tag or Commit Revision to retrieve it. This is shown in the %prep section example. 4 months ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/SourceURL — English	English Alternately, if you are using a specific revision that is either a pre-release revision or a post-release revision, you must follow the "snapshot" guidelines. They are documented here: xref:Versioning.adoc#_snapshots[Snapshots]. You can substitute `+%{shortcommit}+` for the git hash in `+%{checkout}+` in that section. English 321 characters edited Current translation Read only Alternately, if you are using a specific revision that is either a pre-release revision or a post-release revision, you must follow the "snapshot" guidelines. They are documented here: xref:Versioning.adoc#_snapshots[Snapshots]. You can substitute `+%{shortcommit}+` for the git hash in `+%{checkout}+` in that section. 4 months ago

Browse all translation changes

Quick downloads

83	File in original format as translated in the repository	gettext PO file
83	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-01-02 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2023-01-02 AND state:<=needs-editing`	Add