Re: inconsistent handling of 'Top' node case in refs and in nodes

[Karl Berry]

    possible to have anchors with a different case than the node. 

Thanks for the report.  Here's a patch.  I'm not happy with it, because
it simply forces the node name to always be "Top", throwing away
whatever the user actually had in the document.  So the error message
says "Top" instead of "top" or "TOP" or whatever.

However, that's what is being done already for nodes named "Top" in
whatever case, so it'll have to do for now.

Regards,
karl


*** node.c.~1.9.~       Mon Mar 24 06:06:30 2003
--- node.c      Tue Apr 29 16:02:04 2003
***************
*** 1045,1050 ****
--- 1045,1053 ----
    /* Parse the anchor text.  */
    anchor = get_xref_token (1);
  
+   /* Force all versions of "top" to be "Top". */
+   normalize_node_name (anchor);
+ 
    /* In HTML mode, need to actually produce some output.  */
    if (html)
      {