A few thoughts I had while actually using Halibut's Info output.
authorben <ben@cda61777-01e9-0310-a592-d414129be87e>
Sat, 7 Apr 2007 23:33:50 +0000 (23:33 +0000)
committerben <ben@cda61777-01e9-0310-a592-d414129be87e>
Sat, 7 Apr 2007 23:33:50 +0000 (23:33 +0000)
git-svn-id: svn://svn.tartarus.org/sgt/halibut@7449 cda61777-01e9-0310-a592-d414129be87e

bk_info.c

index 5b82177..6b0e16f 100644 (file)
--- a/bk_info.c
+++ b/bk_info.c
  *        * Section 1.2: Nodename. Title of section.
  * 
  *  - might be helpful to diagnose duplicate node names!
+ *
+ *  - more flexibility in heading underlines, like text backend.
+ *     + Given info.el's fontifier, we'd want the following defaults:
+ *       \cfg{info-title-underline}{*}
+ *       \cfg{info-chapter-underline}{=}
+ *       \cfg{info-section-underline}{0}{-}
+ *       \cfg{info-section-underline}{1}{.}
+ *
+ *  - Indices generated by makeinfo use a menu rather than a bunch of
+ *    cross-references, which reduces visual clutter rather.  For
+ *    singly-referenced items, it looks like:
+ *      * toner cartridge, replacing:              Toner.
+ *    It does a horrid job on multiply-referenced entries, though,
+ *    perhaps because the name before the colon is meant to be unique.
+ *
+ *  - The string "*note" is matched case-insensitively, so we could
+ *    make things slightly less ugly by using the lower-case version
+ *    when the user asks for \k.  Unfortunately, standalone Info seems
+ *    to match node names case-sensitively, so we can't downcase that.
  */
 
 #include <stdio.h>