Russian translation

C. Michael Pilato cmpilato at
Wed Jun 27 10:59:19 CDT 2012

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.

On 06/27/2012 10:28 AM, Maxim Kravets wrote:
> 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.
> Stable vs. Unstable
> 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.
> 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.
> On Tue, Jun 26, 2012 at 9:18 PM, C. Michael Pilato <cmpilato at
> <mailto:cmpilato at>> wrote:
>     As you noted, the last Russian translation of the book is very, very old.
>     To my knowledge, no one is working on a more up-to-date translation.
>     I see the translation challenge as two-fold.
>     First, there's the social/workforce challenge.  Are you willing and
>     able to
>     tackle this task alone, or do you have some friends willing to help you?
>     The COMMITTERS file
>     (
>     lists the
>     names and email addresses of the last known Russian translators.  You
>     might
>     consider contacting that group to see if any of them are interested in
>     helping you with this task.
>     Secondly, there's the nuts-and-bolts of the translation work.  The book is
>     written in DocBook XML, then compiled into the various formats
>     published on
>     the website (HTML, PDF, etc.)  Different groups have approached the
>     translation task in different ways in the past.  Most start by making
>     a copy
>     of the most recent stable English book sources, and work against those
>     (rather than trying to keep up with the moving target that is "trunk/en").
>     Some perform the translation inline, commenting out the original
>     English XML
>     one paragraph at a time and substituting matching translated paragraphs.
>     Others have taken a last direct route, converting to book sources to PO
>     format, and using translation tables to accomplish their task.  You
>     and your
>     team will need to decide which approach works best for you.
>     Please let me know how I can assist you.  When you have a plan of attack
>     formulated, I can grant you the required commit access.
>     -- Mike
>     On 06/26/2012 10:11 AM, Maxim Kravets wrote:
>     > Hello!
>     > I'd like to join russian translation team or form this team (last
>     russian
>     > version is very old 1.4 one). What should I do, read, write, etc?
>     >
>     > _______________________________________________
>     > svnbook-dev mailing list
>     > svnbook-dev at <mailto:svnbook-dev at>
>     >
> -- 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the svnbook-dev mailing list