Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43022
Return-Path: <danielc@analysisandsolutions.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 61035 invoked from network); 12 Feb 2009 17:00:27 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Feb 2009 17:00:27 -0000
Authentication-Results: pb1.pair.com smtp.mail=danielc@analysisandsolutions.com; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=danielc@analysisandsolutions.com; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.72 cause and error)
X-PHP-List-Original-Sender: danielc@analysisandsolutions.com
X-Host-Fingerprint: 166.84.1.72 mail1.panix.com  
Received: from [166.84.1.72] ([166.84.1.72:55957] helo=mail1.panix.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id DD/96-28940-AA554994 for <internals@lists.php.net>; Thu, 12 Feb 2009 12:00:27 -0500
Received: from panix3.panix.com (panix3.panix.com [166.84.1.3])
	by mail1.panix.com (Postfix) with ESMTP id B2262294AC
	for <internals@lists.php.net>; Thu, 12 Feb 2009 12:00:24 -0500 (EST)
Received: by panix3.panix.com (Postfix, from userid 14662)
	id C45F68FDE0; Thu, 12 Feb 2009 12:00:24 -0500 (EST)
Date: Thu, 12 Feb 2009 12:00:24 -0500
To: PHP Internals List <internals@lists.php.net>
Message-ID: <20090212170022.GA27821@panix.com>
References: <53C9D049-8C10-48F2-8312-C8A81D2B5990@pooteeweet.org> <00a601c98c7b$4ed5a4a0$919f644d@foxbox> <20090212032914.GA5060@panix.com> <006301c98d31$573efef0$919f644d@foxbox>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006301c98d31$573efef0$919f644d@foxbox>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [PHP-DEV] 5.3 todos
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi Steph:

> It's nothing to do with structure. "Everything" makes for a very long 
> file, full stop.

It doesn't matter that the XML file is long.  Each section is broken up 
into a separate page in the manual.

You want the upgrade guide to contain just the things that will cause 
difficulties upgrading.  That's cool.  Put such info in one <section> and 
it will be churned out as one web page in the manual.  Name it clearly.  
Then anyone can easily find and read the info you want in one URI.

The rest of the information can be put into other <section>s so folks who 
want more in depth coverage can have it too.

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409