Ged2web is program for generating a set of web pages from a GEDCOM file.
The program produces a view for each person consisting of an information summary including:
The number of individuals per file can be set by the user to allow a balance to be set between the number of files generated and the size of each file.
An index of individuals is produced with a user set number of individuals per index file (again to allow a file sizes to be traded off against number of files. Each viewable block within a file is followed with links to the previous and next blocks as well as a set of alphabetic links into the index.
A list of surnames is produced to link to the index of individuals.
No attempt is made to import source information.
Although the program will import more than one GEDCOM file no attempt is made to perform a merge operation. As a result any people duplicated across two or more GEDCOM files will result in duplicates in the generated web pages.
Ged2Web for Windows can be found here.
If any problems are encountered with the program I would appreciate it if you could inform me by email at with a subject line of "Ged2Web Enquiries" in order that I can address the problem (If possible, could you include the GEDCOM file(s) being used and the settings that you used (Alternately supply the ged2web.ini file). Please make sure that you include the Ged2Web version number being used.
As of version 3.43, no registration of Ged2Web is required. You may make a Volutary Donation should you wish to do so. Users of previous versions, both registered and unregisterd, may download version 3.43 or later of Ged2Web.
If you would like to reward me for my past efforts in producing Ged2Web, you may use Paypal to make a donotation using the button below:
This is purely optional and will make no difference to the features or your use of Ged2Web. You should donate whatever you feel the program is worth to you as it stands. Donations should be made on the understanding that it does not entitle you to any enhanced level of service from myself.
No functional changes. Updated the installer to elliminate anti-virus false positives
Improved indexing of files in the surnames page.
Fixed an issue with the utf8 encoding of the creation date on the surnames page.
Removed the option to create non-utf8 encoded web pages.
Added explicit 'NAME' checkbox to deciding whether or not to include 'Also known as' NAME tags (those other than the first) in the HMML output.
Fixed issue whereby blank lines in a gedcom file caused early termination of the file import.
Added support for Individuals with multiple NAME tags. The first tag is considered 'primary'. Additional NAME tags create 'Also known as" aliases.
Fixed a problem whereby the nature of parent/child relationships (birth/adopted/foster/sealed) was not handled correctly causing misleading or wrong output.
Added support for the Gedcom 5.5.1 'FACT' tag as an alias to the 5.5 'EVEN' tag which appears to do the same thing.
Added support for UNICODE (UTF-16) encoded gedcom files.
Improved the handling of the ANSEL character set used by some GEDCOM files.
Fixed a number of issues with utf8 support when characters not in the latin-1 character set were encounted.
Fixed an issue that caused corruption of the index file separator.
Fixed an issue with the encodeing of the email address when email is exported.
Fixed a formatting issue on notes pages.
Fixed Installer issue that could cause install failure on 32 bit systems.
Improved cursor behaviour during export.
Fixed issue only seen with some multiple file imports that could lead to incorrect cross referencing of individuals associated with a family.
More improvements to GUI responsiveness.
Fixed issue whereby GUI became unresponsive when large eports were performed.
Fixed issue whereby settings file location was not correctly setup in Windows XP and prior.
Changed installer to install a 64bit version on 64 bit Windows.
Fixed issue whereby settings changes were not saved in Windows 10.
Added support for utf8 encoded gedcom files with a Byte Order Marker at the head of the file.
Added option to output pages using utf8 character encoding instead of latin-1. Extended support for reading non-standard utf-8 encoded GEDCOM files.
Added an option to output birth and death location in the generated index pages.
Removed the marking of output web pages with the "unregistered" status of Ged2Web.
Fixed a cosmetic problem whereby the number of families encountered during import was miscounted.
Fixed a single problem whereby a spurios new line was inserted at the end of a note when 'retain formatting' was selected.
Fixed an import problem whereby empty family records caused the following family record information to be wronly associated with the empty record.
Fixed a problem with the HTML generation when ancestor and/or descendent charts were generated on the individual page.
Added an option to add two leading columns to the index file containing the
original gedcom file and the gedcom individual reference.
Added the ability to handle Census events
Fixed problems experienced with forward referenced notes under certain
circumstances
Fixed problem with a spurious 'next' link at the end of the alphabetic links at the bottom of index pages when the number of people in the gedcom file is an exact multiple of the index block size.
Further tidying up of generated HTML code
Changed the way that alphabetic character links at the bottom of the index
files are generated so that it copes with large index sections better (made
necessary by the changes in version 3.33)
Tidied up HTML generation to make it more consistent
Relaxed limit on number of people in an index section (was 50 now 1000)
Added the optional ability to generated a text index file similar in nature
to the Gendex.txt file that was removed in version 3.30. The main differences
is that that place names are enclosed in quotes, the default separator (it can
be changed) is a ',' instead of a '|' and the surname is not repeated.
Changed the progress bar to use smooth update instead of stepped update.
Changed the way that the index table spacing is done so that no vertical
spacing is introduced.
Removed the generation of the gendex.txt file since it can not now be used (The
genealogical index at www.gendex.com is defunct).
The import filename dialogue now remembers the directory of the last
import.
The import filename dialogue now filters the files for gedcom files (*.ged).
A progress bar is now displayed during the export.
Changed the encoding of email addresses to fully encode the email address
rather than just the @ character.
Fixed two minor problems with version 3.27. The first was an HTML validation problem on the generated surnames page. The second was an 'Out by one error' on the indentation of the ancestor charts.
Changed to replace the '@' in the supplied email address with the equivalent
character entity '@' in order to prevent the harvesting of email
addresses by spam robots.
Fixed minor problem where an index block separator was inserted in the index
files even when the number of blocks per file was set to One.
Changed the Main surnames page to provide links to the surnames starting with
each different character.
Fixed problem with the language dependent sorting.
Fixed problem whereby the list of links at the bottom of the index pages only
contained characters from the English alphabet.
Added the ability to set the amount of indentation per generation on ancestor
charts and descendent lists.
Fixed three problems:
TR and TD elements not terminated properly in the index pages.
Links at bottom of the page not enclosed in any element lower in the hierarchy
than BODY .
The title of individual pages when only one person was put on each page was
still presented as a range.
Added limit support for the ANSEL character set used by GEDCOM.
Changed to way that support for ISO 8859-1(Latin-1) character entities are handled for the importing of Gedcom data so that the character entities do not affect the sort order of names.
Changed the HTML generation to use standard named character entities for extended characters (above 127 in the ANSI char set).
Added support for the non standard character set 'ISO 8859-1' which is used by some family tree database programs and which includes HTML character entities.
Added support for Adoptive, Foster and Sealing parent Child relationships
Added support for the LDS tags 'ENDL', 'SLGS' and 'SLGC'
Made performance improvements to the sorting of individuals during import.
Fixed improper labelling of the boundary box on the Marriage Events tab of the Options Dialogue
Fixed problem where the LDS Endowment event utilized an incorrect short form.
Changed the way cross referencing is handled to make it more rugged. This allows Ged2Web to handle non-numeric reference number schemes such as that used by Ancestral File which it could not do beforehand.
Added support for 17 additional event tags. Ged2Web now supports all of the GEDCOM event tags.
Added the ability to choose which events should be exported to the HTML pages.
Further quality improvements.
Fixed a minor memory leak that could occur under very rare circumstances.
Minor quality and performance improvements.
Fixed bug whereby empty Notes, Descendant and Ancestor pages could be created even though they weren't linked to.
Improved the handling of the gedcom EVEN tag in in order to handle the form of the tag used for AKA by family Origins.
Improved the handling of the GEDCOM ADDRESS tag.
Improved the handling of OCCU tag structures where the occupation is placed in the place field. (This is done by FTM)
Added the ability to import cause of death from Gedcom and present it on the Individuals page.
Fixed a bug in the generation of the style-sheet link where by the reference was being incorrectly generated for pages other than the 'surnames' page when the 'Create all files in the same directory' option was selected in the 'Export' tab of the 'Options' property sheet'.
Further increased the options associated with the output format of notes. You can now choose not to retain the original formatting which will cause ged2web to generate notes pages that do not consist of pre-formatted text. This provides better looking web pages when the original notes are not heavily formatted using whitespace.
Increased the maximum number of descendent generations that can be shown on the descendent pages to 60.
Added the ability to enable or disable the word wrapping in the export of 'notes' pages and to set the maximum number of characters on a line when word wrapping is enabled. This gives sufficient control to enable web pages to be created which retain any formatting in the original notes when necessary.
Improved the way that word wrapping is done so that it copes with NOTE, CONC and CONT tags with submitter information of more than 80 characters.
Changed the Options Dialogue to use a property sheet in order to make it fit into a smaller area and to limit the number of options presented at any one time.
Added a code to wrap lines in notes at 80 characters. The notes are output as pre-formatted text so that any formatting will be retained. However, the line wrapping may upset some formatting if the formatted line is longer than 80 characters.
Added the ability to cope with a non standard way of generating Notes records. This non standard output is used by EasyTree version 5.2 from Sierra. Prior to this change, Note records generated in such a way would be ignored. This change will not interfere with the import of correctly generated note records.
Fixed a long standing problem whereby the long form of the Gedcom 'Continuation' tag was ignored.
Fixed a serious problem whereby generating HTML with the 'Include Notes' option deselected when there are notes associated with individual events in the gedcom file, caused a protection fault. This does not affect operation on files which only have notes associated with individuals or marriages.
Fixed a serious problem (introduced in 3.06) whereby parent links were not getting correctly made.
Changed the way that occupation tags are displayed to suppress the '(Date and Place Unknown)' message.
Version 3.06 adds the ability to turn the tool tips on and off from the system menu.
This version also addresses a problem with previous versions whereby children within a family would be duplicated if the family record preceded the individual records in the Gedcom file.
Version 3.05 adds the ability to sort marriages associated with a person so that marriages are presented in chronological order.
Version 3.05 also adds the ability to handle Gedcom divorce tags of the form '1 DIV N' with no subordinate tags to indicate that no divorce took place. This is required to handle gedcom files generated by some programs. Previously, Ged2Web would have taken the presence of a DIV tag with no subordinate tags to mean that a Divorce was known to have occurred but no details are known.
Version 3.04 fixes a long standing bug whereby a 'prev' entry was printed at the bottom of the Index if all of the individuals fitted on one index page.
Version 3.04 fixes a memory leak present in version 3.03
Version 3.03 changes the way that individuals are sorted to make the sort compliant with the lexical order of characters in different national alphabets.
Version 3.03 now sorts children according to their approximate year of birth.
Version 3.03 fixes a bug in previous versions whereby the HTML generation was incorrect if individuals with no sex designation were present in the Gedcom file.
Version 3.01 fixes a bug in previous version 3.0 whereby the gendex file was being generated incorrectly.
Version 3.0 fixes a bug in previous versions whereby the presence of a Gedcom Event Detail structure with the first subordinate structure being a Note, would cause the program to exit abnormally when importing the file.
Version 3.0 can handle more than one of the Gedcom Events for each individual. Previous versions would only generate HTML output for one Event of each type. If more than one event of a given type was encountered, then previous versions would overwrite the information from prior events of the same type with the information from the latest.
Version 3.0 now understands the Gedcom RESI, ADDR, EVEN and TYPE tags. The TYPE tag is used only to provide details of the nature of the Event described by the EVEN tag.
Ged2Web 2.67 adds a count to each surname listed on the surnames page. It also adds a prompt to tell you when the export process has completed.
Ged2Web 2.67 fixes a bug whereby Name entries in a GEDCOM file with no surname present would terminate the program abnormally when the HTML export was started.
Version 2.66 adds the ability to create all files in the same directory if desired.
Version 2.64 adds the creation of notes pages associated with relationships and marriages.
Version 2.63 dramatically speeds up the import and indexing of large GEDCOM files (in excess of about 5000 individuals). For Small files (less than about 1000 individuals) no appreciable difference will be observed.
Version 2.62 dramatically speeds up the generation of the HTML for large files (in excess of 5000 individuals) especially when descendent lists are being produced.
Version 2.61 fixes a bug associated with the importing of events. The bug causes the line after the event entry to be skipped when there are no GEDCOM lines associated with the event itself.
Version 2.60 adds the ability link to a style sheet and adds code to separate sections within an HTML file in order to eliminate problems with confusing link operation.
Version 2.59 fixes two problems associated with the importing of notes.
Version 2.58 addresses a major fault introduced in version 2.57 which prevented the export of the HTML due to a problem with the index file path names.
Version 2.57 addresses a single fault whereby the link to the index of individuals on the surnames page did not work.
Version 2.56 addresses a fault in the importing of notes associated with events rather than individuals or marriages. Versions 2.55 and 2.54 would not correctly import the GEDCOM file when such notes were present.
Version 2.55 addresses a fault in the importing of individuals names when the surname is enclosed in '/' characters and no space is present between the last forename and the first '/' character. The bug manifests itself as an omission of the last character of the last forename
Version 2.54 addresses a fault in the generated output when an individual has children from more than one relationship and there are no details known for the second relationship. In this case previous versions of the program produced HTML output which seemed to indicate that the child(ren) from the second relationship were from the first.
No new features have been introduced in version 2.53 of Ged2Web. However, a serious bug affecting all previous versions of Ged2Web has been fixed.
In previous versions of the program, producing a descendent chart with more than 5 generations would cause indeterminate behavior usually resulting in an abnormal exit.
As well as all of the features of earlier versions of Ged2Web, Ged2Web 2.51 can import notes related to either individuals, or events associated with individuals, from GEDCOM files and export them to the created web pages. Notes relating to a relationship between two people such as marriage notes or relating to an event associated with a relationship such as a divorce will not be imported.
Creating notes pages is optional so that note pages can be omitted if web space is limited.
Ged2web is a shareware program to convert one or more GEDCOM files into a set of HTML pages that can be published on the Web. Version 2.1 has been enhanced in the following ways over version 1.1: