Documentation/articles/problem-reports/_index

Translation status

122	Strings		2%	Browse Translate
4,531	Words		1%	Browse Translate

Strings status

122	All strings — 4,531 words	Browse Translate Zen
3	Translated strings — 3 words	Browse Translate Zen
119	Unfinished strings — 4,528 words	Browse Translate Zen
119	Untranslated strings — 4,528 words	Browse Translate Zen
119	Unfinished strings without suggestions — 4,528 words	Browse Translate Zen
122	Strings without a label — 4,531 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
books/fdp-primer/trademarks/_index BSD-2-Clause	0%	19	344	2,534	19	0	0	0

books/fdp-primer/translations/_index BSD-2-Clause	0%	74	1,419	9,399	74	0	0	0

books/fdp-primer/weblate/_index BSD-2-Clause	0%	158	1,844	13,671	158	0	0	0

books/developers-handbook/kernelbuild/_index BSD-2-Clause	0%	15	224	1,429	15	0	0	0

books/accessibility/preface/_index BSD-2-Clause	0%	23	278	2,140	0	0	0	0

books/accessibility/partii BSD-2-Clause	0%	6	131	1,099	0	0	0	0

books/accessibility/help/_index BSD-2-Clause	0%	15	240	1,672	0	0	0	0

books/accessibility/colors/_index BSD-2-Clause	0%	193	1,864	13,955	0	0	0	0

books/accessibility/book BSD-2-Clause	0%	7	91	689	0	0	0	0

books/accessibility/parti BSD-2-Clause	0%	3	21	137	0	0	0	0

Browse all components

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/ko/articles/problem-reports/_index.po`
Last change	Jan. 12, 2024, 8:10 a.m.
Last author	Kyung-tak, Yoo

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


Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb

Quick numbers

4,531

Hosted words

122

Hosted strings

Translated

Contributors

and previous 30 days

Trends of last 30 days

+3%

Hosted words

+100%

+6%

Hosted strings

+100%

−1%

Translated

+2%

+100%

Contributors

—

None New strings to translate Documentation / articles/problem-reports/_index — Korean	35 new strings to translate appeared to the translation. 13 days ago
None Resource update Documentation / articles/problem-reports/_index — Korean	The "`documentation/content/ko/articles/problem-reports/_index.po`" file was changed. 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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]. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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`. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English The following instructions apply only to submissions via Bugzilla. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English Filling out the Bugzilla Form Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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. Korean 0 characters edited Current translation 13 days ago
None String updated in the repository Documentation / articles/problem-reports/_index — Korean	English 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. Korean 0 characters edited Current translation 13 days ago

Browse all translation changes

Quick downloads

122	File in original format as translated in the repository	gettext PO file
122	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX
119	Unfinished strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2026-02-04 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2026-02-04 AND state:<=needs-editing`	Add