unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Miguel Ángel Arruga Vivas" <rosen644835@gmail.com>
To: Hubert Lombard <contact@hubert-lombard.website>
Cc: help-guix@gnu.org
Subject: Re: Some (little) problems about contributing to the translation of guix-manual
Date: Tue, 27 Oct 2020 20:42:05 +0100	[thread overview]
Message-ID: <87a6w7o3qq.fsf@gmail.com> (raw)
In-Reply-To: <20201027093823.24f1c25c@hubert-lombard.website> (Hubert Lombard's message of "Tue, 27 Oct 2020 09:38:23 +0100")

Hi, Hubert!

Hubert Lombard <contact@hubert-lombard.website> writes:
> 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).

I supposed you have a clone of the repository, if not you need these two
extra steps (I suppose you don't even have Git in your profile[1], just
a running guix installation):

$ guix environment --ad-hoc git -- git clone https://git.savannah.gnu.org/git/guix.git
$ cd guix

And then the steps from my last mail. :-)

> 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'm sure you'll advance more, just wanted to ensure. :-)

>> 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...

Po-mode is easy... once you get the key bindings, hehehe.  'f' (fuzzy),
'u' (untranslated), RET (edit the current translation, open an Emacs
window) and 'C-c C-c' (accept the translation, close the Emacs window).
Upper case letters for the reverse order... And the rest are
nice-to-have features, like 'V' to execute msgfmt and so on.

Best regards,
Miguel

[1] I personally recommend you to use in your daily work git or any
other VCS: they are very useful tools, help to avoid lots of problems
and aren't really hard to use for an only-forward workflow (save =
commit), which is a real life saver sometimes.


  reply	other threads:[~2020-10-27 19:42 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
2020-10-27 19:42     ` Miguel Ángel Arruga Vivas [this message]
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=87a6w7o3qq.fsf@gmail.com \
    --to=rosen644835@gmail.com \
    --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.
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).