M2H_OTHERINDEXES=
rcfile1:
rcfile2:
...:
rcfileN
<OTHERINDEXES>
rcfile1:
rcfile2:
...
rcfilei:
...:
rcfileN
</OTHERINDEXES>
-otherindexes
rcfile1:
rcfile2:
...:
rcfileN
OTHERINDEXES defines a list of resource files that
define other index pages
to generate when creating, or updating, an archive. When setting
the OTHERINDEXES resource, the filenames are separated by colons
(or semicolons under MSDOS/Windows). Line-breaks can be used
to separate filenames if setting OTHERINDEXES via the
OTHERINDEXES
element.
It is very important that each resource file specified defines the MAIN or THREAD resource to determine the type of index to create. Also, the IDXFNAME or TIDXFNAME resource (and IDXPREFIX or TIDXPREFIX resource if MULTIPG is active) must be defined to prevent overwriting of the default index pages.
MHonArc will only store the name of the resource files listed in the database. Therefore, for any subsequent updates of the archive, the extra index resource files must exist inorder to generate the extra index pages.
Since MHonArc will look in the archive location for
resource files specified with relative pathnames, you can keep the
other index resource files in the same location as the archive, and
just specify the filenames for the OTHERINDEXES
element
in the main resource file.
When create resource files for extra indexes, make sure to explicitly set all resources desired since some resource settings may no longer be set to the defaults due to database settings, or from a previously read resource file. Ie. MHonArc does not reset to the default settings when reading in the other resource files.
Nil
N/A
Since MHonArc only creates two indexes by default (the main/date index and the thread index), you can use OTHERINDEXES to define other index formats for navigating your archive. A possible setting for OTHERINDEXES may look like this:
<OtherIndexes> reversedateidx.rc subjectidx.rc </OtherIndexes>
1.2
IDXFNAME, IDXPREFIX, MULTIPG, TIDXFNAME, TIDXPREFIX, MAIN, THREAD