A team of translators of PHP documentation needs help.
Upd : For the impatient: step by step instructions for creating translations .
Good afternoon!
As many know, for a long time now on php.net there is no Russian version of the PHP documentation. This does not mean that the translation work was discontinued, and the results of this work were gone.
The fact is that translation of documentation is a voluntary matter, and there are not many volunteers, let's say. One or two people tried to keep the translation afloat, but all the same, in the end, the documentation was outdated and rather misled those who used it than helped in mastering the language. Somewhere in 2008, there was no one left in the translation team, then the documentation was so outdated that the assembly process (which included synchronization with the English version) broke down and the Russian manual disappeared from the official site until “better times.” The slow and painful revival of documentation began in October 2010, but since then it has been gaining momentum every day.
At the moment, only a few people participate in the doc-ru team. Most of the current translation for a long time was done by Alexei Shein aka conf , he is currently the coordinator of translations. The “order” is monitored by the core PHP developer Anton Dovgal aka tony2001, who has already abandoned the translation of the documentation. There are also others - incoming, outgoing and disappearing translators, but also making a valuable contribution to our common cause.
Now, when you imagine a team of translators, I’ll give some statistics at the moment:
')
Is not it sad? The next step of our article has become a logical step.
You can argue for a long time if you need a Russian PHP manual. Let's put these disputes aside - let everyone decide for himself what is better to use. Almost all of us are adults. But I know for sure that beginner web developers should better recommend a manual than books with incomprehensible and outdated, and often terrible examples. Another argument for writing the manual can be considered ... patriotism. There is a wonderful example - the French PHP manual. This manual is translated by 99%, with 80% translated by one single person - Yannick Torrès (yannick). Why is our multimillion country worse?)
We, the doc-ru team, ask everyone who is interested to join the translation of the PHP documentation.
PHP 5.4 will be released very soon (3 alpha will be released on Thursday, August 4) with new features such as:
Let's take a look at the description of all these features in our own language for the first time?
Of course, the main purpose of participating in a team of translators should be a strong desire to expand and improve the Russian translation of PHP documentation in every way, as well as a pleasant sense of satisfaction and accomplishment. But besides this, there are also some nice buns, such as:
1) Postal address with the domain php .net. From there, you can set up a redirect to your primary email address, for example, to Gmail.
2) Open-source license (with free updates for a year) for the excellent Jetbrains PhpStorm (only for working on open-source projects ).
3) Public recognition. Your names will always be on the special page of the documentation, even after you stop working on it, see the section “Translators” on the page docs.php.net/manual/ru/preface.php .
Attention:
All of the above is available only to those who have made a significant contribution to the translation or editorial editing of documentation and have received a svn-account. Because There is a lot of freeloaders to have a beautiful address, and so on. You must first prove that you can do serious work, namely creating patches.
There are three main strategies for revolting Russian documentation from the ashes:
I do not think that we can impose one of these options on you, but if you want to quickly see the return of the Russian manual, we suggest that you take the first two.
If every habrayuser involved in this blog translates at least one article, then it will already be a huge leap for our team.
For those who are not good in English, but strong in Russian and, of course, in PHP and want to help us, there is also a huge and important work - rechecking articles after translators.
Next, I will describe the technical side of the translation, for those we are interested in.
You can ask questions or participate in the discussion of translation in our mailing list doc-ru@lists.php.net. To subscribe, you need to send an empty letter to
Also, if need be, you can subscribe to the main PHP documentation mailing list : phpdoc@lists.php.net (in English).
You can track the general status of the translation documentation at http://doc.php.net/trantools/revcheck_extended_ru.html .
The documentation itself is constantly (4 times a day) laid out on one of the PHP servers: http://docs.php.net/manual/ru/ .
Of the translation agreements, there is currently a modest file , but our plans are to create a strong and active translation community whose collective mind will create a strong and good basis for translation in the future. Therefore, if you are in doubt about how to translate a particular offer, do not fully understand the meaning, etc. - feel free to ask on the mailing list. It’s better to think together than write something wrong :).
How exactly to translate can be found in our article on the new translation tool edit.php.net and in the material " PHP Documentation HOWTO " (English).
Thank you all for your attention and we are waiting for you in our team!
Article prepared: conf , irker . If you find a typo or error in the article, please write me a private message about them.
Russian PHP documentation
Good afternoon!
As many know, for a long time now on php.net there is no Russian version of the PHP documentation. This does not mean that the translation work was discontinued, and the results of this work were gone.
The fact is that translation of documentation is a voluntary matter, and there are not many volunteers, let's say. One or two people tried to keep the translation afloat, but all the same, in the end, the documentation was outdated and rather misled those who used it than helped in mastering the language. Somewhere in 2008, there was no one left in the translation team, then the documentation was so outdated that the assembly process (which included synchronization with the English version) broke down and the Russian manual disappeared from the official site until “better times.” The slow and painful revival of documentation began in October 2010, but since then it has been gaining momentum every day.
PHP Translation Team
At the moment, only a few people participate in the doc-ru team. Most of the current translation for a long time was done by Alexei Shein aka conf , he is currently the coordinator of translations. The “order” is monitored by the core PHP developer Anton Dovgal aka tony2001, who has already abandoned the translation of the documentation. There are also others - incoming, outgoing and disappearing translators, but also making a valuable contribution to our common cause.
Now, when you imagine a team of translators, I’ll give some statistics at the moment:
- The number of translated files ~ 700
- Number of obsolete translated files ~ 200
- The number of untranslated files ~ 8900
')
Is not it sad? The next step of our article has become a logical step.
Appeal to users and all sympathizers
You can argue for a long time if you need a Russian PHP manual. Let's put these disputes aside - let everyone decide for himself what is better to use. Almost all of us are adults. But I know for sure that beginner web developers should better recommend a manual than books with incomprehensible and outdated, and often terrible examples. Another argument for writing the manual can be considered ... patriotism. There is a wonderful example - the French PHP manual. This manual is translated by 99%, with 80% translated by one single person - Yannick Torrès (yannick). Why is our multimillion country worse?)
We, the doc-ru team, ask everyone who is interested to join the translation of the PHP documentation.
PHP 5.4 will be released very soon (3 alpha will be released on Thursday, August 4) with new features such as:
- traits;
- embedded web server;
- short syntax for creating arrays (
array('one', 'foo' => 'test') === ['one', 'foo' => 'test'];); - dereferencing an array from the result of a function call (
foo()[1]); - calling an object's method as an array (
$arr = array('Class', 'method'); $arr();); - and much, much more .
Let's take a look at the description of all these features in our own language for the first time?
Additional motivation
Of course, the main purpose of participating in a team of translators should be a strong desire to expand and improve the Russian translation of PHP documentation in every way, as well as a pleasant sense of satisfaction and accomplishment. But besides this, there are also some nice buns, such as:
1) Postal address with the domain php .net. From there, you can set up a redirect to your primary email address, for example, to Gmail.
2) Open-source license (with free updates for a year) for the excellent Jetbrains PhpStorm (only for working on open-source projects ).
3) Public recognition. Your names will always be on the special page of the documentation, even after you stop working on it, see the section “Translators” on the page docs.php.net/manual/ru/preface.php .
Attention:
All of the above is available only to those who have made a significant contribution to the translation or editorial editing of documentation and have received a svn-account. Because There is a lot of freeloaders to have a beautiful address, and so on. You must first prove that you can do serious work, namely creating patches.
Strategy
There are three main strategies for revolting Russian documentation from the ashes:
- Update all the already translated files and then continue to translate the rest.
- Translate the basics of the language and only then translate the documentation for the modules, etc.
- Translate everything that is more like and close to your heart.
I do not think that we can impose one of these options on you, but if you want to quickly see the return of the Russian manual, we suggest that you take the first two.
If every habrayuser involved in this blog translates at least one article, then it will already be a huge leap for our team.
For those who are not good in English, but strong in Russian and, of course, in PHP and want to help us, there is also a huge and important work - rechecking articles after translators.
Next, I will describe the technical side of the translation, for those we are interested in.
Resources and instructions
You can ask questions or participate in the discussion of translation in our mailing list doc-ru@lists.php.net. To subscribe, you need to send an empty letter to
doc-ru-subscribe@lists.php.net (to unsubscribe, respectively, to doc-ru-unsubscribe@lists.php.net ).Also, if need be, you can subscribe to the main PHP documentation mailing list : phpdoc@lists.php.net (in English).
You can track the general status of the translation documentation at http://doc.php.net/trantools/revcheck_extended_ru.html .
The documentation itself is constantly (4 times a day) laid out on one of the PHP servers: http://docs.php.net/manual/ru/ .
Of the translation agreements, there is currently a modest file , but our plans are to create a strong and active translation community whose collective mind will create a strong and good basis for translation in the future. Therefore, if you are in doubt about how to translate a particular offer, do not fully understand the meaning, etc. - feel free to ask on the mailing list. It’s better to think together than write something wrong :).
How exactly to translate can be found in our article on the new translation tool edit.php.net and in the material " PHP Documentation HOWTO " (English).
Afterword
Thank you all for your attention and we are waiting for you in our team!
Article prepared: conf , irker . If you find a typo or error in the article, please write me a private message about them.
Source: https://habr.com/ru/post/125348/
All Articles