<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I've just committed the creation of ^/branches/1.6/ru as a copy of
^/branches/1.6/en (minus some English-specific stuff). I've also
granted commit privileges to <a class="moz-txt-link-rfc2396E" href="mailto:zeelax@gmail.com">"zeelax@gmail.com"</a>. Happy translating!<br>
<br>
<div class="moz-cite-prefix">On 06/27/2012 12:17 PM, Maxim Kravets
wrote:<br>
</div>
<blockquote
cite="mid:CAPhRKcmRCoCSv6psh8sMx114kfscxFtQpYZRnNOwTwrC0Ex5gA@mail.gmail.com"
type="cite">Hm...
<div>So, I think it will be good to start with some stable
version. Later it is possible to put some translation from
stable to trunk and vise versa. At the very beginning I've
decided to translate 1.6 version because of it's popularity. As
I can see from repository many of 1.6 parts can go to 1.7 (and
even to trunk now) without or with little modification. So,
there will be no problem with further updates. (If translation
wouldn't be VERY slow ;)<br>
<br>
<div class="gmail_quote">On Wed, Jun 27, 2012 at 9:59 PM, C.
Michael Pilato <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cmpilato@red-bean.com" target="_blank">cmpilato@red-bean.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> If you wish to
translate in trunk, that's certainly fine, but just
understand that trunk is relatively unstable. Today trunk
ostensibly covers Subversion 1.8, but in reality it hasn't
been updated much since the 1.7 updates were completed.
Eventually, though, it will get a flurry of changes to
update it for 1.8. This is why I assumed you'd want to
chase a more stable target.
<div>
<div class="h5"><br>
<br>
<br>
<div>On 06/27/2012 10:28 AM, Maxim Kravets wrote:<br>
</div>
<blockquote type="cite">I've decided to use commenting
original and translate inside XML-files. The same
method was used by previous Russian translators and
well documented in Norwegian version.
<div><br>
</div>
<div>Stable vs. Unstable</div>
<div> If it possible to do translation in trunk,
I'll be very happy with it. If it is not - I'll
start with 1.6 or 1.7 branch.</div>
<div>1.6 version is very popular and is still in use
on many sites. It is default in Debian stable and
testing - it gives more points to 1.6 before 1.7
for beginners. That's why I've started to work
with 1.6. I think it's not so hard to switch to
1.7, for example.</div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">On Tue, Jun 26, 2012 at
9:18 PM, C. Michael Pilato <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:cmpilato@red-bean.com"
target="_blank">cmpilato@red-bean.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">As you noted, the last
Russian translation of the book is very, very
old.<br>
To my knowledge, no one is working on a more
up-to-date translation.<br>
<br>
I see the translation challenge as two-fold.<br>
<br>
First, there's the social/workforce challenge.
Are you willing and able to<br>
tackle this task alone, or do you have some
friends willing to help you?<br>
The COMMITTERS file<br>
(<a moz-do-not-send="true"
href="https://code.google.com/p/svnbook/source/browse/trunk/COMMITTERS"
target="_blank">https://code.google.com/p/svnbook/source/browse/trunk/COMMITTERS</a>)
lists the<br>
names and email addresses of the last known
Russian translators. You might<br>
consider contacting that group to see if any
of them are interested in<br>
helping you with this task.<br>
<br>
Secondly, there's the nuts-and-bolts of the
translation work. The book is<br>
written in DocBook XML, then compiled into the
various formats published on<br>
the website (HTML, PDF, etc.) Different
groups have approached the<br>
translation task in different ways in the
past. Most start by making a copy<br>
of the most recent stable English book
sources, and work against those<br>
(rather than trying to keep up with the moving
target that is "trunk/en").<br>
Some perform the translation inline,
commenting out the original English XML<br>
one paragraph at a time and substituting
matching translated paragraphs.<br>
Others have taken a last direct route,
converting to book sources to PO<br>
format, and using translation tables to
accomplish their task. You and your<br>
team will need to decide which approach works
best for you.<br>
<br>
Please let me know how I can assist you. When
you have a plan of attack<br>
formulated, I can grant you the required
commit access.<br>
<br>
-- Mike<br>
<div>
<div><br>
On 06/26/2012 10:11 AM, Maxim Kravets
wrote:<br>
> Hello!<br>
> I'd like to join russian translation
team or form this team (last russian<br>
> version is very old 1.4 one). What
should I do, read, write, etc?<br>
><br>
</div>
</div>
>
_______________________________________________<br>
> svnbook-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:svnbook-dev@red-bean.com"
target="_blank">svnbook-dev@red-bean.com</a><br>
> <a moz-do-not-send="true"
href="http://www.red-bean.com/mailman/listinfo/svnbook-dev"
target="_blank">http://www.red-bean.com/mailman/listinfo/svnbook-dev</a><br>
<br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
DO NOT INSTALL INTERFACE CARDS WITH POWER APPLIED<br>
</div>
</blockquote>
<br>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
DO NOT INSTALL INTERFACE CARDS WITH POWER APPLIED<br>
</div>
</blockquote>
<br>
<br>
</body>
</html>