| Date: Mon, 4 Nov 2002 11:55:00 -0500 | From: [EMAIL PROTECTED] (Karl Berry) | | Changing hundreds of decade-old function names in a dozen Scheme | implementations seems an unreasonable burden merely to continue | using texinfo. | | Of course Scheme should not change, that would be absurd :). | | Is texinfo going to support Scheme? | | It supports Scheme (and C++ and every other language that uses colons) | as well as it ever did, which is to say, colons in index entries or node | names can get misinterpreted. This is clearly a defect in Texinfo which | we wish to fix, but it is not easy to do so.
Let me suggest a way to do this (assuming there is some legacy issue preventing info readers from considering only the last ":" in an index line as the separator). Putting a TAB character after the ":" in index entries in .info files does not screw up indexing for the info (4.1) program or emacs (21.2). The next version of makeinfo would put tabs after ":" in index entries. New versions of info readers would treat ":<TAB>" as the separator if present; falling back to ":" if tabs are absent. Notice that this method transparently interoperates with old versions of .info files and also with old info readers. | The new warning is there not for Scheme et al. manuals, but for manuals | which might have one or two index entries containing colons that could | be rewritten, for the sake of current info readers. | | Meanwhile, the best approach for you is just to run makeinfo --no-warn. OK. _______________________________________________ Bug-texinfo mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-texinfo
