unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: znavko@disroot.org
To: 35525@debbugs.gnu.org
Subject: bug#35525: guix-manual proposals
Date: Thu, 02 May 2019 08:38:21 +0000	[thread overview]
Message-ID: <bb044392c1977476221899f3c5dddbe4@disroot.org> (raw)
In-Reply-To: <2530df52d53c8ac976ce37ed854b509a@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 4988 bytes --]

I think here the word 'installed' is wrong:

#. type: itemx
#: doc/guix.texi:3011 doc/guix.texi:3024
#, no-wrap
msgid "-A [@var{regexp}]"

#. type: table
#: doc/guix.texi:3015 doc/guix.texi:3028
msgid ""
"List packages currently available in the distribution for this system "
"(@pxref{GNU Distribution}). When @var{regexp} is specified, list only "
"installed packages whose name matches @var{regexp}."

In my own as I see, it does not list installed but all available packages.
May 1, 2019 6:04 PM, znavko@disroot.org (mailto:znavko@disroot.org) wrote:
Also here GuixSD rests instead of Guix System:

#. type: Plain text
#: doc/guix.texi:2650
msgid ""
"If you are not using the Guix System Distribution, consider adding the "
"following lines to your @file{~/.bash_profile} (@pxref{Bash Startup Files,,, "
"bash, The GNU Bash Reference Manual}) so that newly-spawned shells get all "
"the right environment variable definitions:"
And this text is English-specific, lacks its features in another language, words 'force a local build' and 'challenge providers' in Russian has no direct translations:

#. type: Plain text
#: doc/guix.texi:2589 doc/guix.texi:2582
msgid ""
"This foundation allows Guix to support @dfn{transparent binary/source "
"deployment}. When a pre-built binary for a @file{/gnu/store} item is "
"available from an external source---a @dfn{substitute}, Guix just downloads "
"it and unpacks it; otherwise, it builds the package from source, locally "
"(@pxref{Substitutes}). Because build results are usually bit-for-bit "
"reproducible, users do not have to trust servers that provide substitutes: "
"they can force a local build and @emph{challenge} providers (@pxref{Invoking "
"guix challenge})."
msgstr "Эта концепция позволяет Guix поддерживать @dfn{прозрачное внедрение бинарников/исходников}. Когда доступен элемент @file{/gnu/store}, собранный заранее на внешнем источнике, то есть готова @dfn{подстановка}, Guix просто скачивает и распаковывает его. В противном случае он собирает пакет из исходников на локальной машине (@pxref{Substitutes}). Так как результаты сборки обычно воспроизводимы бит-к-биту, пользователи не должны доверять серверам, которые поставляют подстановки --- они могут целенаправленно запросить локальную сборку и @emph{не пользоваться} серверами подстановки (@pxref{Invoking guix challenge})."

force a local build  - Russian equivalent can be only 'purposely ask local build'
challenge providers - in Russian we do not have such idea (as some others equivalents of words too), so I've translated exactly 'do not use substitute servers'

I think this text may be simplified and extended a bit.
May 1, 2019 4:00 PM, znavko@disroot.org (mailto:znavko@disroot.org) wrote:
Hello! Here it is 'many types of fs', but only one mentioned as example:

#. type: Plain text
#: doc/guix.texi:2268
msgid ""
"Alternatively, you may use a swap file. For example, assuming that in the "
"new system you want to use the file @file{/swapfile} as a swap file, you "
"would run@footnote{This example will work for many types of file systems (e."
"g., ext4). However, for copy-on-write file systems (e.g., btrfs), the "
"required steps may be different. For details, see the manual pages for "
"@command{mkswap} and @command{swapon}.}:"
Also, writing configuration step is not so easy when using manual installation. I think, there also should be a message with link to 'Graphical Installation', that you can use graphical installation that will generate configuration you need automatically.

#. type: Plain text
#: doc/guix.texi:2315
msgid ""
"@xref{Using the Configuration System}, for an overview of the configuration "
"file. The example configurations discussed in that section are available "
"under @file{/etc/configuration} in the installation image. Thus, to get "
"started with a system configuration providing a graphical display server (a "
"``desktop'' system), you can run something along these lines:"

And also if another language is ready to use (Spanish), need to say it on:

#. type: Plain text
#: doc/guix.texi:117
msgid ""
"This manual is also available in French (@pxref{Top,,, guix.fr, Manuel de "
"référence de GNU Guix}) and German (@pxref{Top,,, guix.de, Referenzhandbuch "
"zu GNU Guix}). If you would like to translate it in your native language, "
"consider joining the @uref{https://translationproject.org/domain/guix-manual (https://translationproject.org/domain/guix-manual)."
"html, Translation Project}."

[-- Attachment #2: Type: text/html, Size: 5995 bytes --]

  parent reply	other threads:[~2019-05-02  8:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 15:58 bug#35525: guix-manual proposals znavko
2019-05-01 18:03 ` znavko
2019-05-02  8:38 ` znavko [this message]
2019-05-02 15:22   ` Ludovic Courtès
2019-05-02 15:37     ` Danny Milosavljevic
2019-05-02 21:43       ` Ludovic Courtès
2019-05-03  4:51       ` znavko
2019-05-09 19:12       ` znavko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb044392c1977476221899f3c5dddbe4@disroot.org \
    --to=znavko@disroot.org \
    --cc=35525@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).