unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: znavko@disroot.org
To: "Ludovic Courtès" <ludo@gnu.org>, "Pavel Maryanov" <acid@jack.kiev.ua>
Cc: guix-devel@gnu.org
Subject: Re: New Russian PO file for 'guix-manual' (version 1.0.0-pre3)
Date: Sat, 11 May 2019 20:40:52 +0000	[thread overview]
Message-ID: <5bfa997cf956959531952a3d77437aba@disroot.org> (raw)
In-Reply-To: <87y33cvje5.fsf@gnu.org>

I have just sent both:
guix-manual-1.0.1-pre1.ru.po, 
guix-manual-1.0.0-pre3.ru.po

containing exact the same content. If it is right.
As I understood, we go up in version number.

May 11, 2019 8:14 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:

> Hi Pavel and znavko,
> 
> Ludovic Courtès <ludo@gnu.org> skribis:
> 
>> While trying to integration the Russian translation of the manual into
>> Guix, I stumbled upon the following issues:
>> 
>> • The “contributing.texi” string must translate to
>> “contributing.ru.texi”; failing to do that, the build system would
>> include the English version of that file, leading to various
>> failures.
>> 
>> • “dfn{функциональный пакетный менеджер}” should be replaced by
>> “@dfn{функциональный пакетный менеджер}” (with an ‘@’).
>> 
>> • There’s one typo: “@dnf” should be replaced by “@dfn”.
>> 
>> • You translated node names “Using the Operating System” and “System
>> Configuration” by the same string, but Texinfo requires these two
>> strings to be different. Could you change one or the other?
>> 
>> • The translation of node name “Keyboard Layout and Networking and
>> Partitioning” includes commas, I think, which are unfortunately not
>> allowed in this context. Is there a way you could work around that?
> 
> It seems to me that these issues are not addressed in revision
> “2019-05-11 22:05+0200” of the PO file.
> 
> There’s also a missing closing brace for @footnote here:
> 
> @footnote{Флаг @option{-E} команды @command{sudo}) …
> 
> Could you take a look?
> 
> I’d really like us to include the Russian manual in Guix 1.0.1,
> hopefully by the end of next week. Let us know if you need guidance!
> 
> Thanks,
> Ludo’.

  parent reply	other threads:[~2019-05-11 20:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04  9:47 New Russian PO file for 'guix-manual' (version 1.0.0-pre3) Translation Project Robot
2019-05-09 14:22 ` Ludovic Courtès
2019-05-11 20:14   ` Ludovic Courtès
2019-05-11 20:40   ` znavko [this message]
2019-05-11 21:04     ` pelzflorian (Florian Pelz)
2019-05-13  9:01       ` Ludovic Courtès
2019-05-09 14:42 ` znavko
2019-05-09 14:47   ` Pavel Maryanov
2019-05-09 14:51   ` znavko
2019-05-09 15:08     ` Pavel Maryanov
2019-06-06 10:01       ` pelzflorian (Florian Pelz)
2019-06-28  6:14         ` pelzflorian (Florian Pelz)
  -- strict thread matches above, loose matches on Subject: below --
2019-05-09 15:02 Translation Project Robot
2019-05-10 14:17 Translation Project Robot

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=5bfa997cf956959531952a3d77437aba@disroot.org \
    --to=znavko@disroot.org \
    --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).