If you run this program under Windows (as G2H.EXE, see here for details), you can supply command line options exactly as you would under Un*x. (Note that the program does not recognize the DOS conventions of control flags starting with ``/'' and parameters specified using ``:'' after the control flag.) If you run the program under Windows, then you don't actually have a "command line" on which to specify the parameters, as it is intended that Windows programs should pop up a dialog box to obtain their parameters. To make running the program easier and less confusing for most Windows users, I have supplied the front-end program GED2HTML.EXE whose purpose is simply to pop up a dialog box, collect parameters, and start G2H.EXE with the appropriate command line. See here for a more detailed description of how to launch the program under Windows.
Here are some examples of typical command lines and their effect on GED2HTML:
ged2html myged.ged
Run GED2HTML on the GEDCOM file ``myged.ged'', using the default options and creating the HTML files containing individual information in the current directory (or in subdirectories of the current directory). Also created are index files ``PERSONS.html'' and ``SURNAMES.html'' (``PERSONS.HTM'' and ``SURNAMES.HTM'' under Windows). If the number of individuals exceeds the default ``index width'' (currently 28), then ``PERSONS.html'' is the root of a hierarchical index organized into several files in such a way that the total number of entries in each file is less than or equal to the index width. Finally, a textual index file ``GENDEX.txt'' (``GENDEX.TXT'' under Windows) is created. This file contains one line for each individual and is output in a format suitable for processing by Unix tools such as AWK and SORT. It is intended for the use of network indexing software that utomatically collects pointers to individual data from a large number of sites and merge them into a single master index. See here for further information on an index I am maintaining.
ged2html -i myged.ged
Same as above, except that only the individual HTML pages are created, and not the ``PERSONS.html'', ``SURNAMES.html'' or ``GENDEX.txt'' files.
ged2html -c myged.ged
Automatic capitalization of surnames is disabled, so that surnames appear in the HTML output the same as they do in the original GEDCOM file.
ged2html -w 0 myged.ged
The ``index width'' is set to zero, which disables the production of a hierarchical index and arranges for all individual entries to be placed in the single ``PERSONS.html'' file.
ged2html -w 100 myged.ged
The ``index width'' is set to 100. This results in somewhat fewer index files and a shallower index hierarchy than the default setting.
ged2html -i -c -s I1001 I1002 -- myged.ged
This command specifies that no index files are to be generated, that automatic capitalization of surnames is disabled, and that HTML output files should be produced *only* for the individuals with cross reference ID's (XREF) I1001 and I1002 in the GEDCOM file. An arbitrarily long list of ID's can be specified after the ``-s'' flag, so that the ``--'' option is needed to indicate the end of option processing and that all remaining arguments are to be regarded as the names of GEDCOM files.
ged2html -d 100 myged.ged
Cause the individual HTML files to be placed in subdirectories, with a maximum of 100 files per subdirectory. The hyperlinks (URL's) placed in the HTML output files take the directory organization into account. This means that once you process a GEDCOM file and create a tree of directories and HTML files, you must preserve the organization of this tree if you want a WWW browser to be able to traverse the links between the files.
ged2html -d 0 myged.ged
Specifying ``-d 0'' disables the use of subdirectories, so that all individual HTML files are placed in the current directory.
Hopefully, you get the idea... Here is a list of all the options currently understood by the program:
Print a brief message listing the available options.
Print version number of program and copyright information.
The GEDCOM 5.3 draft standard standard specifies that continuation lines created using CONT are to be separated from the previous line by a newline, and that continuation lines created using CONC are not to have a newline. This flag forces a strict adherence to the standard. Strict adherence is not the default because I have found that most genealogy programs don't even output CONC; instead they use separate NOTE records when a line break is indicated. Thus, most people's output looks best when CONT and CONC are treated identically.
Disable automatic capitalization of surnames.
Specify number of individual files per subdirectory (0 means don't use subdirectories).
Specify a template string for the names of the HTML files (default '%s.html' or '%s.htm').
Force production of the ``GENDEX.txt'' textual index file (for use by automatic indexers). See here for more information on what this file is for.
Do not generate the ``PERSONS.html'' and ``SURNAMES.html'' index files containing entries for all the individuals and surnames in the input. See here for more information on these files.
Output files contain specified number of individuals (0 means don't put multiple individuals per file).
Include pedigree charts of the specified depth (0 means don't include any pedigree charts).
Limit the production of output files to a specified list of zero or more selected individuals.
Specify a template file for the surname index.
Specify a template file for individuals.
Specify a template file for the individual index.
See here for more information
on templates.
Create hierarchical index with nodes of specified maximum width (0 means put all individuals in one index file).
Copyright © 1995 Eugene W. Stark. All rights reserved.