Re: ncurses Documentation
| From: | Hans Zaunere | Date: | Wed, 21 May 2003 14:24:17 +0000 |
| Subject: | Re: ncurses Documentation | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969353714@lists.php.net to get a copy of this message | ||
Philip Olson wrote:
On Tue, 20 May 2003, Gabor Hojtsy wrote:I'm guessing he went in categories outside of /en/ which are indeed empty. Hans, you most likely already found it but you want: phpdoc/en/reference/ncurses/ Yeah, got things located. It seems that while /phpdoc/ isn't completely empty on http://cvs.php.net, after checking it out, much is filled in, so there must be some kind of preprocessing during checkout, as I'm sure everyone knows already :)Hm, http://cvs.php.net/cvs.php/phpdoc does not seem to be empty for me.Check out the whole phpdoc module if you would like to do local editing and testing. Look into the howto for more info, [nearly] everything is explained there.Oops, my apologies - I went for conveinence over accuracy. http://cvs.php.net shows /phpdoc as empty, but when I really checked it out it was generated. I'm well on my way, thanks all.
See the HOWTO and README for more information. I've read the various HOWTOs and README, but find it very tedious to work with the DocBook formats and XML, especially, for instance, if I wanted to send a diff of a particular manual page with my changes. Any tips for editors to use, preferably in Windows since my UNIX environments are strictly for servers. I of course use a regular text editor in Windows, but dealing with these DocBook files is worse than hand editing HTML files :)Lastly, I've been able to render the DocBook XML files into HTML; is there a way to render them into plain text? Thanks, Hans