Documentation/books/developers-handbook/policies/

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English BSD-2-Clause		0	0	0	0	1	0	0

Chinese (Simplified) (zh_CN) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Chinese (Traditional) (zh_TW) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Dutch (nl_NL) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

French BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

French (fr_FR) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

German (de_DE) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Greek BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Indonesian BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Italian (it_IT) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Korean BSD-2-Clause	1%	50	1,154	7,742	50	0	0	0

Norwegian Bokmål BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Persian BSD-2-Clause	29%	36	916	6,351	28	5	0	0

Polish BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Portuguese BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Portuguese (Brazil) BSD-2-Clause	1%	50	1,157	7,761	50	0	0	0

Spanish BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Turkish (tr_TR) BSD-2-Clause	0%	51	1,159	7,777	51	0	0	0

Please sign in to see the alerts.

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/*/books/developers-handbook/policies/_index.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		918		20,862		139,986
Source		51		1,159		7,777
Translated	7%	68	6%	1,409	6%	9,254
Needs editing	1%	8	1%	341	1%	2,050
Read-only	5%	51	5%	1,159	5%	7,777
Failing checks	1%	6	1%	301	1%	1,781
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	91%	842	91%	19,112	91%	128,682

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

20,862

Hosted words

918

Hosted strings

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+100%

—

Hosted strings

+100%

—

Translated

+7%

—

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2025-03-29 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:>=2025-03-29 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Committed changes Documentation / books/developers-handbook/policies/_index — French	Committed changes 3 months ago
None New strings to translate Documentation / books/developers-handbook/policies/_index — French	51 new strings to translate appeared to the translation. 3 months ago
None Resource update Documentation / books/developers-handbook/policies/_index — French	File `documentation/content/fr/books/developers-handbook/policies/_index.po` was added. 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English The ELF dynamic linker matches library names literally. There is a popular convention where library version is written in the form `libexample.so.x.y`, where x is the major version, and y is minor. Common practice is to set the library' soname (`DT_SONAME` ELF tag) to `libexample.so.x`, and set up symlinks `libexample.so.x->libexample.so.x.y`, `libexample.so->libexample.so.x` on library installation for the latest minor version y. Then, since the static linker searches for `libexample.so` when the `-lexample` command line option is specified, objects linked with libexample get a dependency on the right library. Almost all popular build systems use this scheme automatically. French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English It is the duty of the committer making the change to handle library versioning. French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English For instance, added functions and bugfixes not changing the interfaces are fine, while deleted functions, changed function call syntax, etc. should either provide backward-compat symbols, or will force the major version number to change. French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English Before even considering bumping library version for symbol-versioned library, consult with Release Engineering team, providing reasons why the change is so important that it should be allowed despite breaking the ABI French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English If this is impossible, or the library does not use symbol versioning, bump the library version French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English If there is an incompatible change, handle it with symbol versioning, maintaining backward ABI compatibility French 0 characters edited Current translation 3 months ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — French	English It is strongly recommended to add symbol versioning to the new library French 0 characters edited Current translation 3 months ago

Browse all component changes