Re: [PHP-DOC] Preferred doc checkouts
No, and what is worse svn does not fail, it simply ignores any changes in svn:externals. Unless you only ever plan to change docs in a single translation, I don't recommend using the svn:externals modules. However, for those people who are exclusively documenting in 1 language, and never touch the source code they're documenting it is a great system. For everyone else, use a sparse checkout. I put in a small amount of effort last week to make phd work, and as long as you aren't adding in images, it works fine (phd needs a small change to allow it to find images in a sparse checkout, which I have not and will not investigate since I don't care about images :). Greg My experience is different. I'm using TortoiseSVN on Windows XP SP3. I recently made a change to doc-en involving both doc-base and en - see http://svn.php.net/viewvc?view=revisionrevision=286553 Hi, Great - so that means users of TortoiseSVN don't have this issue. The command-line subversion client is the only deficiency if you're using svn:externals. Good to know. Hi, I just made a simple test with my repository and native svn-client Subversion 1.4.4 native svn-client 1.6.3 repository layout: tmp/test1 tmp/test2 tmp/test3 under tmp/test1 , svn:externals ext-t2 http://localhost/svn/tmp/test2 ext-t3 http://localhost/svn/tmp/test3 So, when I make svn co http://localhost/svn/tmp/test1, the whole thing becomes /test1 /test1/ext-t2 /test1/ext-t3 Then I touched 3 files. /test1/t1 /test1/ext-t2/t2 /test1/ext-t3/t3 svn st gives X ext-t2 X ext-t3 ? t1 Performing status on external item at 'ext-t2' ? ext-t2/t2 Performing status on external item at 'ext-t3' ? ext-t3/t3 after svn add and I perform svn ci -m test t1 ext-t2/t2 ext-t3/t3 gives: Adding t2 Adding ext-t2/t2 Adding ext-t3/t3 Commit with no problem and sharing the same commit log. Thus I think svn:externals gives no problem at all (with native svn-client 1.6.x I think) ks
Re: [PHP-DOC] Preferred doc checkouts
KSChan wrote: No, and what is worse svn does not fail, it simply ignores any changes in svn:externals. Unless you only ever plan to change docs in a single translation, I don't recommend using the svn:externals modules. However, for those people who are exclusively documenting in 1 language, and never touch the source code they're documenting it is a great system. For everyone else, use a sparse checkout. I put in a small amount of effort last week to make phd work, and as long as you aren't adding in images, it works fine (phd needs a small change to allow it to find images in a sparse checkout, which I have not and will not investigate since I don't care about images :). Greg My experience is different. I'm using TortoiseSVN on Windows XP SP3. I recently made a change to doc-en involving both doc-base and en - see http://svn.php.net/viewvc?view=revisionrevision=286553 http://svn.php.net/viewvc?view=revisionrevision=286553 Hi, Great - so that means users of TortoiseSVN don't have this issue. The command-line subversion client is the only deficiency if you're using svn:externals. Good to know. Hi, I just made a simple test with my repository and native svn-client Subversion 1.4.4 native svn-client 1.6.3 repository layout: tmp/test1 tmp/test2 tmp/test3 under tmp/test1 , svn:externals ext-t2 http://localhost/svn/tmp/test2 ext-t3 http://localhost/svn/tmp/test3 So, when I make svn co http://localhost/svn/tmp/test1, the whole thing becomes /test1 /test1/ext-t2 /test1/ext-t3 Then I touched 3 files. /test1/t1 /test1/ext-t2/t2 /test1/ext-t3/t3 svn st gives X ext-t2 X ext-t3 ? t1 Performing status on external item at 'ext-t2' ? ext-t2/t2 Performing status on external item at 'ext-t3' ? ext-t3/t3 after svn add and I perform svn ci -m test t1 ext-t2/t2 ext-t3/t3 gives: Adding t2 Adding ext-t2/t2 Adding ext-t3/t3 Commit with no problem and sharing the same commit log. Thus I think svn:externals gives no problem at all (with native svn-client 1.6.x I think) try: svn commit -m doesn't work in the top-level directory. All internal svn:externals are ignored. If you explicitly provide them, it will work. Having done this for a few months, I can say with certainty that 10% or more of the time, one of the directories with changes will be forgotten in the commit. We are, after all, human. Greg
Re: [PHP-DOC] Translating php manual into Persian
Dear Pedram, Thank you for your valuable guidance. I'll start my work and send 'em to you. Regards, Dan On Fri, Jul 31, 2009 at 10:03 AM, pedram salehpoorpedram.salehp...@gmail.com wrote: dear Daniel We better to continue our discussion in the dedicated mailing list of persian translation DOC-FA. But have you worked with any extension of PHP. The main part of PHP documentation is its documentation of extensions. The other parts are relatively translated. If you are able to translate some of documentation of extensions that will be a great help. Regards. Pedram On Fri, Jul 31, 2009 at 2:20 AM, Daniel Rahmanzadeh dan...@gmail.com wrote: Dear Pedram, Please let me know which part of manual should i translate and send to you. Regards, Dan On Thu, Jul 16, 2009 at 12:08 AM, Daniel Rahmanzadehdan...@gmail.com wrote: Hi, Unfortunately I don't have any translations currently about PHP. But i have accomplished something for java that can be found here: http://www.mobilejava.mobi Regards, Dan On Wed, 2009-07-15 at 09:41 +0430, pedram salehpoor wrote: Hi dear daniel The translations are in http://svn.php.net/viewvc/phpdoc/fa/trunk/ and they are going on. There will be some changes in translation files of phpdoc so I have put a hold on committing new translations for now until changes are complete. So if you would like to, please send me some of your translations. Regards. Pedram On Tue, Jul 14, 2009 at 9:15 PM, Daniel Rahmanzadeh dan...@gmail.com wrote: hi there, I'd like to help translate php manual into persian. there's a page for Persian manual but unfortunately no part is translated. I want to know how to start it. Maybe i need a quick start guide or HOWTO. Thanks in advance, Daniel -- Daniel Rahmanzadeh -- Daniel Rahmanzadeh
[PHP-DOC] CVS Account Request: chadm
Contributing to Documentation
