unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Hubert Lombard <contact@hubert-lombard.website>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: Some (little) problems about contributing to the translation of guix-manual
Date: Thu, 29 Oct 2020 22:21:22 +0100	[thread overview]
Message-ID: <20201029222122.7c464a44@hubert-lombard.website> (raw)
In-Reply-To: <90692B35-81AA-4C5A-AA02-77ADB68E54CB@lepiller.eu>

Hi, Julien and help-guix :-)

Le Thu, 29 Oct 2020 15:17:44 -0400,
Julien Lepiller <julien@lepiller.eu> a écrit :

> Actually, I just had a look at the file you created. There are
> multiple issues with it. Remember that the text is in texinfo format,
> so anything of the form @command{content} is a texinfo command. If
> you translate it, it might have unexpected effects (not able to
> compile, …).
> 
> For instance, I see you translated @value{VERSION} (which is a
> command that dereferences a texinfo variable and replaces it with its
> value, eg. 1.2.0) by @valeur{VERSION}. @valeur is not a valid texinfo
> command :)
> 
> There's a command that has been completely removed and all that's
> left is a lonely {--gc-keep-derivations}. And similar stuff :)
> 
> Additionnaly, (and I should have told you earlier), you should not
> translate the @pxref, @xref and @ref commands yourself, as this is
> done automatically afterwards. This ensures that we don't get in
> trouble if a title is changed (or its translation), because texinfo
> is really picky when it comes to making links.
> 
> Right now, I see two different capitalisations of the French title,
> and none of tgem is the same as the actual title, which is an error.

Thank you for your attention, I'm not at all surprised that it gave such a result.
When I was translating, I asked myself the same questions about all
these subtleties and I tried to solve them as I went along (while
Poedit told me that there were no errors in the translation :-) 
 
> If you're not working on that file right now, I can take care of
> fixing these issues and give you control over the file again tomorrow
> morning. 

It's very nice of you, I'd like you to take care of it if you can. Tomorrow morning, I will study carefully what you will have done.
Really, thank you Julien!

I also read your answers on git clone, I'll take good note of them too
;)

Well, I'm going to go rest a little bit!


> Thanks!

Thanks to you!

Kind regards

Hubert



-- 


  reply	other threads:[~2020-10-29 21:21 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
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 [this message]
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=20201029222122.7c464a44@hubert-lombard.website \
    --to=contact@hubert-lombard.website \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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).