From f1399b6857d72ebe3a82618226ba019dcc9ce789 Mon Sep 17 00:00:00 2001 From: Ben Harris Date: Sat, 7 Apr 2007 23:33:50 +0000 Subject: A few thoughts I had while actually using Halibut's Info output. [originally from svn r7449] --- bk_info.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/bk_info.c b/bk_info.c index 5b82177..6b0e16f 100644 --- a/bk_info.c +++ b/bk_info.c @@ -21,6 +21,25 @@ * * 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 -- cgit v1.1