> -----Original Message----- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 31 December 2003 13:11 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DOC] dropping the unix tools > > > >>So we are on making the phpdoc workers life > >>easier... One of the biggest > >>problems is for starters, that many tools are > >>needed. There has been > >>some discussion on dropping the required unix tools, > >>and base the whole > >>build system on PHP. That would mean that Windows > >>people would not need > >>to have cygwin, which is a huge step forward. > > > > Huh? What is so difficult w/ installing Cygwin? AFAICT > > I had not seen people who had try installing that had > > much problem, assuming that they've read the > > documentation for Cygwin beforehand. > > Cygwin takes long to download. The developers put more and more stuff in > there, and we have not been able to compile a list of tools needed by > the PHP documentation, since the simple tools depend on each other, so > those starting to download cygwin only have the option to download it > all (including Apache, PostreSQL, etc.). I used to download my first > cygwin years ago on a dialup connection and I know there are people > still using dialup... > > > I would expect that someone writing code in PHP, that > > can read/understand C, and is thus helping in > > documenting the language would have a simpler time. > > From practice I must point out that most of the people working for the > translations of the documentation know nearly nothing about C, and > mostly use Windows. > > > The main concerns I've seen here (and in PEARDOC) > > where related to the complexity of Docbook, which is > > initially true, as it has a high learning curve if you > > have never used a structured document format (e.g. > > Latex). > > The visual editor idea is aimed at solving the complexity of DocBook for > authors and translators. But currently it is a more critical problem, > that new updates take months to get on to the website (which does > decrease the motivation of translators). > > >>I have only found http://phing.tigris.org/ so far, > >>which is a PHP based > >>ready-to-use build system. It could do the tasks we > >>require, *but* it
> The idea is to make the build system useable (and hopefully unified) for > all projects. Our needs are converging, since the PHP documentation just > needs to accomodate OO docs, long time after the PHP-GTK and PEAR docs > needed that. So the needs are increasingly the same, and we would like > to keep the door open for all contributors to put effort in any PHP > documentation project they like to add their freetime to. This means > keeping the build system simple and keeping the vairous build systems as > close as possible. Amen to that! I've no objection to working toward this, whatsoever, so long as the replacement systems are robust. You mentioned earlier in this mail that livedocs would be moving to cvs.php.net - is there an e.t.a. on that? > > Goba Steph
