Translation status

29 Strings 37%
Browse Translate
805 Words 49%
5,570 Characters 49%

Strings status

Strings Words Characters
29 805 5,570
All strings Browse Translate Zen
11 399 2,768
Translated strings Browse Translate Zen
18 406 2,802
Unfinished strings Browse Translate Zen
18 406 2,802
Untranslated strings Browse Translate Zen
2 2 64
Strings with suggestions Browse Translate Zen
16 404 2,738
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 25 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/Debuginfo.po
Translation file Download po/pt_BR/master/pages/Debuginfo.po
Last change Nov. 9, 2024, 6:45 p.m.
Last change made by Weblate Translation Memory
Language Portuguese (Brazil)
Language code pt_BR
Text direction Left to right
Number of speakers 200,247,320
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
10 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 29 805 5,570
Translated 37% 11 49% 399 49% 2,768
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 6% 2 1% 2 1% 64
Untranslated strings 62% 18 50% 406 50% 2,802
Last 12 months Previous

Activity in last 12 months

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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change
DecJanFebMarAprMayJunJulAugSepOctNov

Quick numbers

805
Hosted words
29
Hosted strings
37%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Suggestion added
Resources
Recursos
a month ago
User avatar anonymous

Suggestion added
https://fedoraproject.org/wiki/StackTraces[StackTraces]
https://fedoraproject.org/wiki/StackTraces[Rastreios de pilha]
a year ago
User avatar rffontenelle

Translation added
Flaws that manifest themselves as unexpectedly small `+*.debug+` in the debuginfo package and/or source files missing:
Falhas que se manifestam como inesperadamente pequeno `+*.debug+` no pacote debuginfo e/ou arquivos fonte em falta:
3 years ago
User avatar rffontenelle

Translation added
`+find-debuginfo.sh+` does not process setuid or setgid binaries. There's a https://bugzilla.redhat.com/117858[bug filed against rpmbuild] about that, but until it is fixed in the distros your package is targeted at, make sure that all your binaries do _not_ have the setuid/setgid bits at end of `+%install+`, and restore them in the `+%files+` section using `+%attr(...) /path/to/file+`
`+find-debuginfo.sh+` não processa binários setuid ou setgid. Há um https://bugzilla.redhat.com/117858[bug relatado para o rpmbuild] sobre isso, mas até que seja corrigido nas distros às quais seu pacote se destina, certifique-se de que todos os seus binários _não_ tenham os bits setuid/setgid no final de `+%install+`, e restaure-os na seção `+%files+` usando `+%attr(...) /caminho/para/arquivo+`
3 years ago
User avatar rffontenelle

Translation added
`+find-debuginfo.sh+` processes only files that are executable when it's run; for practical purposes one can assume that happens under the hood after the `+%install+` section. Make sure that all ELF binaries (executables, shared libraries, DSO's) are executable at end of `+%install+`.
`+find-debuginfo.sh+` processa apenas arquivos que são executáveis quando é executado; para fins práticos, pode-se supor que isso aconteça após a seção `+%install+`. Certifique-se de que todos os binários ELF (executáveis, bibliotecas compartilhadas, DSO) são executáveis no final de `+%install+`.
3 years ago
User avatar rffontenelle

Translation added
The package is not marked as `+noarch+`, but does not contain any architecture dependent things (native binaries, architecture dependent paths etc). True `+noarch+` packages contain nothing rpmbuild could strip from them, so it's expected that they're empty if `+BuildArch: noarch+` is missing. If that's the case, make the package `+noarch+`.
O pacote não está marcado como `+noarch+`, mas não contém nenhuma coisa dependente da arquitetura (binários nativos, caminhos dependentes da arquitetura, etc.). Os pacotes `+noarch+` verdadeiros não contêm nada que o rpmbuild possa remover deles, então é esperado que eles estejam vazios se `+BuildArch: noarch+` estiver faltando. Se for esse o caso, faça o pacote `+noarch+`.
3 years ago
User avatar rffontenelle

Translation added
The specfile or the package's build routines explicitly strip symbols out of the binaries. Look for invocations of `+strip+`, `+install -s+`, `+ld -s+`, or `+gcc -s+` etc and get rid of them (or the `+-s+` flags). The method how to do that varies, some examples cases include patching, using `+%configure+` or a `+make+` target that prevents the strip from happening, and/or overriding a strip command like for example `+make install STRIP=/bin/true+`
O specfile ou as rotinas de construção de pacote retiram explicitamente os símbolos dos binários. Procure invocações de `+strip+`, `+install-s +`, `+ld -s+` ou `+gcc -s+` etc e se livre delas (ou das sinalizações `+-s+`). O método de fazer isso varia, alguns exemplos de casos incluem patching, usando `+%configure+` ou um alvo `+make+` que evita que o strip aconteça, e/ou sobrescrevendo um comando strip como por exemplo `+make install STRIP=/bin/true+`
3 years ago
User avatar rffontenelle

Translation added
Useless or incomplete debuginfo packages are often a result of packaging flaws. Typical flaws that often manifest themselves as debuginfo packages containing no files:
Pacotes de debuginfo inúteis ou incompletos geralmente são o resultado de falhas de pacote. Falhas típicas que muitas vezes se manifestam como pacotes debuginfo sem arquivos:
3 years ago
User avatar rffontenelle

Translation added
Useless or incomplete debuginfo packages due to packaging issues
Pacotes de debuginfo inúteis ou incompletos devido a problemas de empacotamento
3 years ago
User avatar rffontenelle

Translation added
A useful debuginfo package contains stripped symbols from ELF binaries (`+*.debug+` in `+/usr/lib/debug+`) as well as the source code related to them (in `+/usr/src/debug+`). The script that generates the packages is `+/usr/lib/rpm/find-debuginfo.sh+`, read it through to get a basic understanding of how they're generated. If your debuginfo package doesn't contain any files, or is missing the sources or the size of the `+*.debug+` files in it is unexpectedly small (typically `+*.debug+` are larger than the corresponding binary it was stripped from), it's likely that there's a flaw in your package. That's not always the case though, read on.
Um pacote debuginfo útil contém símbolos removidos de binários ELF (`+*.debug+` em `+/usr/lib/debug+`), bem como o código-fonte relacionado a eles (em `+/usr/src/debug+`). O script que gera os pacotes é `+/usr/lib/rpm/find-debuginfo.sh+`, leia-o para obter um entendimento básico de como eles são gerados. Se o seu pacote debuginfo não contém nenhum arquivo, ou está faltando as fontes ou o tamanho dos arquivos `+*.debug+` nele é inesperadamente pequeno (normalmente `+*.debug+` são maiores do que o binário correspondente que foi removido de), é provável que haja uma falha em seu pacote. Mas nem sempre é o caso, continue lendo.
3 years ago
Browse all translation changes