Set this option if you want to see the name/address of the file submitter and how many records were read. This also gives you the chance to view any errors. Errors encountered during a GEDCOM import are always reported in the GEDERR.TXT file and you can view this file using Windows Notepad by clicking on the Errors button on the statistics form. Very often you will find errors reported which do not affect the integrity of the GEDCOM import. For example, "GIVN" and "SURN" tags are ignored by TreeDraw because a person's name is read from the "NAME" tag.

"Additional data", is GEDCOM data which TreeDraw recognises, but there is no specific field set up for it in "Options | Preferences | GEDCOM". By setting this option any extra data will be added to the appropriate set of notes which you can add to person details or family details in "Options | Preferences | Import fields". See Supported GEDCOM syntax for a list of recognised extra data.

By setting this option any extra data (see above) will be added to the GEDCOM import error file, GEDERR.TXT.

By setting this option any dates encountered which are invalid (eg. they do not conform to the GEDCOM standard date format DD MMM YYYY) are imported but are converted to text without being formatted.

Some programs export notes in GEDCOM files using a CONC tag to split long notes over several lines in the GEDCOM file. Sometimes the program splits the line at a space character, which is not allowed. This makes TreeDraw join two words together when it imports the file. To prevent this, set this option and an extra space character will be inserted at the beginning of every CONC line. This does not affect other types of data which also use the CONC tag.

Set this option if you want TreeDraw to make all imported surnames have all capital letters, irrespective of the case in the GEDCOM file; eg. "Thomas Gordon" imports as "Thomas GORDON".

GEDCOM V5.5 requires that the first occurrence of a series of duplicated tags should be the one that is used in the program. For example, if a person has more than one name then there would be several NAME tags for him in the GEDCOM file. TreeDraw will use the first tag it comes across if the Use first occurrence option is set.

Some previous versions of GEDCOM accepted the last occurrence of multiple tags as the "genuine" one. If this is the case for the GEDCOM file you are importing, set the Use last occurrence option.

GEDCOM files created with the IBMPC character set (usually from a DOS program) may have been written using one of the alternative DOS code pages. These pages are generally used in non-English speaking countries and contain extra characters such as "ã" to cover the additional diacritics used in their language.

You can select one of the following code pages and TreeDraw will convert the incoming extra characters into the appropriate ANSI characters for use in Windows. If you are in doubt about which code page was used to create the GEDCOM file, assume it was 437 English.

 
Code pages supported:

• 437 English
• 850 Latin I
• 860 Portuguese
• 863 Canadian-French
• 865 Nordic

If the program encounters the end of a GEDCOM file before finding the TRLR record, it assumes that the file has been split over more than one disk (or file). You will be prompted to insert the disk containing the next file in sequence. GEDCOM files split into several files are named <filename>.GED, <filename>.G00, <filename>.G01, etc, where <filename>.GED is the filename originally specified for input.

TreeDraw will automatically detect which character set has been used to create the GEDCOM file. ANSI, ANSEL, Unicode, UTF-8, IBMPC (DOS) and Apple MAC are all supported. Please make sure that the GEDCOM file was written using one of these sets.