On Tue, 19 Mar 2002, Richard Stallman wrote:
> Let's assume that we have a manual > about C++ classes, which describes a class `foo'. Then it will probably > document methods like `foo:foo', `foo:~foo', and `foo:bar'. As a user > who reads that manual and looks for the methods from that class, I'd try > typing "i foo: TAB". Is that what you have in mind as well? > > Yes. And either way the result would failure, since the menu > item in the index won't start with `foo:'. You are again comparing with the temporary kludge I made in the Emacs manual. I would never think about doing something similar in a manual about C++, because it will never work there. So I suggest to judge the proposal on its own, not as compared to the temporary change that doesn't pretend to be a general solution. > Let's quickly change Makeinfo to convert colon to `<colon>' > and change the Emacs manual sources back. If the problem with Emacs manual is with the printed copy, I can put a @iftex there that would produce a literal colon in print. Would that be okay? _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
