Source strings

190 Strings 100%
Browse Translate
5,533 Words 100%
39,216 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
190 5,533 39,216
All strings Browse Translate Zen
190 5,533 39,216
Read-only strings Browse Translate Zen
3 115 784
Strings with any failing checks Browse Translate Zen
1 46 302
Failing check: Unpluralised Browse Translate Zen
2 69 482
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 a233f9785
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Last commit in Weblate Translated using Weblate (Spanish) 76319285b
User avatar vareli authored 4 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Rust.po
Translation file Download pot/master/pages/Rust.pot
Last change April 24, 2024, 10:23 p.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 190 5,533 39,216
Translated 100% 190 100% 5,533 100% 39,216
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 190 100% 5,533 100% 39,216
Failing checks 1% 3 2% 115 1% 784
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

1 change 0 changes 0 changes 178 changes 0 changes 2 changes 4 changes 0 changes 0 changes 0 changes 0 changes 0 changes 4 changes 47 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

5,533
Hosted words
190
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/Rust.pot” file was changed. 6 months ago
User avatar None

String added in the repository
Packages *MUST* ensure that the cargo calls that are internal to the project's build system do not pass flags or arguments that are incompatible with either the default link:#_compiler_flags[compiler flags] or cargo options that are set in the `%cargo_build` macro or configured by `%cargo_prep`.
Packages *MUST* ensure that the cargo calls that are internal to the project's build system do not pass flags or arguments that are incompatible with either the default link:#_compiler_flags[compiler flags] or cargo options that are set in the `%cargo_build` macro or configured by `%cargo_prep`.
6 months ago
User avatar None

String added in the repository
Handling of projects that include both C/C++ and Rust code depends on how building the Rust code is integrated into the project's build system.
Handling of projects that include both C/C++ and Rust code depends on how building the Rust code is integrated into the project's build system.
6 months ago
User avatar None

String added in the repository
Rust projects that are organized as "cargo workspaces" *MUST* be named according to the generic https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Naming Guidelines], i.e. they *MUST NOT* use a `rust-` prefix for the source package name.
Rust projects that are organized as "cargo workspaces" *MUST* be named according to the generic https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Naming Guidelines], i.e. they *MUST NOT* use a `rust-` prefix for the source package name.
6 months ago
User avatar None

String added in the repository
Packages that fall into this category *MUST NOT* ship crate sources in `%{cargo_registry}`, i.e. they cannot ship `-devel` subpackages that contain crate sources or have any subpackages that have virtual provides for `crate(...) = %{version}`.
Packages that fall into this category *MUST NOT* ship crate sources in `%{cargo_registry}`, i.e. they cannot ship `-devel` subpackages that contain crate sources or have any subpackages that have virtual provides for `crate(...) = %{version}`.
6 months ago
User avatar None

String added in the repository
https://pagure.io/fedora-rust/rust2rpm[rust2rpm] has basic support for generating spec files for this type of package by running `rust2rpm path/to/Cargo.toml` in unpacked upstream sources, (where `./Cargo.toml` must be the path to the "workspace root", i.e. the `Cargo.toml` file that contains the `[workspace]` table).
https://pagure.io/fedora-rust/rust2rpm[rust2rpm] has basic support for generating spec files for this type of package by running `rust2rpm path/to/Cargo.toml` in unpacked upstream sources, (where `./Cargo.toml` must be the path to the "workspace root", i.e. the `Cargo.toml` file that contains the `[workspace]` table).
6 months ago
User avatar None

String added in the repository
Rust applications that are "crates" but which are not published on https://crates.io[crates.io] *MUST* be named according to the generic https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Naming Guidelines], i.e. they *MUST NOT* use a `rust-` prefix for the source package name.
Rust applications that are "crates" but which are not published on https://crates.io[crates.io] *MUST* be named according to the generic https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Naming Guidelines], i.e. they *MUST NOT* use a `rust-` prefix for the source package name.
6 months ago
User avatar None

String added in the repository
To prevent the `+%cargo_install+` macro from installing library sources into `%{cargo_registry}`, the `%cargo_install_lib` macro can be defined to `0`. When using rust2rpm with a path to a Cargo.toml file this macro definition is injected automatically.
To prevent the `+%cargo_install+` macro from installing library sources into `%{cargo_registry}`, the `%cargo_install_lib` macro can be defined to `0`. When using rust2rpm with a path to a Cargo.toml file this macro definition is injected automatically.
6 months ago
User avatar None

String added in the repository
Packages that fall into this category *MUST NOT* ship crate sources in `%{cargo_registry}`, i.e. they cannot ship `-devel` subpackages that contain crate sources or have subpackages that have virtual provides for `crate(...) = %{version}`.
Packages that fall into this category *MUST NOT* ship crate sources in `%{cargo_registry}`, i.e. they cannot ship `-devel` subpackages that contain crate sources or have subpackages that have virtual provides for `crate(...) = %{version}`.
6 months ago
User avatar None

String added in the repository
By default, running `cargo test` (i.e. by calling the `%cargo_test` macro), all three kinds of tests are run. They can also be invoked separately (for example, because parts of the test suite or large data files are not included in published sources) by passing through filtering arguments to the underlying `cargo test` command:
By default, running `cargo test` (i.e. by calling the `%cargo_test` macro), all three kinds of tests are run. They can also be invoked separately (for example, because parts of the test suite or large data files are not included in published sources) by passing through filtering arguments to the underlying `cargo test` command:
6 months ago
Browse all translation changes