Re: Serbian translation of the PHP manual
| From: | Nikola Smolenski | Date: | Sat, 02 Apr 2011 04:18:04 +0000 |
| Subject: | Re: Serbian translation of the PHP manual | ||
| References: | 1 2 3 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969382594@lists.php.net to get a copy of this message | ||
Дана Thursday 31 March 2011 18:20:53 Philip Olson написа:
> On Mar 30, 2011, at 1:00 PM, Nikola Smolenski wrote:
> > 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.
>
> Another good question. Should we do this for every language? I wonder if
> all of our language codes line up with CC, which would make using an entity
> here easy.
CC does have such licenses for a number of countries (see
http://wiki.creativecommons.org/CC_Affiliate_Network
) though a question
remains what license to use for languages spoken in multiple countries
(Spanish). I don't see how an entity would help here?
> > 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.
>
> Adding text may cause problems in determining if the translation is
> up-to-date. How about adding additional text like this to an rs-specific
> entity, and including it?
If everything else fails, that could do. I see that the online editor
complained about errors when I did that - do such errors affect the build or
could they be ignored?
> > 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?
>
> Yes. The general rule is to add an entity if text is repeated 3 or more
> times. Also, please don't mix whitespace changes with textual changes. But
> agreed, the less work for translators the better.
I made a frequency analysis of the manual and there are 1023 texts that are
repeated 3 or more times :) Perhaps this should be done gradually...