Re: Colon in index items

[Karl Berry]

      (a) The stand-alone Info doesn't use regular expressions to parse 
          references;

Sure, we would have do it by hand in Info.  We do it by hand now in
the other direction.

      (b) You could have more than one colon in a row (happens a lot in C++, 
          for example).

Sorry, I don't see the problem.

* foo::bar:  nodename.
will still get parsed correctly, seems to me.  The .* will swallow
everything up to the very last : ... as long as the nodename does not
have any colons in it.

^\* (.*)( <[0-9]>*)?:[ \t]*(.*)\.$

    The possibility of parsing references from the end was raised in the past 
    (IIRC).  It works better in some cases, but fails in others.

Specifically?

Thanks,
k