The output of GED2HTML on a typical GEDCOM can be a very large number (thousands) of files and directories. Uploading each of these files individually to a Web provider would be an incredibly time-consuming and tedious task that is to be avoided at all costs. Similarly, performing any kind of individual editing on every file output by GED2HTML is also generally not feasible. About the only thing that it might be feasible to do (and sometimes necessary) is to systematically rename all the output files from GED2HTML, for example to change the filename extensions from .HTM to .HTML. Even this is to be avoided if at all possible.
To avoid having to upload individual files, the following general strategy is applied to get the files (and directories) from your system to your Web provider's system:
One big thing that can go wrong with the above strategy is that you might not have shell access to your Web provider's system. In that case, all bets are off, and you will have to check with your Web provider's technical support staff to find out what might be the best way to get the GED2HTML output files and directories from your personal computer to the Web provider's system. Often the best strategy in this case is to use a good FTP client such as WS-FTP that is capable of uploading multiple files without manual intervention.
Note that when unpacking a ZIP archive with a program such as PKUNZIP, it may be necessary to tell the program to preserve the directories (folder) organization the files originally had when they were created by GED2HTML. When using PKUNZIP to unpack the archive, this is done by giving the "-d" parameter on the command line. When using WinZip to unpack the archive, the "Use Folder Names" box should be checked to do the same thing.
Another alternative is the classic unix "tar" archiver. Many Web providers are Unix-based systems, and essentially every Unix system has the "tar" program available, so using "tar" to create the archive is often a viable option. You can download a TAR.EXE for use under DOS or Windows from here. (Note that this version of TAR.EXE is a DOS program that doesn't understand Windows 95 long filenames. There may be more up-to-date versions available on the 'net, but I haven't looked recently.)
Use the DOS command
You should be aware that, with a GEDCOM of any significant size, GED2HTML will produce a great many output files. One reason why GED2HTML uses subdirectories in the first place is that it can be somewhat inconvenient to manipulate a directory containing several thousand files. In addition, under Windows accessing such directories becomes very slow. If you ask GED2HTML to create a "flat" file structure, be aware that it could take substantially longer to create your HTML files, and that dealing with the resulting directory might be a bit cumbersome.
One way to get around this problem, should you encounter it, is to see if the uploading program or unarchiver you used has an option that allows you select whether DOS files are unpacked with upper-case or lower-case names. If so, that may be the fastest way out. If not, then GED2HTML is now fully configurable to handle this type of situation. If you find that files are ending up on your Web provider with all upper-case names, then set the "Case-fold-links" option of GED2HTML to "Upper" before processing your GEDCOM. This will cause GED2HTML to make all the links in the HTML output upper-case only, so that they will work properly once the whole batch of files arrives on your provider's system. If you find that files are ending up on your Web provider with all lower-case names, then set the "Case-fold-links" option of GED2HTML to "Lower". If both your system and your Web provider's system are case-sensitive systems, then setting "Case-fold-links" to "None" is probably the option for you. See here for more details on this, and other customization options provided by GED2HTML.
When you create HTML files under Windows 3.1, all the files are created with a .HTM extension, because DOS only supports three-letter filename suffixes, and will truncate anything longer than that. When run under Windows 3.1, the default behavior of GED2HTML is to use a .HTM extension for all the hyperlinks internal to the output files, in order to be compatible with the .HTM extension with which the files are created.
When you upload files created under Windows 3.1 to your provider's system, everything will be fine as long as the HTTP (Web) server running on your provider's system is set up to recognize files ending in .HTM as HTML source code. The server passes this information along to your browser, which formats displays the information properly. However, not all HTTP servers are configured to recognize files ending in .HTM as HTML files. In this case, the server will tell your browser that the file is text, and it will not be properly displayed.
The simplest way out of this predicament is to ask for the cooperation of your Web service provider. Web servers generally have a "mime.types" configuration file, which lists mappings from filename extensions to MIME types. This information allows the server to determine what kind of information is in a file by looking at the extension. The server communicates this information to your browser when the file is retrieved, and the browser, in turn, uses the information to control how the file is displayed. Some servers lack an entry:
Although many Web service providers will make the configuration change described above, some providers will refuse to make the change and will tell you that you should change all filenames from .HTM to .HTML, perhaps using a special script that they provide. In this case, it will be necessary to reprocess and re-upload your data, so that all the internal links in each of the datafiles say .html instead of .htm. Under the Windows 3.1 version of GED2HTML, this can be done by putting the following in the "Additional Options:" field in the top-level dialog box:
I have also been told about a utility called "MultiRen", which is a Multiple File Rename utility. A GED2HTML user writes:
I discovered a neat Multiple File Rename utility, MultiRen, a great idea for those of us that use your GED2HTML for generating multiple databases, so we can give the g0000... and ind00... files different names (g12xx and ind12xx for instance) for each database. [I've been doing this by hand, and editing the html with a global find & replace utility]GED2HTML home page
> You can find it on p. 269 of the June 9th, '98 issue of PC Magazine and
http://www.pcmag.com(at the home page click on downloads) or
ftp.zdnet.com. The full source code is also available from
Copyright © 1995-2004 Eugene W. Stark. All rights reserved.