Hi,
This has been discussed many times with many dead ends. Here are some see also threads:
http://marc.theaimsgroup.com/?l=phpdoc&m=100894842011360 http://marc.theaimsgroup.com/?l=phpdoc&m=101051061316162 http://marc.theaimsgroup.com/?l=phpdoc&m=105601918607181
One structure that was proposed is as follows. Not sure why
it wasn't implemented, let's wait until Goba comes back from vacation to answer this :)
<note role="seealso"> <simplelist> <member><function>print</function></member> <member><function>echo</function></member> </simplelist> </note>
I can't find any mention of &listendand; on the lists, and from RFC/2003_meeting_findings.txt is this:
"About see also lists, the attendees of the meeting concluded in that the current see also writing scheme is fine, and there is no need to modify it."
In summary: Not sure what happened with this idea. It seemed
like everyone wanted the structured see also (no commas, no
and...) as to let XSL/Livedocs deal with the style but it never happened. Let's see what Goba says on this.
I have implemented &listendand; in the author list, because I needed a quick way to add a list which will work among translations too automatically. I had no intention to start tweaking the sheets, or wait for some solution, since it was already too late to start crediting contributors.
Now that we can give more thought to it, it is clearly visible that a markup-rich solution is better, which shows us the structure of the list. For see also lists, the role would enable DSSSL and XSLT sheets to find out how the list items need to be separated and how the last item needs to be printed. It might also happen that simplelist already works this way (I have not tried it).
Why I have not shouted in to oppose the continued use of &listeandand; is that the use of this entity makes these kind of lists instantly findable in the source, so we can convert to a semantically better markup later if need be. However since there are already so much to do around the files, the changing of the see also lists might not be that big of a task anyway.
Ps. Thanks for Mehdi to get this to my attention again. This was on my (very long) TODO list somewhere :)
Goba
