Re: [PHP-DOC] Request for review : ldap_control_paged_result ldap_control_paged_result_response
Hello Philip, On Tue, 20 Mar 2012 20:58:09 -0700, Philip Olson phi...@roshambo.org wrote: I'm not all that familiar with LDAP but know the documentation there is lacking. It'd be most wonderful if you chose to champion those docs. Or, simply offering these patches is perfectly fine too. I sent this patch as the co-dev of those functions but I can take a look to some missing docs. I'm going to assume you want to get involved with the PHP documentation, in which you'd want someone to nitpick by finding every tiny little problem with your patches. I can do that! :) So here goes: Thanks for your feedback, I'll fix my patch soon. Regards, -- Jean-Sébastien H. au-fil-du.net
Re: [PHP-DOC] Syncing your translation with the EN build
On Wed, Mar 21, 2012 at 21:30, Klaus Silveira klaussilve...@php.net wrote: Dear maintainers, I have a tricky question that you guys might be able to help by sharing your experiences. The pt_BR build of the PHP documentation is very obsolete. There are a lot of files that don't exist anymore in the EN build and lot's of files from the current EN missing from the pt_BR build. Not only the references are obsolete, the actual files are missing or should be removed. Is there a quick way of syncing the two again, so we can start working on a more stable and updated pt_BR build? The configuration scripts will automatically fallback to English files when files are missing in the translations - as long as the container files aren't overwritten (i.e. the files that contain the entity references). I would start with either making sure the container files are up2pdate, or removing them (files like book.xml which contain entity includes of classes and functions). That will ensure the fallback will kick in, and the English translation will be included when the translation is missing some files. If you have a lot of files in the translation that no longer exists in the english version, then those files have most probably be refactored into smaller chunks. They could also simply have been renamed (which we really really try to avoid exactly to prevent this sort of issues), but I would recommend you track down when the file was removed and why - just so you won't have to translate the entire thing again for no reason. I'm not a translator, so I can't say what other translations do.. hopefully someone can explain what they do in these cases :] -Hannes
Re: [PHP-DOC] SVN Account Request: khela
On Sat, Mar 10, 2012 at 19:09, Alessandro Nuzzo khe...@gmail.com wrote: Contibuiting to translating php.docs in Italian Can someone verify this request? -Hannes
Re: [PHP-DOC] Syncing your translation with the EN build
Hi Klaus, In addition with Hannes say, perhaps you can start using the online editor ( https://edit.php.net). This tools make a lot of things in the background who will help you on common tasks with translation. Best, Yannick 2012/3/22 Hannes Magnusson hannes.magnus...@gmail.com On Wed, Mar 21, 2012 at 21:30, Klaus Silveira klaussilve...@php.net wrote: Dear maintainers, I have a tricky question that you guys might be able to help by sharing your experiences. The pt_BR build of the PHP documentation is very obsolete. There are a lot of files that don't exist anymore in the EN build and lot's of files from the current EN missing from the pt_BR build. Not only the references are obsolete, the actual files are missing or should be removed. Is there a quick way of syncing the two again, so we can start working on a more stable and updated pt_BR build? The configuration scripts will automatically fallback to English files when files are missing in the translations - as long as the container files aren't overwritten (i.e. the files that contain the entity references). I would start with either making sure the container files are up2pdate, or removing them (files like book.xml which contain entity includes of classes and functions). That will ensure the fallback will kick in, and the English translation will be included when the translation is missing some files. If you have a lot of files in the translation that no longer exists in the english version, then those files have most probably be refactored into smaller chunks. They could also simply have been renamed (which we really really try to avoid exactly to prevent this sort of issues), but I would recommend you track down when the file was removed and why - just so you won't have to translate the entire thing again for no reason. I'm not a translator, so I can't say what other translations do.. hopefully someone can explain what they do in these cases :] -Hannes
[PHP-DOC] Patch files: isCopyrighted and isProtectionEnabled
Hello and thanks for reading this message. I created two patch files, because I think there information incorrect on the label refpurpose in the files: isCopyrighted and isProtectionEnabled, in the directory reference/ktaglib/ audioproperties. Attached the two patch files, if any of you want to review it. A greeting and thanks. patch-1332468139.patch Description: Binary data patch-1332468164.patch Description: Binary data
