The LITEMPLATE resource defines how each message listing is displayed
in the main index page. The $SUBJECT$ and
$FROM$ are resource
variables. $SUBJECT$ will get expanded to the current message's
subject, hyperlinked to the message page.
$FROM$ will be replaced with
the message's author's name and address.
Some resource variables take arguments. Take the following
NEXTLINK resource setting for
<li>Next by Date:
The resource setting uses two resource variables: $MSG$ and
However, an argument is given to each resource variable
delimited by ( ).
$SUBJECT$ will get expanded to the current message's
With the "NEXT" argument,
we are instructing MHonArc to use the next message's
subject. $MSG(NEXT)$ will get expanded to the next message's
filename. Therefore, the above resource value is creating a link to
the next message in the archive.
In the two examples given, the replacement value of
$SUBJECT$ is different (excluding the variable argument difference).
For compatibility of older versions of MHonArc, when $SUBJECT$
is used without any arguments, it will be expanded to
the current message's subject hyperlinked to the current message
page. If an argument is given to $SUBJECT$, then the variable
will get expanded only to the subject text of the applicable message.
NO hyperlink is automatically created.
Treat the text as part of a URL string. MHonArc will escape
any characters that are considered special in a URL.
An optional argument list delimited by parentheses: ( ).
Some resource variables can take arguments which modify how the
variable is expanded. If a variable can
take more than one argument, each argument will be separated by
a semi-colon. For example: $MSGLOCALDATE(NEXT;%H:%M)$.
In the example, there are two arguments to the $MSGLOCALDATE$
variable: "NEXT" and "%H:%M".
The end of a resource variable.
If an unrecognized variable is encountered, it gets replaced with an
empty string, and a warning is generated. If a literal "$"
is needed, use "$$".
different rules for variable expansion:
variable does not exactly match the set of variables available for
each resource, the variable text will be taken literally
as part of the element content. Therefore, a single "$"
can be used to represent a "$" character.
Variables should NOT
have ":NJMU" modifiers. This will prevent the
variables from being recognized. MHonArc automatically
treats the replacement value as a part of a URL string, so the
":U" modifier is not needed.
A time format string specifies how a date/time will be
printed for a date/time related variable. The syntax of the format
string is the same as the conversion specification as defined in
the GMTDATEFMT and
The NAME and HREF attributes to use in an anchor
to link to the archived message.
The NAME attribute provides a destination location when a message
links to the index page. This resource variable is equivalent to
The (raw) date of the message. This variable will expanded to
the date string used within the message itself. If you want to
customize the formatting of the date, use
Message header field value as stored by the
field-name denotes the name of the field value. The
following resources are applied to the expanded string:
MAILTOURL (if the
":M" modifier is specified), and
The ordinal message number of the current discussion thread. Numbering
starts with the first top/root message of a thread and ends with the
last message of the thread, spanning in sub-threads. The following
illustrates how the numbering works:
1. top/root message2. first follow-up to 13. first follow-up to 24. second follow-up to 25. second follow-up to 16. first follow-up to 57. first follow-up to 68. third follow-up to 1
The above contains 8 total message in the discussion thread, so numbering
goes from 1 to 8.
Markup linking to a list of index pages. $PGLINKLIST$ takes
two arguments: the first is the number of pages before the current page
to create links to; the second is the number of pages after the
current page to create links to. If either number argument is prefixed
with a 'T', then the list of links apply to the thread index.
Examples: $PGLINKLIST(3;3)$, $PGLINKLIST(T2;T3)$. The
link text for a given page is the page number, with the current page not
linked. For example, if the current index page is 5, $PGLINKLIST$
would expand to something like the following:
The subject text of the message, and if no arguments, wrapped in
an anchor element that hyperlinks to the message. This behavior exists
for backwards capatibility to provide a simple way to link to
the current message using the subject as the link text. The
no argument version is equivalent to:
Filename of thread index page. The value is set by the
resources. If the first page, TIDXFNAME is used. For other pages,
the filename is TIDXPREFIXpage-number.HTMLEXT.
A slice of the thread listing relative to the current message.
Size of slice is determined by the TSLICE
resource, or explicitly by the arguments provided. The first argument
is the number of maximum messages to list before the current message.
The second argument is the number of maximum message messages to list
after the current message. The third argument is a flag, 0
or 1, denoting if slice should cross discussion thread
boundaries or not. If any of the arguments are blank, the value
defined in the TSLICE resource
will be used.