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/fa/articles/problem-reports/_index.po
Last change May 30, 2021, 9:16 p.m.
Last author Parsa Samet

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 114 4,385 27,115
Translated 3% 4 1% 5 1% 38
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 96% 110 99% 4,380 99% 27,077
Last 12 months Previous

Activity in last 12 months

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

Quick numbers

4,385
Hosted words
114
Hosted strings
3%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

New strings to translate

Documentation / articles/problem-reports/_index — Persian

10 new strings to translate appeared to the translation. a year ago
User avatar None

Resource update

Documentation / articles/problem-reports/_index — Persian

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

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

extref:{pr-guidelines}[Problem Report Handling Guidelines]: Valuable insight into how problem reports are handled by the FreeBSD developers.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

https://github.com/smileytechguy/reporting-bugs-effectively/blob/master/ENGLISH.md[How to Report Bugs Effectively]: An excellent essay by Simon G. Tatham on composing useful (non-FreeBSD-specific) problem reports.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

Join the relevant IRC channels. A partial listing is here: https://wiki.freebsd.org/IRC/Channels[]. Inform the people in that channel about the problem report and ask for assistance. Be patient and stay in the channel after posting, so that the people from different time zones around the world have a chance to catch up.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

_Description:_ A complete and accurate description of the problem you are experiencing. Try to avoid speculating about the causes of the problem unless you are certain that you are on the right track, as it may mislead a developer into making incorrect assumptions about the problem. It should include the actions you need to take to reproduce the problem. If you know any workaround, include it. It not only helps other people with the same problem work around it, but may also help a developer understand the cause for the problem.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

_Environment:_ This should describe, as accurately as possible, the environment in which the problem has been observed. This includes the operating system version, the version of the specific program or file that contains the problem, and any other relevant items such as system configuration, other installed software that influences the problem, etc.—quite simply everything a developer needs to know to reconstruct the environment in which the problem occurs.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

Also note that while including small patches in a PR is generally all right—particularly when they fix the problem described in the PR-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 PR 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 to the original PR. Finally, large patches simply increase the size of the database, since closed PRs are not actually deleted but instead kept and simply marked as complete.
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

For the base FreeBSD code, you should carefully study the contents of [.filename]#/usr/src/UPDATING# on your system or the latest version at https://cgit.freebsd.org/src/tree/UPDATING[https://cgit.freebsd.org/src/tree/UPDATING]. (This is vital information if you are upgrading from one version to another, especially if you are upgrading to the FreeBSD-CURRENT branch).
 
a year ago
User avatar None

String updated in the repository

Documentation / articles/problem-reports/_index — Persian

The extref:{handbook}eresources/[mailing lists, eresources-mail]. If you are not subscribed, use https://www.FreeBSD.org/search/#mailinglists[the searchable archives] on the FreeBSD web site. If the problem has not been discussed on the lists, you might try posting a message about it and waiting a few days to see if someone can spot something that has been overlooked.
 
a year ago
Browse all translation changes