guix/documentation-manual — Persian @ Fedora Weblate: documentation

Translation

English #-#-#-#-# contributing.pot (guix manual checkout) #-#-#-#-# type: cindex #-#-#-#-# guix.pot (guix manual checkout) #-#-#-#-# type: item

Persian

Needs editing

Skip

	English	Persian	Actions
	LGTM, Looks Good To Me
	review tags
	Reviewed-by, git trailer
	When you deem the proposed change adequate and ready for inclusion within Guix, the following well understood/codified @samp{Reviewed-by:@tie{}Your@tie{}Name<your-email@@example.com>} @footnote{The @samp{Reviewed-by} Git trailer is used by other projects such as Linux, and is understood by third-party tools such as the @samp{b4 am} sub-command, which is able to retrieve the complete submission email thread from a public-inbox instance and add the Git trailers found in replies to the commit patches.} line should be used to sign off as a reviewer, meaning you have reviewed the change and that it looks good to you:
	If the @emph{whole} series (containing multiple commits) looks good to you, reply with @samp{Reviewed-by:@tie{}Your@tie{}Name<your-email@@example.com>} to the cover page if it has one, or to the last patch of the series otherwise, adding another @samp{(for the whole series)} comment on the line below to explicit this fact.
	If you instead want to mark a @emph{single commit} as reviewed (but not the whole series), simply reply with @samp{Reviewed-by:@tie{}Your@tie{}Name<your-email@@example.com>} to that commit message.
	If you are not a committer, you can help others find a @emph{series} you have reviewed more easily by adding a @code{reviewed-looks-good} usertag for the @code{guix} user (@pxref{Debbugs Usertags}).
	update-guix-package, updating the guix package
	It is sometimes desirable to update the @code{guix} package itself (the package defined in @code{(gnu packages package-management)}), for example to make new daemon features available for use by the @code{guix-service-type} service type. In order to simplify this task, the following command can be used:
	make update-guix-package
	The @code{update-guix-package} make target will use the last known @emph{commit} corresponding to @code{HEAD} in your Guix checkout, compute the hash of the Guix sources corresponding to that commit and update the @code{commit}, @code{revision} and hash of the @code{guix} package definition.
	To validate that the updated @code{guix} package hashes are correct and that it can be built successfully, the following command can be run from the directory of your Guix checkout:
	./pre-inst-env guix build guix
	To guard against accidentally updating the @code{guix} package to a commit that others can't refer to, a check is made that the commit used has already been pushed to the Savannah-hosted Guix git repository.
	This check can be disabled, @emph{at your own peril}, by setting the @code{GUIX_ALLOW_ME_TO_USE_PRIVATE_COMMIT} environment variable. When this variable is set, the updated package source is also added to the store. This is used as part of the release process of Guix.
	documentation	مستندات
	Guix is documented using the Texinfo system. If you are not yet familiar with it, we accept contributions for documentation in most formats. That includes plain text, Markdown, Org, etc.
	Documentation contributions can be sent to @email{guix-patches@@gnu.org}. Prepend @samp{[DOCUMENTATION]} to the subject.
	When you need to make more than a simple addition to the documentation, we prefer that you send a proper patch as opposed to sending an email as described above. @xref{Submitting Patches} for more information on how to send your patches.
	To modify the documentation, you need to edit @file{doc/guix.texi} and @file{doc/contributing.texi} (which contains this documentation section), or @file{doc/guix-cookbook.texi} for the cookbook. If you compiled the Guix repository before, you will have many more @file{.texi} files that are translations of these documents. Do not modify them, the translation is managed through @uref{https://translate.fedoraproject.org/projects/guix, Weblate}. @xref{Translating Guix} for more information.
	To render documentation, you must first make sure that you ran @command{./configure} in your source tree (@pxref{Running Guix Before It Is Installed}). After that you can run one of the following commands:
	@samp{make doc/guix.info} to compile the Info manual.
	You can check it with @command{info doc/guix.info}.
	@samp{make doc/guix.html} to compile the HTML version.
	You can point your browser to the relevant file in the @file{doc/guix.html} directory.
	@samp{make doc/guix-cookbook.info} for the cookbook Info manual.
	@samp{make doc/guix-cookbook.html} for the cookbook HTML version.
	translation	ترجمه
	l10n
	i18n
	native language support

Loading…

mskf1383

Suggestion accepted

English

Persian 7 characters edited Current translation Translated

2 years ago

None

Suggestion added

English

Persian 7 characters edited Current translation

3 years ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Persian
No related strings found in the glossary.

String information

Source string description

#-#-#-#-# contributing.pot (guix manual checkout) #-#-#-#-# type: cindex #-#-#-#-# guix.pot (guix manual checkout) #-#-#-#-# type: item

Flags

no-wrap

Source string location

guix-git/doc/contributing.texi:2921 • guix-git/doc/guix.texi:3957 • guix-git/doc/guix.texi:43547 • guix-git/doc/guix.texi:43604

String age

3 years ago

Last updated

2 days ago

Source string age

3 years ago

Translation file

po/doc/guix-manual.fa.po, string 756