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/committers-guide/_index.po
Translation file Download documentation/content/fa/articles/committers-guide/_index.po
Last change May 21, 2023, 6:27 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,091 28,196 178,860
Translated 1% 3 1% 3 1% 15
Needs editing 1% 2 1% 5 1% 39
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 1% 1 1% 9
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 99% 1,086 99% 28,188 99% 178,806
Last 12 months Previous

Activity in last 12 months

0 changes 269 changes 0 changes 60 changes 0 changes 3 changes 2 changes 3 changes 2 changes 0 changes 0 changes 18 changes 4 changes 0 changes 0 changes 0 changes 0 changes 0 changes 23 changes 6 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

28,196
Hosted words
1,091
Hosted strings
1%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+1%
—
Contributors
—
User avatar None

New strings to translate

Documentation / articles/committers-guide/_index — Persian

4 new strings to translate appeared to the translation. 3 months ago
User avatar None

Resource update

Documentation / articles/committers-guide/_index — Persian

The "documentation/content/fa/articles/committers-guide/_index.po" file was changed. 3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

FreeBSD builds with both Clang and GCC. The project does this in a careful and controlled way to maximize benefits from this extra work, while keeping the extra work to a minimum. Supporting both Clang and GCC improves the flexibility our users have. These compilers have different strengths and weaknesses, and supporting both allows users to pick the best one for their needs. Clang and GCC support similar dialects of C and C++, necessitating a relatively small amount of conditional code. The project gains increased code coverage and improves the code quality by using features from both compilers. The project is able to build in more user environments and leverage more CI environments by supporting this range, increasing convenience for users and giving them more tools to test with. By carefully constraining the range of versions supported to modern versions of these compilers, the project avoids unduly increasing the testing matrix. Older and obscure compilers, as well as older dialects of the languages, have extremely limited support that allow user programs to build with them, but without constraining the base system to being built with them. The exact balance continues to evolve to ensure the benefits of extra work remain greater than the burdens it imposes. The project used to support really old Intel compilers or old GCC versions, but we traded supporting those obsolete compilers for a carefully selected range of modern compilers. This section documents where we use different compilers, and the expectations around that.
 
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

Sometimes there are merge conflicts. That is OK. Do not panic. Instead, handle them the same as any other merge conflicts. To keep it simple, I will just describe a common issue that may arise. A pointer to a complete treatment can be found at the end of this section.
 
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

Tag signatures can be verified with `git verify-tag <tag name>`, or `git tag -v <tag name>`.
 
3 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

shows me moving the working tree to the `main` branch (a816...) and then updating from upstream (to 5ef0...). In this case, bad would be HEAD (or 5ef0bd68b515) and good would be a8163e165c5b. As you can see from the output, HEAD@{1} also often works, but isn't foolproof if you have done other things to your Git tree after updating, but before you discover the need to bisect.
 
3 months ago
User avatar None

New strings to translate

Documentation / articles/committers-guide/_index — Persian

16 new strings to translate appeared to the translation. 7 months ago
User avatar None

Resource update

Documentation / articles/committers-guide/_index — Persian

The "documentation/content/fa/articles/committers-guide/_index.po" file was changed. 7 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

If for some reason using extref:{porters-handbook}testing[poudriere, testing-poudriere] to test the new port is not possible, the bare minimum of testing includes this sequence:
 
7 months ago
User avatar None

String updated in the repository

Documentation / articles/committers-guide/_index — Persian

The extref:{porters-handbook}testing[Porters Handbook's Testing Chapter] contains more detailed instructions. See the extref:{porters-handbook}testing[Portclippy / Portfmt, testing-portclippy] and the extref:{porters-handbook}testing[poudriere, testing-poudriere] sections.
 
7 months ago
Browse all translation changes