From: Julien Lepiller <julien@lepiller.eu>
To: Hubert Lombard <contact@hubert-lombard.website>
Cc: help-guix@gnu.org
Subject: Re: Following my first contributions to the translation of the guix-manual
Date: Fri, 4 Dec 2020 19:57:47 +0100 [thread overview]
Message-ID: <20201204195747.15fec9be@tachikoma.lepiller.eu> (raw)
In-Reply-To: <20201204175149.2646575d@hubert-lombard.website>
Le Fri, 4 Dec 2020 17:51:49 +0100,
Hubert Lombard <contact@hubert-lombard.website> a écrit :
> Hi Guix!
>
> Based on the recommendations that you provided me after the first
> contributions to the translation of the guix-manual, I thought that I
> would do some proofreading, track down possible spelling mistakes,
> identify possible offensive expressions, emphasize inclusive writing,
> etc...
>
> Can you confirm that this inspiration is still relevant, about
> guix-manual-1.2.0-pre3.fr.po?
>
> If so, can I simply copy the 'guix-manual-1.2.0-pre3.en.po' current
> (Date: Thu, 03 Dec 2020 20:32:04 +0100) instead of
> 'guix-manual.en.po' into my initially cloned guix git ad-hoc git
> environment?
>
> If not, do I have to do the following manipulation again?
>
> ~/guix$ guix environment guix
> ~/guix [env]$ ./bootstrap
> ~/guix [env]$ ./configure --localstatedir=/var
> ~/guix [env]$ make
> ~/guix [env]$ make info && info -f doc/guix.fr.info
>
> Unless it is not necessary, is the update done automatically? In my
> opinion, the update is done automatically, but if in doubt, I prefer
> to ask you...
>
> Thank you in advance :-)
>
>
If you want to test your changes to guix-manual-*.fr.po, you need to
use make, so intermediate files are updated too:
~/guix$ guix environment guix
~/guix [env]$ ./bootstrap
~/guix [env]$ ./configure --localstatedir=/var
~/guix [env]$ make doc/guix.fr.info
next prev parent reply other threads:[~2020-12-04 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 16:51 Following my first contributions to the translation of the guix-manual Hubert Lombard
2020-12-04 18:57 ` Julien Lepiller [this message]
2020-12-04 20:15 ` Hubert Lombard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201204195747.15fec9be@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=contact@hubert-lombard.website \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.