Translation status

190 Strings 0%
Browse Translate
5,533 Words 0%
39,216 Characters 0%

Strings status

Strings Words Characters
190 5,533 39,216
All strings Browse Translate Zen
190 5,533 39,216
Unfinished strings Browse Translate Zen
190 5,533 39,216
Untranslated strings Browse Translate Zen
3 7 51
Strings with suggestions Browse Translate Zen
187 5,526 39,165
Unfinished strings without suggestions Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary fedora-docs-l10n/packaging-guidelines CC-BY-SA-3.0 0 0 0 0 0 0 0
master/pages/MPI CC-BY-SA-3.0 0% 60 1,527 10,897 60 0 1 0
master/pages/D CC-BY-SA-3.0 0% 33 420 3,067 33 0 2 0
master/pages/Golang_advanced CC-BY-SA-3.0 0% 43 835 12,879 43 0 0 0
master/pages/Tcl CC-BY-SA-3.0 0% 42 1,152 7,990 42 0 3 0
master/pages/LibreOfficeExtensions CC-BY-SA-3.0 0% 10 246 1,774 10 0 0 0
master/pages/FontsPolicy CC-BY-SA-3.0 1% 430 5,985 42,455 430 0 6 0
master/pages/Ada CC-BY-SA-3.0 0% 36 1,008 7,110 6 0 1 0
master/pages/WeakDependencies CC-BY-SA-3.0 0% 32 670 4,436 31 1 4 0
master/pages/GAP CC-BY-SA-3.0 1% 54 933 6,804 54 0 2 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 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 aa7b6c16f
♪ I'm a bot, bot, bot ♪ authored 3 hours ago
Last commit in Weblate Update translation files 722a074b5
Weblate authored a year ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Rust.po
Translation file Download po/pt_BR/master/pages/Rust.po
Last change April 24, 2024, 10:23 p.m.
Last author None
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 190 5,533 39,216
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 1% 3 1% 7 1% 51
Untranslated strings 100% 190 100% 5,533 100% 39,216
Last 12 months Previous

Activity in last 12 months

0 changes 5 changes 0 changes 0 changes 0 changes 2 changes 6 changes 0 changes 15 changes 0 changes 0 changes 0 changes 2 changes 0 changes 0 changes 178 changes 0 changes 2 changes 6 changes 0 changes 0 changes 0 changes 0 changes 1 change
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

5,533
Hosted words
190
Hosted strings
0%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
The "po/pt_BR/master/pages/Rust.po" file was changed. yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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`.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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}`.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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).
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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}`.
 
yesterday
User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Rust
  3. Portuguese (Brazil)
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:
 
yesterday
Browse all translation changes