Re: Pearweb vs xhtml

Hi, I'm not sure that you should be suggesting this since setting up pearweb is not as trivial as one might wish, especially for new comers :) Btw you forgot the pearweb_index package to get things like news, frontpage, group page and such. I suggest that people don't go too trigger happy and spend too much time on this, most of the reports you're talking about are things like & isn't &amp; in urls, name="" being used in forms (bugs.php) we're in Strict mode so it's understandable that we get validation issues and I'm still in the process of refactoring the HTML behind pearweb, accounts.php is one place that I didn't touch, packages.php is another. Now I'm not saying people should not help, by all means do help :-) Just the fact that we are in the process of changing the layout and thus the HTML and CSS behind pearweb, as some people might have noticed, then a patch might get invalid pretty fast since the last pearweb release was only the first in series of layout improvements. Regards Helgi On Jan 15, 2008 7:07 AM, Daniel O'Connor <daniel.oconnor@gmail.com> wrote: > If you're bored and looking for Something Productive or Easy to do, or > a newcomer not at all familiar with PEAR, here's a suggestion. > > There's large chunks of pearweb which aren't quite valid xhtml. These > bugs are generally easy to fix. > > 1. Install https://addons.mozilla.org/en-US/firefox/addon/249 > 2. Set it to SGML mode > 3. Wander around pearweb until you find a page with errors > 4. Do a pear install pearweb and pear > run-scripts pearweb if you > haven't got a local copy already > 5. Alternatively, grab a fresh copy from CVS > 6. Make the changes, check they are OK both visually and validator-y > 7. Provide a diff or post a bug with one or more patches - ie, > http://pear.php.net/bugs/bug.php?id=12910 > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >