Comments?
Good idea! Unfortunately I don't have enough time and enthusiasm to
implement this currently, so other volunteers are welcome :-).
In my eyes, extension categorization is not so visible in the appendix
so the described problems are not so big as if it would be directly in
the contents but it's still worth implementing it this way IMHO.
Jakub Vrana
Implemented part of the solution: moved out language specific content
from extensions.xml to extensions.ent, so that it does not need to be
translated anymore. Next step is to autogenerate the file, with some
flags like:
<!-- Flags: purpose.basic.text, state.experimental, membership.pecl -->
Or maybe with searching for &warn.experimental;, we can automate
experimental tagging, and &pecl.moved; is one that can be used to detect
PECL extensions...
Goba
I'll work on this. News later today ;)
Nuno
