public inbox for gentoo-doc-ru@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-doc-ru@lists.gentoo.org
Subject: Re: [gentoo-doc-ru] Joining (was: Test)
Date: Fri, 29 Jun 2007 11:43:08 +0400	[thread overview]
Message-ID: <1183102988.26542.38.camel@localhost> (raw)
In-Reply-To: <20686162.1183098809481.JavaMail.root@elwamui-darkeyed.atl.sa.earthlink.net>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

В Птн, 29/06/2007 в 02:33 -0400, Igor Korot пишет:
> I have couple of questions in regards to the translations.
> 
> I did the Handbook for the SPARC translation.

Здорово. Этот перевод тоже требуется обновить. Оглавление уже на 1.5
года отстаёт от оригинала
- <date>2005-12-19</date>
+ <date>2007-05-07</date>

> 1. It is a usual practice during translation, that the people's name
> is spelled in Cyrillic and then the original English spelling will be
> put in parenthesis. I, as an author, didn't do it AFAIR, however, I thought
> that this will be done by the editor/corrector. Guess I was wrong?
> (It is at least on the FAQ Gentoo/Linux SPARC page).

Всё верно. Такая практика есть, но пока у нас она не введена. Впрочем
возможно сейчас как раз самое время это сделать. Так как это ещё не
сделано, то будет лучше, если вы предложите русское написание, а я потом
просмотрю/отредактирую.

> 2. Also, I just looked at the FAQ Gentoo/Linux SPARC. There are couple of phrases
> that are missing the words. I believe that this happens after the translation.
> If it's possible to check this document and fix those couple sentences, it would be
> great.

Если это так, то это нужно сделать. А вы не напомните где лежит исходный
перевод? В багзилле я его не нашёл.

> 3. Finally, there is no list of which document has a old translation, and which
> don't need to be upgraded. Is there such a page?

В простейшем варианте есть:
http://www.gentoo.org/doc/ru/overview.xml

Но по хорошему нужен trads.

-- 
Peter.

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-29  7:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  6:33 [gentoo-doc-ru] Joining (was: Test) Igor Korot
2007-06-29  7:43 ` Peter Volkov [this message]
2007-06-29 11:23   ` lash the core
2007-06-30  7:39     ` Peter Volkov
2007-06-30  8:24       ` Yuriy Rusinov
2007-06-30  8:47         ` Peter Volkov
2007-07-01 18:42           ` Yuriy Rusinov
2007-07-05 15:22             ` Yuriy Rusinov
2007-07-05 15:32             ` Yuriy Rusinov
2007-07-05 20:51               ` [gentoo-doc-ru] Re: gentoo-x86-quickinstall.xml ... [done] Peter Volkov
2007-07-13 14:14                 ` Yuriy Rusinov
2007-07-17 14:29                   ` Yuriy Rusinov
2007-07-17 13:23                 ` Yuriy Rusinov
2007-07-17 14:11                   ` Peter Volkov
  -- strict thread matches above, loose matches on Subject: below --
2007-06-28 23:00 [gentoo-doc-ru] Joining (was: Test) Igor Korot
2007-06-29  5:52 ` Peter Volkov
2007-06-25 16:03 [gentoo-doc-ru] Test Yuriy Rusinov
2007-06-28 21:34 ` [gentoo-doc-ru] Joining (was: Test) Peter Volkov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1183102988.26542.38.camel@localhost \
    --to=pva@gentoo.org \
    --cc=gentoo-doc-ru@lists.gentoo.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