Hi Al start->run->cmd cd /path/to/your/phpdoc/checkout cvs up php configure.php php scripts/file-entities.php php scripts/missing-entities.php cd .. cvs -d:pserver:[EMAIL PROTECTED]/repository co phd cd phd edit config.php # Fix 'xml_root' to your phpdoc checkout # Remove the die() at the bottom php -derror_reporting=0 build.php # Wait for couple of minutes, three max open the "html" folder and browse to "index.html" double click it
You need to repeat all these steps after each change you do in phpdoc (with the exception of cvs up & cvs co, and edititng config.php). There is no way to avoid that, sorry. I'd recommend you throw all this into a bat file which you can then just double click each time you change something. -Hannes On 9/8/07, Al <[EMAIL PROTECTED]> wrote: > Maybe I could have been clearer. I want to spend my time helping with the > documentation, and not playing with the tools. > > I suspect there are plenty others who would help but don't want to spend their > limited time messing with tools-on-windows, etc. I started down that path and > didn't get far. I ended up finding my own CVS diff and XML editor. Then I > couldn't figure out a simple way to view my end results. > > Al........... > > Al wrote: > > I also wanted to help with documentation for the Imagick extension; but, > > found it very difficult to find good tools for Windows. After fiddling > > for hours with several XML editors and CVS diff programs, I ended up > > with Oxygen XML Editor and TortoiseCVS. > > > > However, I never did find a simple way to view the final result. So, my > > willingness to help is currently on hold. > > > > I could have made a significant documentation contribution during the > > time I spent trying to find suitable tools. > > > > I recommend that you post a good description of the steps needed to > > generate a CVS diff file and view the resultant finished page, using > > Windows tools. > > > > I'm fairly proficient with PHP running on a Linux server; but, I use a > > Windows editor [phpEdit] for coding. > > > > Thanks......... > > > > > > > > Philip Olson wrote: > >> > >> On Sep 6, 2007, at 9:12 PM, Paul Reinheimer wrote: > >> > >>> After intending to get started helping out with the PHP documentation > >>> for a long time, I think i'm finally > >>> going to get there. One quick question as I begin making my own local > >>> copy, is the documentation at > >>> http://doc.php.net/php/dochowto/ up to date? Is there anything else I > >>> should keep in mind? > >> > >> Excellent news :) > >> > >> I'd describe the HOWTO as mostly up to date. But, we're in the middle > >> of splitting this mailing list into three, in the alpha stages of a > >> new build system (PhD (PHP) instead of XSL), finishing up converting > >> all documentation to the new doc style, debating using set/book for > >> all documentation, working on a new OOP DocBook syntax, debating a new > >> method for tracking EN revisions for translators, and a few other > >> things that aren't coming to mind as I type this message like 'The > >> Tool'. So, you will have questions and discover problems but that's > >> good because HOWTO adjustments are needed. > >> > >> Regards, > >> Philip >
