概览

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

字符串统计数据

字符串百分比 托管的字符串数 字数百分比 托管的单词数 字符百分比 托管的字符数
总数 114 4385 27115
已翻译数 2% 3 1% 3 1% 23
需要编辑 0% 0 0% 0 0% 0
只读 0% 0 0% 0 0% 0
未通过的检查数 0% 0 0% 0 0% 0
带有建议的字符串数 0% 0 0% 0 0% 0
未翻译的字符串数 97% 111 99% 4382 99% 27092
过去 12 个月 上一年

过去 12 个月内的活动

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

快速数字

4385
托管的单词数
114
托管的字符串数
2%
已翻译
0
贡献者
及之前 30 天

过去 30 天的趋势

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

要翻译的新字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

翻译中出现了 10 条要翻译的新字符串。 1 年前
用户头像 无

资源更新

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

文件 documentation/content/zh_TW/articles/problem-reports/_index.po 已更改。 1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

extref:{pr-guidelines}[Problem Report Handling Guidelines]: Valuable insight into how problem reports are handled by the FreeBSD developers.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

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.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

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.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

_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.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

_Environment:_ This should describe, as accurately as possible, the environment in which the problem has been observed. This includes the operating system version, the version of the specific program or file that contains the problem, and any other relevant items such as system configuration, other installed software that influences the problem, etc.—quite simply everything a developer needs to know to reconstruct the environment in which the problem occurs.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

Also note that while including small patches in a PR is generally all right—particularly when they fix the problem described in the PR-large patches and especially new code which may require substantial review before committing should be placed on a web or ftp server, and the URL should be included in the PR instead of the patch. Patches in email tend to get mangled, and the larger the patch, the harder it will be for interested parties to unmangle it. Also, posting a patch on the web allows you to modify it without having to resubmit the entire patch in a followup to the original PR. Finally, large patches simply increase the size of the database, since closed PRs are not actually deleted but instead kept and simply marked as complete.
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

For the base FreeBSD code, you should carefully study the contents of [.filename]#/usr/src/UPDATING# on your system or the latest version at https://cgit.freebsd.org/src/tree/UPDATING[https://cgit.freebsd.org/src/tree/UPDATING]. (This is vital information if you are upgrading from one version to another, especially if you are upgrading to the FreeBSD-CURRENT branch).
 
1 年前
用户头像 无

更新了仓库中的字符串

Documentation / articles/problem-reports/_index — 中文（繁体） (zh_TW)

The extref:{handbook}eresources/[mailing lists, eresources-mail]. If you are not subscribed, use https://www.FreeBSD.org/search/#mailinglists[the searchable archives] on the FreeBSD web site. If the problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something that has been overlooked.
 
1 年前
浏览翻译的所有变化