Forgot to remove the explicit roman numerals from the expected result:

<ol>
<li><A HREF="funcref.php">Function Reference</A>
  <ol style="list-style-type: upper-roman">
    <li><A HREF="ref.apache.php">Apache-specific Functions</A></li>
    <li><A HREF="ref.apd.php">Advanced PHP debugger</A></li>
    <li><A HREF="ref.array.php">Array Functions</A></li>
    <li><A HREF="ref.aspell.php">Aspell functions
[deprecated]</A></li>
  </ol>
</li>

All the source is in the phpdoc module, good luck fixing DSSSL stylesheets - it's not going to be trivial ....

Can you narrow it down a bit?  I looked in there before and couldn't find the source to that page.

Sorry, but I would have to look for it too - i've generally no idea, but I *think* it might in the standard docbook dsssl sheets, which you'll have to override.

Finding the right place in the DSSSL sheets is already solving half of the problem, then doing some overrides will probably be simple :)

If you can provide a patch, fine, but we won't waste time fixing this issue. IMO, there's nothing wrong with the index.

Sniper:

1) Just because you don't have a problem with it doesn't mean it's not a problem.  It makes the index harder to use.

2) Say it's a minor problem on an individual level.  Suppose it means that people take an extra 2 seconds to find the entry they want.  With thousands of page views a day, this becomes a large problem in the aggregate.

3) The current system is poorly coded.  You don't hard-code ordinals in your PHP scripts, you shouldn't do it in html list markup.  It flies in the face of good web design.  It's not just a readability problem, but an accessibility issue.  PHP of all projects should respect proper HTML coding practices.

Unfortunately, I no longer have time to fix it.  Which probably means it will lay around broken forever because people like sniper think if it works for him, it works for everyone.  While we're at it, let's just remove all the img alt tags from php.net; most people don't need em.

Dear bug reporter. As too many people already indicated, we are open to any patches submitted in this issue. Ranting about why people not have the time to do this (especially instead of looking after the problem) does not solve anything.

I agree, ranting doesn't solve anything.  If you'll reread my comment more carefully, you'll see I am not in fact ranting, but providing my rationale why the bug is important.  I have not asked anyone else to fix it, only pointed out why it deserves to be fixed.  Since I don't have the time to do it myself, the least I can do is outline the reasons others may want to do so in the future.  This is both constructive and desirable.  If the last paragraph is a bit heavy on sarcasm, I felt it necessary to reinforce my point.