DRAFT speech-friendly message-page resource definitions

Here is the current state of my .rc file.

I have killed the headers entirely per Earl's help and the policy
notions in 

http://www.access.digex.net/%7Easgilman/lynx/plans/format_options.html

A cursory examination by one of the best of blind reviewers found
only on point on the index pages (multiple links on a line, which
I haven't worked on) as an impediment worth mentioning (and not
bad at that).

I do mean to make the context and follow-up links at the foot use
whole words and maybe even whole sentences in the full-up speech
adaptation.  Abbreviations are a net value-subtractor in a speech
context.
-----------------------------------------------------------------------
<!-- ================================================================== -->
<!--    headless.rc                    
        Al Gilman <asgilman(_at_)access(_dot_)digex(_dot_)net>
  -->
<!--    MHonArc Resource File                                           --
  --                                                                    --
  --    Description:                                                    --
  --                                                                    --
  --        This is an experiment to generate message pages that        --
  --        listen well in a speech-output browse.  See                 --
  -- <URL:http:www.access.digex.net/%7Easgilman/lynx/plans/format_options.html 
--
  --        for some motivation.                                        --
  -->
<!-- ================================================================== -->

<!-- ================================================================== -->
<!--    Variable definitions                                            -->
<!-- ================================================================== -->
<!--
        User defined variables are defined by the DEFINEVAR element.
        The first line is the name of the variable and subsequent
        lines to the close tag are the value of the variable.  User
        variables can reference other variables.
  -->
<!-- ================================================================== -->

<!--    Variable for name of the list the archive is derived from
        Note: The "chop" attribute is to tell mhonarc to delete the
              last newline (or end-of-line sequence) from the content
              of the element.
        It is up-cased because it is used as a prefix in the page TITLE
  -->
<DEFINEVAR chop>
LISTNA
LIST-NAME           
</DEFINEVAR>

<!-- ================================================================== -->
<!--    Options                                                         -->
<!-- ================================================================== -->

<!--    It is good to be explicit when possible since a default
        resource file, and/or environment variables, may be in affect.
  -->
<MAIN>
<THREAD>
<SORT>
<REVERSE>
<NOTREVERSE>

<!--    Have mhonarc generate multipage indexes with a maximum of 40
        messages listed per page.
  -->
<MULTIPG>
<IDXSIZE>
40
</IDXSIZE>

<!-- ================================================================== -->
<!--    Thread index resources                                          -->
<!-- ================================================================== -->

<!--    The thread index is setup where a thread will have the subject
        in bold at the top of the thread and the names of the authors
        of the messages in the thread will be hyperlinked to the
        actual message.  Nested unordered lists are used to provide a
        visual cue of the depths of the thread.

        Unique messages are show in normal text.
  -->

<TTITLE chop>
$LISTNA$:&nbsp;Discussion&nbsp;Threads
</TTITLE>


<!-- ================================================================== -->
<!--    Main index resources                                            -->
<!-- ================================================================== -->

<!--    The main index is the chronological index since we have
        specified the <SORT> element (which is the default).
  -->
<TITLE chop>
$LISTNA$:&nbsp;recent messages first
</TITLE>


<!-- ================================================================== -->
<!-- Message page tailoring
<!-- ================================================================== -->
<!-- ================================================================== -->

<MsgPgBegin>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN">
<HTML>
<HEAD>
<TITLE>$SUBJECTNA:72$</TITLE>
<TITLE>$LISTNA$:&nbsp;$SUBJECTNA:60$</TITLE>
<LINK REV="made" HREF="mailto:$FROMADDR$";>
</HEAD>
<BODY>
</MsgPgBegin>



<TOPLINKS>

</TOPLINKS>

<!-- Revised Setting -- for dev-access rev 1 ff.
 -->
<SubjectHeader>
<H1>$FROMNAME$:&nbsp;$SUBJECTNA$<BR>
$MSGLOCALDATE$</H1>
</SubjectHeader>


<Excs Override>
.*
</Excs>

<HEADBODYSEP>
<BR>
</HEADBODYSEP>



<BotLinks>
<HR>
<UL>
$PREVLINK$<BR>
$NEXTLINK$<BR>
$TPREVLINK$<BR>
$TNEXTLINK$
<LI>Index(es):
<UL>
<LI><A HREF="$IDXFNAME$#$MSGNUM$">
Main</A></LI>
<LI><A HREF="$TIDXFNAME$#$MSGNUM$">
Thread</A></LI>
</UL>
</LI>
</UL>
</BotLinks>

<!-- edit end -->