On Tue, Apr 15, 2008 at 6:30 AM, Philip Olson <[EMAIL PROTECTED]> wrote: > > > On 14 Apr 2008, at 11:10, Hannes Magnusson wrote: > > > On Mon, Apr 14, 2008 at 7:32 PM, Philip Olson <[EMAIL PROTECTED]> wrote: > > > > > > > > On 13 Apr 2008, at 08:01, Daniel Convissor wrote: > > > > > > > > > > Hi Hannes: > > > > > > > > > > > > > > > > > The idea is to first refactor it with minimum changes so translators > > > > > don't have to retranslate the entire thing again. > > > > > Then after the commit it is easy to make any further adjustments, > but > > > > > yeah. That should be noted. > > > > > > > > > > > > > > > > > > Yeah. Was thinking the same thing. > > > > > > > > Thanks for the the fixes, and of course the whole reworking. > > > > > > > > > > > > > > This is a great change to the docs, except the first page looks odd with > > > "Superglobals" essentially being listed twice. Moving that part to its > own > > > little section seems like a good choice. > > > > > > > You mean splitting the page in two <reference>s, one for superglobals > > and one for "others"? > > > > > > I agree, it feels a bit weird looking at it at first sight, but the > > TOC contains all predefined-variables, not only superglobals... > > > > > I mean have a page that talks about what superglobals are, and it'd include > that superglobals list. So basically this means move > language.variables.superglobals outside of the partintro in variables.xml to > a new page like variables/superglobals.xml even though superglobals isn't a > variable itself. variables.xml would then include it on top of the others.
We would need to create a <part> for it then. > > And as a side effect, we could move information that clutters up each > superglobal page into it... information that although relevant could be in > one location. Like the register_globals and variable scope comments. Sounds like a great idea. I don't have much time to do it until next weekend though, if anyone else has some time, feel free! -Hannes
