We have three related problems:

 - The argument names do not appear in the method summary when 
   "memberHead args" is chosen (the default)
 - The entire declaration (including return type) appears as a link label when
   "memberHead declaration" is chosen (used in the RTJ book)
 - When someone uses {@link Class.method label}, we currently
   ignore the label

These problems occur because we are using FrameMaker cross-references, 
which allow only <$paratext> and constant text (same for all links)
to be the link label.  It does not allow for arbitrary text
to be the link label.

Change the links throughout the document from cross-refs to hypertext Links.
This enables the link *label* to be different text from the actual
destination you're linking to.  This enables us to add argument names
in the first case above, to remove the return type in the second 
case above, and to inert the label in the text stream in the third case.

Doing this requires a character format be applied to the range of
characters to become the link.  I propose we use the existing "Link" 
character format for that.

N/A

The argument name now appears in the member summary table.  I will fix the other problems mentioned in this bug report soon.
  xxxxx@xxxxx   2001-10-21

This is the underlying bug for bug 4527383 "See also refs lack classname-dot prepend".
Raised to priority 1.
  xxxxx@xxxxx   2002-01-17

I was able to fix this bug tonight with Jamie's help.
I converted *method* xrefs to hypertext links (but not class or package xrefs).

I opened bug 4627756 to fix a couple of bugs I found and to convert 
package and class xrefs to hypertext links as well, for consistency.

  xxxxx@xxxxx   2002-01-23