Re: Documentation linking issues

From: Date: Mon, 13 Dec 2010 17:04:18 +0000
Subject: Re: Documentation linking issues
References: 1 2 3  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-53908@lists.php.net to get a copy of this message
On Sun, Dec 12, 2010 at 4:30 PM, Alexey Borzov <borz_off@cs.msu.su> wrote: > Hi Daniel, > > On 09.12.2010 13:47, Daniel O'Connor wrote: >> >> I'm fairly sure its resolved in trunk/current release of pearweb; just >> needs >> deploying. > > What exactly prevents this deploying? I think Brett is working on it? Maybe we need a "do it all in one go" phing task or shell script to deploy in the future? :-) Till > >> 2010/12/9 Alexey Borzov<borz_off@cs.msu.su> >>> >>> There is a long-standing issue with API documentation for latest release >>> not being linked automatically from packages' "Documentation" section: >>> http://pear.php.net/bugs/bug.php?id=16627 >>> >>> Now, it seems, that cron-job has issues with end-user docs, as well. I >>> recently added docs for HTML_Common2: >>> http://pear.php.net/manual/en/package.html.html-common2.php„Äwº >>> Tа>èð07œ >>> and tried several times to add a link to that as the package's >>> "Documentation URI". It appears OK, but is later removed (!!!) by some >>> automatic (at least one hopes that it's not manual) process. >>> >>> Can someone look into this, please? The most common complaint with PEAR >>> is >>> that it doesn't have docs / has shitty docs. Such handling of existing >>> documentation definitely doesn't help. >>> >>> -- >>> PEAR Development Mailing List (http://pear.php.net/) >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >>> >> > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >

« previous php.pear.dev (#53908) next »