From: Julien Lepiller <julien@lepiller.eu>
To: "Pavlo Marianov" <acid@jack.kiev.ua>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Syntax errors in latest guix-manual ru.po
Date: Tue, 07 Apr 2020 08:34:48 -0400 [thread overview]
Message-ID: <AFEF105F-9E23-46D5-A965-0CE82FF0CE88@lepiller.eu> (raw)
In-Reply-To: <CAHt-HhnFGkHhCjPfV2e+R=SN-QiTDbiW_7_4sovbHYXDAt85AA@mail.gmail.com>
Le 7 avril 2020 06:03:18 GMT-04:00, Pavlo Marianov <acid@jack.kiev.ua> a écrit :
>Looks like errors like 'reference to nonexistent node' will remain
>until all text will be translated.
>
>Other errors I could not find in the source PO-file. Maybe coordinates
>are
>wrong. For example reference 'guix.texi:946' is missing in the
>https://translationproject.org/PO-files/ru/guix-manual-1.1.0-pre1.ru.po
>
>вт, 7 квіт. 2020 о 12:44 Ludovic Courtès <ludo@gnu.org> пише:
>
>> Hi Pavlo,
>>
>> Pavlo Marianov <acid@jack.kiev.ua> skribis:
>>
>> > I uploaded a new PO-file.
>> > Hope it fixes that error.
>>
>> Thanks for the quick reply! There’s a few issues left:
>>
>> --8<---------------cut here---------------start------------->8---
>> ./doc/guix.ru.texi:946: warning: accent command `@,' must not be
>followed
>> by whitespace
>> doc/contributing.ru.texi:365: @url missing closing brace
>> Wide character in warn at /home/ludo/.guix-profile/bin/makeinfo line
>632.
>> ./doc/guix.ru.texi:28262: @pxref reference to nonexistent node
>`Системы
>> сборки)'
>> Wide character in warn at /home/ludo/.guix-profile/bin/makeinfo line
>632.
>> doc/contributing.ru.texi:105: @xref reference to nonexistent node
>`Запуск
>> guix environment'
>> Wide character in warn at /home/ludo/.guix-profile/bin/makeinfo line
>632.
>> doc/contributing.ru.texi:915: @pxref reference to nonexistent node
>> `Отправка набора патчей'
>> make[2]: *** [Makefile:4236: doc/guix.ru.info] Error 1
>> --8<---------------cut here---------------end--------------->8---
>>
>> Does that make sense to you?
>>
>> Thanks,
>> Ludo’.
>>
During my translation I also found it was difficult to keep nodes in sync. That's why I added some code to the Makefile so that it will automatically translate node names in the file. Translate nodes, but keep references to them in English. The makefile will find your translation and automatically replace @ref etc.
next prev parent reply other threads:[~2020-04-07 12:35 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 [this message]
2020-04-07 20:17 ` Ludovic Courtès
2020-04-07 23:39 ` Julien Lepiller
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=AFEF105F-9E23-46D5-A965-0CE82FF0CE88@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).