From: Hubert Lombard <contact@hubert-lombard.website>
To: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Some (little) problems about contributing to the translation of guix-manual
Date: Tue, 27 Oct 2020 09:38:23 +0100 [thread overview]
Message-ID: <20201027093823.24f1c25c@hubert-lombard.website> (raw)
In-Reply-To: <873620psxg.fsf@gmail.com>
Le Mon, 26 Oct 2020 22:40:27 +0100,
Miguel Ángel Arruga Vivas <rosen644835@gmail.com> a écrit :
Hi, Miguel!
> Guix compilation is the process taking care of it. To test it, with
> Guix installed and on top the source code from Git, I do the following
> (change 'es' for 'fr', and omit the steps marked as "!" when you have
> already done them once):
>
> $ cp /path/to/my/working/es.po po/doc/guix-manual.es.po
> $ guix environment guix
> ! [env] $ ./bootstrap
> ! [env] $ ./configure --localstatedir=/var
> ! [env] $ make
> [env] $ make info && info -f doc/guix.es.info
>
> You can cancel the "make" step as soon as you see a MAKEINFO line,
> it's needed only to generate some additional files for the manual.
I tried this but it seems that my configuration is not the same as
yours, since I'm not even sure I have the Git source code (My
installation of Guix System was done by the iso image).
[env]$ ./bootstrap
bash: ./bootstrap: Aucun fichier ou dossier de ce type
Well, I'll keep your example for further tests, a good way to start in
guix environment guix.
> It's normal feeling sometimes like that, more when it's the first
> release you're involved---speaking from my own experience---, but you
> also have to look it from the other side: ~90% means that a huge
> portion of the manual text can be read by French speakers! :-)
It's true, Ludo, Simon, Julien and others have done an excellent job,
which I can refer to for a few questions I have.
In addition, I expect to be able to advance a little more in the
translation work before submitting it, the next release 1.2.0 being
planned for early November.
> I don't know how perform poedit and gtranslator at this, but seeing
> the actual .po (as with po-mode with emacs) eases a lot the cleanup
> of fuzzy translations first, because you can spot the difference
> between the old and new msgids---note to writers, please keep the
> paragraphs short:)---and apply just that to the text when it's
> needed, as sometimes the translation didn't have a typo at all.
In the past, with debian or ubuntu, I had tried to use emacs but I
understood absolutely nothing about it. I'm tempted to try again soon,
especially with the po-mode...
> Happy hacking!
Thank you, have some good times too!
--
Hubert
next prev parent reply other threads:[~2020-10-27 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 19:07 Some (little) problems about contributing to the translation of guix-manual Hubert Lombard
2020-10-26 19:16 ` Julien Lepiller
2020-10-26 22:04 ` Hubert Lombard
2020-10-26 21:40 ` Miguel Ángel Arruga Vivas
2020-10-27 8:38 ` Hubert Lombard [this message]
2020-10-27 19:42 ` Miguel Ángel Arruga Vivas
2020-10-27 19:44 ` Miguel Ángel Arruga Vivas
2020-10-28 15:28 ` Hubert Lombard
2020-10-29 18:32 ` Hubert Lombard
2020-10-29 19:00 ` Julien Lepiller
2020-10-29 19:17 ` Julien Lepiller
2020-10-29 21:21 ` Hubert Lombard
2020-10-29 23:42 ` Miguel Ángel Arruga Vivas
2020-10-30 9:18 ` Hubert Lombard
2020-10-30 0:00 ` Julien Lepiller
2020-10-30 8:29 ` 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
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=20201027093823.24f1c25c@hubert-lombard.website \
--to=contact@hubert-lombard.website \
--cc=help-guix@gnu.org \
--cc=rosen644835@gmail.com \
/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.
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).