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: Italian Translation of the Guix Manual
Date: Sat, 24 Oct 2020 15:17:25 +0200	[thread overview]
Message-ID: <87r1pnhifu.fsf@gmail.com> (raw)
In-Reply-To: <20201024141804.6e2ccaec@hubert-lombard.website> (Hubert Lombard's message of "Sat, 24 Oct 2020 14:18:04 +0200")

Hi, Hubert and Matias,

Welcome you both! :-)

Just some comments as a fellow translator.

Hubert Lombard <contact@hubert-lombard.website> writes:
> I am now subscribed to the Translators mailing list. I have used
> Gtranslator but I think POedit is better.

I use po-mode for Emacs (it comes with gettext), but any tool that
provides some kind of automatic spell-checking helps a lot, at least
with typos.

> 2) I haven't used weblate but just the TP by sending my translation in
> an attachment file 'guix-manual-1.2.0-pre2.fr.po' to
> robot@translationproject.org.
>
> In my case, I have not yet succeeded in passing the robot test (a
> returned email from the robot saying it's not OK yet. I must try again).

What's the message the robot emitting?  I'm aware of these problems
common problems:

* You are not allowed: this has to be solved by the coordinators.
* Problems related to the copyright lines: it checks some patterns and
  you have to follow its guidance.
* Problems related to the header: the empty string is special and it
  contains information about the translation and plural forms.  Same as
  before, following its advice is usually enough.
* Problems related to the contents, for that you can run to check it
  yourself "msgfmt -o /dev/null LANG.po".

I'm not aware of any other kind of error on the robot side, but
sometimes they are cryptic, so don't be afraid to ask.  There could be
problems not detected by the robot too, as msgfmt doesn't check the
texinfo markup, but these usually would be notified directly to you by
the maintainers of the project.

And also, thank you both for stepping up to this task. :-)

Best regards,
Miguel


  reply	other threads:[~2020-10-24 13:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-24 10:14 Italian Translation of the Guix Manual Matias Jose Seco Baccanelli
2020-10-24 10:46 ` Matias Jose Seco Baccanelli
2020-10-24 11:54   ` Julien Lepiller
2020-10-24 12:18   ` Hubert Lombard
2020-10-24 13:17     ` Miguel Ángel Arruga Vivas [this message]
2020-10-24 16:36       ` Hubert Lombard
2020-10-24 17:37         ` Miguel Ángel Arruga Vivas
2020-10-24 19:50           ` 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=87r1pnhifu.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).