Documentation/books/developers-handbook/policies/

The translation is temporarily closed for contributions due to maintenance, please come back later.

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

Chinese (Simplified) (zh_CN) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Chinese (Traditional) (zh_TW) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Dutch (nl_NL) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

French (fr_FR) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

German (de_DE) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Indonesian BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Italian (it_IT) BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Korean BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Norwegian Bokmål BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Persian BSD-2-Clause	21%	73	1,834	11,356	48	23	0	0

Polish BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Portuguese BSD-2-Clause	0%	93	2,145	13,148	93	0	0	0

Portuguese (Brazil) BSD-2-Clause	1%	92	2,143	13,132	90	2	0	0

Spanish BSD-2-Clause	0%	93	2,145	13,148	91	2	0	0

Turkish (tr_TR) BSD-2-Clause	0%	93	2,145	13,148	93	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		1,488		34,320		210,368
Source		93		2,145		13,148
Translated	7%	114	7%	2,458	7%	14,956
Needs editing	1%	29	3%	1,055	2%	6,123
Read-only	6%	93	6%	2,145	6%	13,148
Failing checks	2%	30	2%	1,023	2%	5,913
Strings with suggestions	0%	0	0%	0	0%	0
Untranslated strings	90%	1,345	89%	30,807	89%	189,289

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

34,320

Hosted words

1,488

Hosted strings

Translated

Contributors

and previous 30 days

Trends of last 30 days

+96%

Hosted words

+100%

Hosted strings

—

+7%

Translated

—

Contributors

+100%

Search

Advanced query builder

Query examples

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

None New alert Documentation / books/developers-handbook/policies/_index	Component seems unused. a month ago
None New strings to translate Documentation / books/developers-handbook/policies/_index — Portuguese	93 new strings to translate appeared to the translation. a month ago
None Resource update Documentation / books/developers-handbook/policies/_index — Portuguese	File `documentation/content/pt/books/developers-handbook/policies/_index.po` was added. a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	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. Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	English It is the duty of the committer making the change to handle library versioning. Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	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. Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	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 Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	English If this is impossible, or the library does not use symbol versioning, bump the library version Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	English If there is an incompatible change, handle it with symbol versioning, maintaining backward ABI compatibility Portuguese 0 characters edited Current translation a month ago
None String updated in the repository Documentation / books/developers-handbook/policies/_index — Portuguese	English It is strongly recommended to add symbol versioning to the new library Portuguese 0 characters edited Current translation a month ago

Browse all component changes