Conflicting changes in Russian translation

[Andrei Polushin]

09.12.2011 15:17, Alexander Sauta wrote:
>> 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 [...]

I guess you could reject wrong _chunks_ of the patch, so no one is offended.


> [...] Sure, this strings need to be reviewed, as
> well as all my other strings ;). Technical translation is not that
> easy.

Yes, and reading a badly translated technical text is merely annoying.


>>> 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 merge, [...]

This is a `msgmerge', as described at
http://mercurial.selenic.com/wiki/TranslatingMercurial#Updating_a_Translation -
it says the revision should have a commit message of the form "i18n-xx:
synchronized with NODE".
I'm unable to determine a NODE to which you've synchronized, and that
doesn't help me to coordinate with you.


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

As from July 2011, I'm offering my Perl scripting skills for this.


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

I've explicitly CC'ed you [1]. How could that be?

[1] http://selenic.com/pipermail/mercurial-devel/2011-November/035733.html

That message contain a word `discussion', the following message contains a
discussion due date, and the follow-up messages is the discussion.


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

I wish you to continue your work, but you shouldn't block others on
improving the translation. These issues are sort of unrelated.


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

Why, if they'll make the translation just better?


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

Not this order, sorry.

You should be able to do your work _in coordination_ with the community. For
the coordination, you should be able to discuss the vocabulary _first_, then
follow the coordinated terms in your translation.

BTW, it looks strange that you've kept a silence for half a year, now
expressing an eager desire to give orders.


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

FWIW, I still appreciate your previous work.


-- 
Andrei Polushin