unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>, "Pavlo Marianov" <acid@jack.kiev.ua>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Syntax errors in latest guix-manual ru.po
Date: Tue, 07 Apr 2020 19:39:55 -0400	[thread overview]
Message-ID: <D2D8284A-D61F-4315-8C75-32D5F6435711@lepiller.eu> (raw)
In-Reply-To: <877dyr82z6.fsf@gnu.org>

Le 7 avril 2020 16:17:49 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi,
>
>Pavlo Marianov <acid@jack.kiev.ua> skribis:
>
>>> doc/contributing.ru.texi:365: @url missing closing brace
>
>This one is:
>
>  CI-системой @url{@value{SUBSTITUTE-SERVER}.
>                                           ^
>Julien, do we need to do anything for the non-existent node names or is
>there “something” that’ll take care of it?  (Somehow I can never
>remember how that works.)
>
>Ludo’.

You translate the menu and @node. You don't need to translate references like @ref, @xref or @pxref. The xref_command takes care of that (guix self) uses its own parser too. For references outside the guix manual, I use the English name too because they were not translated. It's ok to translate URLs to point to translated resources.

  reply	other threads:[~2020-04-07 23:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 10:00 Syntax errors in latest guix-manual ru.po Ludovic Courtès
2020-04-06 11:55 ` Pavlo Marianov
2020-04-07  9:44   ` Ludovic Courtès
2020-04-07 10:03     ` Pavlo Marianov
2020-04-07 12:34       ` Julien Lepiller
2020-04-07 20:17       ` Ludovic Courtès
2020-04-07 23:39         ` Julien Lepiller [this message]
2020-04-08  7:38           ` Pavlo Marianov
2020-04-08 10:35             ` Ludovic Courtès
2020-04-08 10:50               ` Pavlo Marianov
2020-04-09  9:37                 ` Ludovic Courtès
2020-04-09  9:57                   ` Pavlo Marianov
2020-04-09 11:53                   ` Julien Lepiller

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=D2D8284A-D61F-4315-8C75-32D5F6435711@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=acid@jack.kiev.ua \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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