HTML Indexer (tm) version 4.1.9
Copyright (c) 1998-2016  Brown Inc.
All Rights Reserved


Thank you for your interest in HTML Indexer, still the 
easiest way to create and maintain indexes for web sites, 
intranets, HTML Help, JavaHelp, and other HTML documents!

These release notes contain important information about 
installing HTML Indexer and using the NEW FEATURES.



INSTALLATION

Installing HTML Indexer will replace any existing version 
in the installation directory WITHOUT WARNING.

Specifically, if you accepted the default installation 
directory for HTML Indexer 2.x or 3.x, and you also accept 
the default installation directory for this version, you 
will replace most of the existing program and tutorial 
files.

Your indexes and source files, however, are not affected.



NEW FEATURES

HTML Indexer 4.1 adds right-click selection to the index 
preview pane and fixes a problem with saving certain files.

See the revision history for details of minor releases.

HTML Indexer 4.0 added many important new features:

 *  Fully integrated cross-references

    Create "see" and "see also" references with the same ease 
    as index entries.

 *  Specification of display targets

    Set up index entries that display the source material in 
    a different frame or window.

 *  Framed output for HTML indexes

    Display the navigation bar (the links to group headings) 
    in a separate frame, so they're always visible.

 *  Multiple-file output for HTML indexes

    Put each letter group in a separate file for faster 
    navigation through a large index.

 *  Multiple undo-redo memory

    To err is human, and HTML Indexer gives you lots of 
    chances to experiment and recover.

 *  Automatic use of the default browser

    By default, HTML Indexer opens your finished index in 
    the application associated with the .htm file extension, 
    instead of Notepad.  Of course, you can still specify a 
    different browser or editor.

 *  One-step conversion of default entries

    If you like the default entries HTML Indexer creates for 
    your targets, you can accept one or many with a single 
    command.  That way they won't be overridden when you add 
    your own index entries to the same targets.

 *  Stylesheet control over the formatting of the index 
    heading (H1 tag)

    Use the IndexBodyNav and IndexBodyIndex classes to format 
    the headings at the top of the index and the navigation 
    frame (if used).  See the Indexer.css file for examples.

HTML Indexer 3.4.2 enhanced the use of classes to include 
formatting of return-to-top paragraphs.

HTML Indexer 3.4 added the option to change how index entries 
are indented in the output HTML index file.  To accommodate 
older browsers, HTML Indexer typically uses nonbreaking space 
( ) characters to force indentation of entries:  
2nd-level entries are preceded by five nonbreaking spaces, 
3rd-level entries by ten, and so on.

Since HTML Indexer 3.4, you can choose to use "classes" to 
precisely control indentation:  1st-level entries are 
formatted as <P class="index01">, 2nd-level entries as 
<P class="index02">, and so on.  You must define these 
classes (P.index01, P.index02, and so on) in a stylesheet 
(.css) file, and specify the path and name of that file.

Use the CSS tab of the Project (or Default) Style Settings 
dialog box to set up classes and specify the stylesheet file.  
If the stylesheet file is in a different directory from the 
output HTML index file, be sure to use relative paths with 
forward slashes (/).

HTML Indexer 3.3 removed the restrictions on location of 
graphics (for letter group headings, links to letter 
groups, and return-to-top links), stylesheets, and 
"include" files:

 *  You can use a single set of files for all the indexes 
    you create.

 *  You can define default locations for these graphics, 
    stylesheets, and "include" files.

Of course, you must make sure the graphics files and style 
sheets will be available from within the publication 
directory structures, too.

It's always esasiest to store these files at or below the 
project's main directory.  If you use a location outside the 
main directory, though, be sure to specify the location as a 
relative path (such as "../../otherdir/styles.css").

Note the use of forward slashes, too, rather than DOS-style 
backslashes ("\").  Remember that these paths may be served 
on platforms running non-Windows operating systems, and the 
files may be viewed using non-Microsoft browsers, so correct 
HTML syntax is very important.



HELP-RELATED OUTPUT FILES

When you open any existing project, make sure the project's 
main directory does not contain a file named Indexer.hhk, 
Indexer.xml, or Indexer.jhm (default names for the optional 
HTML Help and JavaHelp output files).

For a new project, HTML Indexer checks for the existence 
of these files and warns you that they will be overwritten.

For an existing project, however, no such check is 
performed!  Existing files using any of the new default 
filenames (Indexer.hhk, Indexer.xml, and Indexer.jhm) are 
assumed to be output of previous work on the project, and 
they will be overwritten if you save any changes to the 
project.



OTHER FILENAMES TO AVOID

Depending on the output options you select, HTML Indexer may 
create additional files with predictable names.  The main 
directory of your index project must not include files with 
these names:

<projectName>.htm          The main body of index entries
                           (or the frameset definition)
<projectName>-nav.htm      Contents of the navigation frame
<projectName>-content.htm  Contents of the index frame
                           (all letter groups)
<projectName>-A.htm        Entries that start with "a"
<projectName>-B.htm        Entries that start with "b"
<projectName>-C.htm        Entries that start with "c"
 ...
<projectName>-Z.htm        Entries that start with "z"
<projectName>-Symbols.htm  Entries that start with a symbol
<projectName>-Numbers.htm  Entries that start with a number



COMMAND-LINE INVOCATION

Since HTML Indexer 3.1, you can run HTML Indexer from the 
DOS command prompt.

Usage:

  Indexer.exe  projectfile.ipj  [options]

Options:

  /makeindex

Example:

  "C:\Program Files\Html Indexer\Indexer.exe"  "C:\My Web Projects\Indexer.ipj"  /makeindex

When you use the /makeindex option, HTML Indexer loads the 
specified project, builds the indexes, and exits.  A 
progress bar appears briefly, but there is no other visual 
display.

You must run HTML Indexer normally to create the project, 
manage files and index entries, specify output types and 
filenames, and set style options.  Once you do, you can 
write a batch job to create the project (.ipj) file, too.

The real purpose of this feature is to support batch 
creation of indexes for web sites that change content 
rapidly and that code source files to provide acceptable 
default index entries.



DOCUMENTATION

The tutorial has not been updated to include a description 
of some of the latest features.  As a result, some of the 
screen shots differ slightly from the current version of the 
software, but not in ways that will cause confusion.

It's still the fastest way to get working with the basic 
features, too, and we encourage you to take an hour or so to 
go through the lessons.



FEEDBACK

Your comments are important to us!  We'd also love to see 
samples of your work.  Please send them to:

  feedback@html-indexer.com

Thank you!