Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/problem-reports/_index.po
Translation file Download documentation/content/pt_BR/articles/problem-reports/_index.po
Last change Sept. 9, 2023, 9:39 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 114 4,385 27,115
Translated 91% 104 83% 3,674 83% 22,604
Needs editing 8% 10 16% 711 16% 4,511
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 11% 13 12% 565 12% 3,429
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 6 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 22 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

4,385
Hosted words
114
Hosted strings
91%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

10 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

The "documentation/content/pt_BR/articles/problem-reports/_index.po" file was changed. a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

extref:{pr-guidelines}[Problem Report Handling Guidelines]: Valuable insight into how problem reports are handled by the FreeBSD developers.
extref:{pr-guidelines}[Diretrizes para manuseio de relatórios de problemas] --informações valiosas sobre como os relatórios de problemas são tratados pelos desenvolvedores do FreeBSD.
a year ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

extref:{pr-guidelines}[Problem Report Handling Guidelines]-v: Valuable insight into how problem reports are handled by the FreeBSD developers.
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]: An excellent essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) problem reports.
https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[Como reportar bugs efetivamente] -um excelente ensaio de Simon G. Tatham sobre como compor de forma útil relatórios de problemas (não específicos do FreeBSD).
a year ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]-a: An excellent essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) problem reports.
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IRC/Channels[]. Inform the people in that channel about the problem report and ask for assistance. Be patient and stay in the channel after posting, so that the people from different time zones around the world have a chance to catch up.
Junte-se aos canais relevantes do IRC. Uma lista parcial está aqui: https://wiki.freebsd.org/IrcChannels[]. Informe as pessoas nesse canal sobre o relatório de problemas e peça ajuda. Seja paciente e fique no canal depois de postar, para que as pessoas de diferentes fusos horários ao redor do mundo tenham a chance de responder.
a year ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IrcRC/Channels[]. Inform the people in that channel about the problem report and ask for assistance. Be patient and stay in the channel after posting, so that the people from different time zones around the world have a chance to catch up.
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

_Description:_ A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. It should include the actions you need to take to reproduce the problem. If you know any workaround, include it. It not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem.
_Description:_ Uma descrição completa e precisa do problema que você está enfrentando. Tente evitar especular sobre as causas do problema, a menos que tenha certeza de que você está no caminho certo, pois isso pode induzir o desenvolvedor a fazer suposições incorretas sobre o problema. Ela deve incluir as ações que você precisa executar para reproduzir o problema. Se você conhece alguma solução alternativa, inclua-a. Ela não apenas ajuda outras pessoas com o mesmo problema a contorná-lo, mas também pode ajudar um desenvolvedor a entender a causa do problema.
a year ago
User avatar None

Source string changed

Documentation / articles/problem-reports/_index — Portuguese (Brazil)

__Description:__ A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. It should include the actions you need to take to reproduce the problem. If you know any workaround, include it. It not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem.
a year ago
Browse all translation changes