Re: cvs: phpdoc / Makefile.in

On Fri, 16 May 2003, Gabor Hojtsy wrote: > First of all these are not significant problems, so you can go to your > weekend and when you'll be back, and have time to test all things out, > then the changes can be committed. It would not be good to commit > untested changes now when the fist xsl builds are going on. That makes sense. I can submit something on Monday. > > 1) We don't reset the Example numbering for each function name. (I > > fixed this.) > > We agreed that this is not a problem, maybe even an advantage. One can > refer to a specific example number (but it will change with every build, > so this should not be relied on). As far as I can see it is not our main > focus to make the XSL output exactly the same as the DSSSL one. Anytime > we can improve things, we'd better to that. This was considered to be > sort of an improvement. Hum... I don't think I really agree that this is sort of an improvement. If you refer to Example 2 for array_merge() and it's switched to Example 3, then it's a little confusing, but you're still on the page physical HTML page. But, if Example 143 moves from array_merge() to array_merge_recursive() then that's really confusing. Since we update the docs on a frequent basis that means all the Examples won't necessarily stay constant for more than a few days. That kind of defeats the purpose of letting people refer to them easily. IMHO. > > 2) Navigation links aren't always correctly generated. See, for > > example, the sidebar of features.safe-mode.functions.php. The DSSSL > > page has a link to "Security and Safe Mode," while the XSL > > generated page does not. I believe this has to do with us putting > > multiple chunks in a single document and our query to generate the > > "toc" array, but I haven't had time to look at this in more detail. > > Well, this is probably a problem and would be nice to fix. I will take a look into this and see what I can do. -adam -- adam@trachtenberg.com