Conflicting changes in Russian translation

[Andrei Polushin]

Martin, I propose to strip these revisions from hg-i18n. See details below.


08.12.2011 19:00, Mercurial Commits wrote:
> 3 outgoing changesets in hg-i18n:

(Note: quoting previous message in chronological order of commits)

> http://bitbucket.org/mg/hg-i18n/changeset/a2edccdfb86a
> changeset:   15604:a2edccdfb86a
> user:        Andrey Somov <py4fun at gmail.com>
> date:        Thu Nov 10 22:05:02 2011 +0100
> summary:     i18n-ru: update translation

This is the patch of Andrey Somov sent to mercurial-devel and rejected by
native Russian speakers. Most of its translations are simply wrong (e.g.
translations of verbatim text from within doc comment of color extension),
others require severe editing.

How on Earth could it be there?


> http://bitbucket.org/mg/hg-i18n/changeset/04425770d162
> changeset:   15605:04425770d162
> user:        Alexander Sauta <demosito at gmail.com>
> date:        Fri Nov 18 21:19:05 2011 +0300
> summary:     i18n-ru: glossary added, acl translation fixed

First of all, this is a synchronization revision, not indicated as such.

Moreover, this commit is an attempt to establish an alternate vocabulary in
a .po file.

Alexander, did you see a vocabulary at
http://mercurial.selenic.com/wiki/TranslatingMercurialIntoRussian ?
I presume you did, because its announcement follows the patch of Andrey
Somov you've just pushed. If so, why didn't you participate in the
vocabulary discussion on mercurial-devel?

Alexander, do you prefer to continue with your own vocabulary instead?


> http://bitbucket.org/mg/hg-i18n/changeset/912525f7b8e2
> changeset:   15606:912525f7b8e2
> tag:         tip
> user:        Alexander Sauta <demosito at gmail.com>
> date:        Thu Dec 08 00:05:24 2011 +0300
> summary:     i18n-ru: eol, fetch, color, LargeFiles, gpg, keywords translated

This one is a real translation, but it uses a non-discussed vocabulary, thus
it looks like an attempt to interfere with my current efforts on editing the
translation using our new vocabulary.

That's why I propose to strip these revisions completely and put Russian
translation on hold, until we'll be able to coordinate.

In addition, I announce that I'm performing a semi-automatic editing of the
Russian translation according to new vocabulary.

It could take me a month (December 2011).

Alas, it could take much more if something like this would frustrate me.

-- 
Andrei Polushin