> Right. Looks like I'm definitely going to need to get Cygwin setup then > so I can do this properly. I just downloaded a couple of XML editor > tools for Windows to see if they are any good but your docs recommend > against that - using emacs or vi is probably the safest way.
Almost any editor, that's setup properly, will work fine. Just be sure to use unix style line endings and basically tell your editor to NOT MESS WITH WHITESPACE!!! :) I use Editplus or Jedit when editing phpdoc. Jedit has nicer XML tools, but Editplus is quick and fast. Cygwin is a must. > I created a path file before Philip sent this message using my Windows > CVS client for a 3 line addition I tried. Is this anywhere near what I > need to be outputting because if so, I might save myself some time if it > is ok. But if not, I'll get cygwin and everything set up in the morning > (2:30am now). The style of your commit looks good except it looks a little wider then the 78 character limit. Most text editors can be setup to show a long line down the edit area so have one of these at 78 characters so you'll know :) The problem with your commit is the uneeded whitespace change on the top. This part should not be in the commit: - <refentry id="function.localtime"> + <refentry id="function.localtime"> > Is there anyone using native Windows tools to do PHP docs or does > everyone just use Linux? The HOWTO has a Windows section that talks about cygwin and how to setup phpdoc on Windows. Regards, Philip
