翻译状态

122 字符串 64%
浏览 翻译
4531 单词 54%

字符串状态

122
所有字符串 — 4531 个单词 浏览 翻译 禅模式
79
已翻译字符串 — 2482 个单词 浏览 翻译 禅模式
43
未完成的字符串 — 2049 个单词 浏览 翻译 禅模式
9
未翻译字符串 — 138 个单词 浏览 翻译 禅模式
34
标记为需要编辑的字符串 — 1911 个单词 浏览 翻译 禅模式
12
带有建议的字符串 — 511 个单词 浏览 翻译 禅模式
43
无建议的未完成字符串 — 2049 个单词 浏览 翻译 禅模式
1
带有任何未通过检查的字符串 — 23 个单词 浏览 翻译 禅模式
1
未通过的检查：连续重复的单词 — 23 个单词 浏览 翻译 禅模式
122
没有标签的字符串 — 4531 个单词 浏览 翻译 禅模式

其他部件

部件 已翻译 未完成 未完成的词 未完成的字符数 未翻译 检查 建议 评论
books/developers-handbook/testing/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 0% 87 1758 11224 86 1 0 0
books/arch-handbook/vm/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 0% 37 1766 10736 36 1 0 0
books/porters-handbook/porting-samplem/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 0% 37 483 3366 36 0 0 0
books/porters-handbook/versions/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 5820 21456 244651 5815 0 0 0
books/developers-handbook/sockets/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 271 6808 40793 262 9 0 0
books/developers-handbook/kerneldebug/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 207 5020 33206 200 7 0 0
books/arch-handbook/scsi/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 356 8562 62236 339 12 0 0
books/arch-handbook/isa/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 366 10359 69029 348 18 0 0
books/developers-handbook/ipv6/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 293 6086 41426 286 8 0 0
books/handbook/wayland/_index 此部件链接到 Documentation/articles/bsdl-gpl 仓库。 BSD-2-Clause 1% 146 4183 27966 146 0 0 0
浏览所有部件

概览

项目网站 docs.freebsd.org/en
翻译许可证 BSD 2-Clause "Simplified" License
翻译进程
  • 可以直接翻译。
  • 可以提出翻译建议。
  • 只允许指定的用户贡献。
  • 该翻译使用双语文件。
文件掩码 documentation/content/*/articles/problem-reports/_index.po
翻译文件 下载 documentation/content/pt_BR/articles/problem-reports/_index.po
最后更改 2026年2月22日 16:31
最后作者 None

字符串统计数据

字符串百分比 托管的字符串数 字数百分比 托管的单词数 字符百分比 托管的字符数
总数 122 4531 28164
已翻译数 64% 79 54% 2482 54% 15362
需要编辑 27% 34 42% 1911 42% 11903
只读 0% 0 0% 0 0% 0
未通过的检查数 1% 1 1% 23 1% 196
带有建议的字符串数 9% 12 11% 511 10% 3058
未翻译的字符串数 7% 9 3% 138 3% 899
过去 12 个月 上一年

过去 12 个月内的活动

0 个更改 0 个更改 0 个更改 4 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 0 个更改 63 个更改 0 个更改 0 个更改 0 个更改 0 个更改
五月 六月 七月 八月 九月 十月 十一月 十二月 一月 二月 三月 四月

快速数字

4531
托管的单词数
122
托管的字符串数
64%
已翻译
0
贡献者
及之前 30 天

过去 30 天的趋势

—
托管的单词数
+100%
—
托管的字符串数
+100%
—
已翻译
+64%
—
贡献者
+100%
用户头像 无

要翻译的新字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

翻译中出现了 35 条要翻译的新字符串。 2 个月前
用户头像 无

资源更新

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

文件 documentation/content/pt_BR/articles/problem-reports/_index.po 已更改。 2 个月前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please submit a follow up. The number one reason for a bug not getting fixed is lack of communication with the originator. The easiest way is to use the comment option on the individual Bugzilla PR's web page, which you can reach from the https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla PR search page].
Se alguém solicitar informações adicionais de você, lembrar ou descobrir algo que você não mencionou no relatório inicial, por favor, adicione um novo comentário de acompanhamento. O motivo número um para um bug não ser corrigido é a falta de comunicação com o criador do relatório. A maneira mais fácil de fazer isso é usar a opção de comentário na página da Web individual do PR, que você pode acessar a partir da https://bugs.freebsd.org/bugzilla/query.cgi[página de pesquisa de PRs].
2 个月前
用户头像 无

改变了源字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If someone requests additional information from you, or you remember or discover something you did not mention in the initial report, please submit a follow up. The number one reason for a bug not getting fixed is lack of communication with the originator. The easiest way is to use the comment option on the individual Bugzilla PR's web page, which you can reach from the https://bugs.freebsd.org/bugzilla/query.cgi[Bugzilla PR search page].
2 个月前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If you really do not know where the problem lies (or the explanation does not seem to fit into the ones above), use the `misc` category. Before you do so, you may wish to ask for help first. You may be advised that one of the existing categories really is a better choice.
Se você realmente não sabe onde o problema se encaixa (ou a explicação não parece se encaixar nos itens acima), use a categoria `misc`. Antes de fazer isso, você pode pedir ajuda primeiro na {freebsd-questions}. Você pode ser avisado que com certeza uma das categorias existentes é uma escolha melhor.
2 个月前
用户头像 无

改变了源字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If you really do not know where the problem lies (or the explanation does not seem to fit into the ones above), use the `misc` category. Before you do so, you may wish to ask for help on the {freebsd-questions} first. You may be advised that one of the existing categories really is a better choice.
2 个月前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If you are convinced that the problem will only occur under the processor architecture you are using, select one of the architecture-specific categories: commonly `i386` for Intel-compatible machines in 32-bit mode; `amd64` for AMD machines running in 64-bit mode (this also includes Intel-compatible machines running in EMT64 mode); and less commonly `arm`, `powerpc`, or `riscv64`.
Se estiver convencido de que o problema ocorrerá apenas sob a arquitetura do processador que você está usando, selecione uma das categorias específicas da arquitetura: geralmente `i386` para máquinas compatíveis com Intel 32 bits; `amd64` para máquinas AMD rodando em 64 bits (isto também inclui máquinas compatíveis com Intel rodando em modo EMT64); e menos comumente, as arquiteturas `arm` ou `powerpc`.
2 个月前
用户头像 无

改变了源字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

If you are convinced that the problem will only occur under the processor architecture you are using, select one of the architecture-specific categories: commonly `i386` for Intel-compatible machines in 32-bit mode; `amd64` for AMD machines running in 64-bit mode (this also includes Intel-compatible machines running in EMT64 mode); and less commonly `arm` or, `powerpc`, or `riscv64`.
2 个月前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

The email address you use will become public information and may become available to spammers. You should either have spam handling procedures in place, or use a temporary email account. However, please note that if you do not use a valid email account at all, we will not be able to ask you questions about your submission.
O endereço de e-mail que você usa se tornará publico e poderá se tornar disponível para spammers. Você deve ter procedimentos de tratamento de spam ou usar uma conta de email temporária. No entanto, observe que, se você não usar uma conta de e-mail válida, não poderemos fazer perguntas sobre seu PR.
2 个月前
用户头像 无

改变了源字符串

Documentation / articles/problem-reports/_index — 葡萄牙语（巴西）

The email address you use will become public information and may become available to spammers. You should either have spam handling procedures in place, or use a temporary email account. However, please note that if you do not use a valid email account at all, we will not be able to ask you questions about your PRsubmission.
2 个月前
浏览翻译的所有变化