Re: cvs: phpdoc /en/reference/mysqli book.xml overview.xml

From: Date: Wed, 29 Oct 2008 09:58:13 +0000
Subject: Re: cvs: phpdoc /en/reference/mysqli book.xml overview.xml
References: 1 2 3  Groups: php.doc.cvs 
Request: Send a blank email to doc-cvs+get-2330@lists.php.net to get a copy of this message
On Wed, Oct 29, 2008 at 10:17, Anthony Bedford <Anthony.Bedford@sun.com> wrote: > I wrote the overview from scratch, but yes you are right, I did develop this > in the MySQL doc system first (a bit easier to work with), Suggestions on how we can improve our process would be greatly appreciated. >> Such a evil thing to do, using colwidth="N*".. which is nearly the >> only thing in the CALS specs we haven't implemented yet, making the >> table (see >> http://docs.php.net/manual/en/mysqli.overview.php) look >> b0rked :D > > Oops. :) Is there any way I can see how this will actually look on the live > site before I commit? Obviously I'm generating HTML to check output, but it > doesn't have quite the same format as the live site. That exact case shouldn't be specific to the phpweb output, its simply missing support in PhD (dealing with N* colwidths).. You shouldn't have to worry about these things, but if you do notice weird/wrong behavior in our systems a heads up (bug report) would be appreciated. To view the phpweb docs locally is a PITA, you'll need phpweb checkout and fetch some generated files from your nearest mirror (or generate them yourself by checking out the php-master-web code and run scripts/update-backend.. after you have removed things like the token check and remove some of the authentication stuff...). The easiest way I guess is to go via rsync and exclude the distribution and manual directory, run phd -d .manual.xml -t phpweb and move the generated php folder into phpweb/manual/en/. You'll have to do minor magic setup of the virtualhost, see http://php.net/mirroring It almost isn't worth it... -Hannes

« previous php.doc.cvs (#2330) next »