Re: Serbian translation of the PHP manual

Дана Thursday 24 March 2011 16:21:08 написасте: > And you have commit rights so feel free to commit, and welcome to the PHP > documentation team :) Great! and thank you :) I have already committed some changes and now everything seems OK. I do, however, have a few tiny questions ;) I see I will be hunted down relentlessly if I translate frontpage authors to Serbian; however, Serbian orthography actually strongly recommends that all foreign names are transliterated in Serbian texts (the same way that f.e. Russian names are always transliterated in English texts). While of course it would be an overkill to transliterate all the contributors, in my opinion at least those on the main page should be transliterated - any solutions? Somewhat similarly, I see that Creative Commons license should not be translated, which is understandable. However, may I instead replace it with the Serbian version of the CC-BY license? This is the same license that is translated to Serbian and adjusted to Serbian legal system, published and endorsed by the Creative Commons. You may see http://creativecommons.org/licenses/by/3.0/rs/deed.en . I believe that using the localized license(s) speeds up adoption of free content, and using this license for this manual would do the same. Is it OK if I add new paragraphs, pages and files to the documentation that are relevant for the translation? For example, in en/appendices/userlandnaming.xml I discuss variable naming in Serbian. Similarly, I would like to make a glossary of terms I used so that future translators could use the same terms throughout the translation (Serbian doesn't really have standardized computer terminology). Finally, when I translate an image, could I add .xcf (GIMP internal file format) files to the English original for other translators to use? Unrelated to the above, how much should I work on the English original? I already encountered a few typos while translating. But, for example, while translating wrapper documentation, I noticed that entries in the Wrapper Summary are very repetitive. Should I introduce new entities so that future translators (and me) would have less work to do?