Take a look on GitHub repository.
For example, main_EN.tex for English, main_RU.tex for Russian, etc.
So just find filename_EN.tex file you want to translate, copy to filename_XX.tex (where XX is your language)
and replace English text by yours.
No special TeX/LaTeX knowledge is needed.
Then just send it to me.
Or if you familiar with git and github, add your file to source tree and create pull request.
How to find directories with *_EN.tex files?
Look here.
Please submit your work as early as possible: other translators will be aware of the piece of work already done.
Korean, Chinese and Persian languages are reserved by publishers.
Do not focus on typography, fonts, nice-looking visual candy and other fancy TeX features. The most important thing here is a text, so this is first priority.
Also, you may ignore all TeX errors, I'll fix them later.
I deeply convinced that technical literature should should be terse and formal. Imagine you've got some reference book on your bookshelf. You need it once a month, to get Pi exact value from it or something like that. Perfect reference is a book where you'll see "Pi=3.14159..." and nothing else. Informal or verbose language in technical books annoys you each time you looking up for the information you need.
On the other hand, terminology may be informal, just as typical modern IT bloggers use. Don't hesitate to use English words in your language if this is norm in IT speech of your language and there are no good translation yet. For example, Russian IT language is a mix of Russian and English words, and this is current language norm (at least in 2016), so I use this language in the book.
Spanish: \ES{}
Brazilian Portuguese: \PTBR{}
Polish: \PL{}
Italian: \ITA{}
German: \DE{}
Thai: \THA{}
Dutch: \NL{}
There are also \ESph{}, \PTBRph{}, \PLph{}, \DEph{} and \ITAph{} placeholder macros in *.tex files, where the translated text must be.
To check your results, just run make RE4B-ES, make RE4B-PTBR, make RE4B-PL, make RE4B-IT, make RE4B-DE.
You'll see almost blank pages with only listings and screenshots, without any text, but your text will be present.
It's very frustrating to find out that a piece of text you have just translated has been translated by someone else at the very same time. For a simple coordination, you can leave a text file named like "Note_to_German_translators.txt" in the directory you're currently working with contents like
I'm going to translate this part soon.
-- [email protected], [email protected], DD/MM/YYYY.
For example. You can jokingly call it "mutex". Feel free to add any other notes for rest of translators.
If you are not familiar with git/github, just send me fragment you translated, so I could add it as early as possible.
Whenever I add/modify some part of text, I also add "\ac{TBT}" (To Be Translated) mark to other translations, into a place where translation should be updated. And/or, I add commentary at the first line of each translated file, which should be updated.
There was a time (before Jan-2019) when I wrote this:
listings TeX package sometimes goes crazy if it encounters UTF-8 character(s) and digit(s) in one line: [stack overflow discussion](http://tex.stackexchange.com/questions/24528/having-problems-with-listings-and-utf-8-can-it-be-fixed).
So it must be escaped, and in this project, "paragraph" symbol is used: `§`.
(Almost) all Cyrillic comments in listings are escaped, [for example](https://github.com/DennisYurichev/RE-for-beginners/blob/9bcd72d176b1f86aa31dda21007740f83ae90484/patterns/02_stack/04_alloca/2_1_gcc_intel_O3_RU.asm#L9).
How to escape French diacritic symbols, [for example](https://github.com/DennisYurichev/RE-for-beginners/blob/c4ee7d6abc3022fd60167d22f47cf100bc4be425/patterns/03_printf/ARM/ARM8_O0_FR.lst#L12).
Do not worry about misplacing them or not placing at all, I'll fix it by myself.
For those, who interested, § symbol is in fact switches you into TeX mode, and you can write anything here as in .tex files, like `\IT{italic}`, etc.
This is why single `$` symbol cannot be used inside escaped line.
In Jan-2019 I learnt about "texcl=true" and now comments in listings are in TeX mode. But, several characters needs to be escaped, as in usual TeX code: $, #, %, , etc. To be on safe side, use \verb|comment|. But if a comment itself contains pipe symbol ("|"), you can do this: \verb!comment!.
However, \verb|long_string| is unbreakable and thus is not suitable for long strings... In this case, I enclose smaller parts of comment in listing...
"§" symbol is still to be used in code, but not in comments. This is a case of translated variable names, like: https://github.com/DennisYurichev/RE-for-beginners/blob/master/patterns/09_loops/simple/loops_1_RU.c https://github.com/DennisYurichev/RE-for-beginners/blob/master/patterns/09_loops/simple/loops_3_RU.c
Do not hesitate to contact me if you have any questions: dennis(a)yurichev.com