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/zh_TW/articles/problem-reports/_index.po
Last change Oct. 9, 2022, 4:15 a.m.
Last author Gasol Wu

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 122 4,531 28,164
Translated 2% 3 1% 3 1% 23
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 0% 0 0% 0 0% 0
Untranslated strings 97% 119 99% 4,528 99% 28,141
Last 12 months Previous

Activity in last 12 months

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 0 changes 0 changes 0 changes 0 changes 0 changes 37 changes
Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Quick numbers

4,531
Hosted words
122
Hosted strings
2%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+3%
Hosted words
+100%
+6%
Hosted strings
+100%
−1%
Translated
+2%
+100%
Contributors
—
User avatar None

New strings to translate

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

35 new strings to translate appeared to the translation. a week ago
User avatar None

Resource update

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

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

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

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].
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

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.
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

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`.
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

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.
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

The following instructions apply only to submissions via Bugzilla.
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

Filling out the Bugzilla Form
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

You should also take note that unless you explicitly specify otherwise in your request or in the patch itself, any patches you submit will be assumed to be licensed under the same terms as the original file you modified.
 
a week ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Chinese (Traditional) (zh_TW)

Also note that while including small patches in a Github Pull Request is generally all right—particularly when they fix the problem described in the Pull Request-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 Pull Request 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. Finally, large patches simply increase the size of the database, since closed reports are not actually deleted but instead kept and simply marked as complete.
 
a week ago
Browse all translation changes