Conflicting changes in Russian translation

Fri Dec 9 08:17:05 UTC 2011

Hello, Andrei)

>> changeset:   15604:a2edccdfb86a
>> user:        Andrey Somov <py4fun at gmail.com>
>> summary:     i18n-ru: update translation
>
> This is the patch of Andrey Somov sent to mercurial-devel and rejected by
> native Russian speakers.
>...
> How on Earth could it be there?

I can agree that quality of this translation is not the briliant,
however, I've made some corrections to it in my next changeset. In
particular I fixed verbatim translations in color extension. I didn't
want to reject Andrei patches completely, cuz I didn't want him to be
offended and I think he has a right to be mentioned in repository
history. We had a conversation on email and, as far as I can remember,
agreed about that issues. Sure, this strings need to be reviewed, as
well as all my other strings ;). Technical translation is not that
easy.

>> changeset:   15605:04425770d162
>> user:        Alexander Sauta <demosito at gmail.com>
>> summary:     i18n-ru: glossary added, acl translation fixed
>
> First of all, this is a synchronization revision, not indicated as such.

What do you mean by synchronization? This is not a megre, look at the
graph. Maybe you've pulled old changesets from my repo
(demosito/hg-i18n-ru)? I've stripped some revisions from it, one of
them was a merge.

> 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?
>

Say honestly, the first time I wrote glossary I've forgotten about
wiki page. So I've just taken terms from .po file and put them in the
beginning, so it just reflects the current terms as I see them, it's
not an instruction or imperative. I've seen the vocabulary in wiki, it
differs a lot from existing translation, so to make them comply with
each other a lot of work is needed. Moreover, I find some terms
metioned there doubtful. We definitely need to discuss them, but I
didn't see any discussion yet. Maybe I've just missed it.

As I said, I don't want to change the terminology right now, because
that's a lot of work while we have some significant parts of
documentations completely untranslated, mq in particular. I'm working
on it right now and I think that it has higher priority then bringing
terms into the correspodence.

After the translation is finished, it should be reviewed and the terms
maybe would be corrected according to the new vocabulary. BUT, your
vocabulary is also disputable, as well as mine.
I'm strictly against automatic replacements in translation.

I don't read wiki really often and I didn't see changesets and patches
from you, that's why I've concluded that you temporarily stopped
translation and didn't consult with you. Sorry that I was wrong.

So, my point is: I finish translation with current terminology, we
discuss terms proposed on wiki, we bring vocabularies into the
correspondence. This order. No automatic replacements. Everything is
discussaable, though.

The decision about push access and stripping is up to mg, if he thinks
that should be done I don't mind.

--
С уважением,
Александр.

2011/12/8 Andrei Polushin <polushin at gmail.com>:
> 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