Header record

Tag

Data content

0 HEAD

empty

1 GEDC

empty

2 VERS

must be '5.5'.

2 FORM

must be 'LINEAGE-LINKED'.

1 CHAR

Character set; if unknown, a dialog for determining the character set will open. See About character sets below.

2 VERS

Code page number for ASCII or ANSI character sets.

1 SUBM @XRef@

Reference to a submitter record.

1 NOTE

FamilyTreeFactory imprint description.

2 CONT

Continuation of FamilyTreeFactory imprint description in the same line.

2 CONC

Continuation of FamilyTreeFactory imprint description in a new line.

Submitter record

Tag

Data content

0 @XRef@ SUBM

empty

1 NAME

FamilyTreeFactory imprint, author.

1 ADDR

FamilyTreeFactory imprint, address (line 1).

2 CONT

FamilyTreeFactory imprint, address (line 2).

2 CONT

FamilyTreeFactory imprint, address (line 3).

Individual record

Tag

Data content

0 @XRef@ INDI

Each individual record has a continuous FamilyTreeFactory record number, starting with 1. If the number of individual records exceeds the maximum number of persons allows in FamilyTreeFactory, conversion will be stopped.

XRef is only written to the FamilyTreeFactory ID code if this has been specified in Gedcom Options, Import Options tab.

1 NAME

NAME must have the form 'Given Name(s) /Surname/'. Given name(s) will become FamilyTreeFactory given name(s). /Surname/ will become an alternate FamilyTreeFactory maiden name if a married name tag is defined and saved. Otherwise, /Surname/ will become the current/last FamilyTreeFactory surname if a married name tag is not defined or is empty. See About preferred given name coding and About married name coding below.

If a suffix is following the surname ('Given Name(s) /Surname/ Suffix') it is added at the end of the FamilyTreeFactory surname or given name depending of what has been specified under Gedcom Options, Import Options tab.

If multiple NAME tags are present, only the first one is normally used. Under Gedcom Options, Import Options tab, you can specify whether a second NAME tag should be written to the FamilyTreeFactory married name.

2 NPFX

Entry in FamilyTreeFactory occupation or title depending of what has been specified under Gedcom Options, Import Options tab.

2 GIVN

as above for given name(s) if NAME tag is empty. See About preferred given name coding below.

2 NICK

FamilyTreeFactory nickname. See About preferred given name coding below. Under Gedcom Options, Import Options tab, you can specify whether an _AKA tag or an ALIA tag should be written to the FamilyTreeFactory nickname instead of the NICK tag. See also _AKA tag and ALIA tag.

2 SPFX

Prefix for SURN if NAME tag is empty. If NAME tag is not empty: The content of this tag is inserted before the FamilyTreeFactory surname if this has been specified under Gedcom Options, Import Options tab.

2 SURN

as above for /Surname/ if NAME tag is empty.

2 NSFX

Suffix for SURN if NAME tag is empty. If NAME tag is not empty: The content of this tag is added at the end of the FamilyTreeFactory surname if this has been specified under Gedcom Options, Import Options tab.

2 _AKA

Special PAF5 tag 'also known as' (such as artist name), becomes FamilyTreeFactory note with text 'Also known as'.

See About preferred given name coding below. This tag is written to the FamilyTreeFactory nickname field if this has been specified under Gedcom Options, Import Options tab. See also NICK tag and ALIA tag.

2 ALIA

FamilyTreeFactory nickname (see also NICK tag and _AKA tag), or FamilyTreeFactory surname variation, if this has been specified under Gedcom Options, Import Options tab.

1 ALIA

FamilyTreeFactory nickname (see also NICK tag and _AKA tag), or FamilyTreeFactory surname variation, if this has been specified under Gedcom Options, Import Options tab.

1 SEX

FamilyTreeFactory gender: 'M' = 'male', 'F' = 'female'. Other data or missing gender data are considered 'unknown'.

1 BIRT

A 'Y' or 'Yes' behind this tag is not processed.

2 DATE

FamilyTreeFactory date of birth.

2 PLAC

FamilyTreeFactory place of birth.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory birth data source).

3 CONC

Continuation of birth data source in the same line.

3 CONT

Continuation of birth data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory birth data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 RELI

FamilyTreeFactory religion.

2 PLAC

Special setting for FTM Gedcom files, if this has been specified under Gedcom Options, Import Options tab: FamilyTreeFactory religion.

1 CHR

A 'Y' or 'Yes' behind this tag is not processed. Any previously accepted CHRA or BAPM tag will be overwritten.

2 DATE

FamilyTreeFactory date of baptism.

2 PLAC

FamilyTreeFactory place of baptism.

2 _GODP

FamilyTreeFactory godparents. See About godparent coding below.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory baptism data source).

3 CONC

Continuation of baptism data source in the same line.

3 CONT

Continuation of baptism data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory baptism data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 CHRA

A 'Y' or 'Yes' behind this tag is not processed. Any previously accepted CHR or BAPM tag will be overwritten.

2 DATE

FamilyTreeFactory date of baptism.

2 PLAC

FamilyTreeFactory place of baptism.

2 _GODP

FamilyTreeFactory godparents. See About godparent coding below.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory baptism data source).

3 CONC

Continuation of baptism data source in the same line.

3 CONT

Continuation of baptism data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory baptism data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 BAPM

A 'Y' or 'Yes' behind this tag is not processed. Any previously accepted CHR or CHRA tag will be overwritten.

2 DATE

FamilyTreeFactory date of baptism.

2 PLAC

FamilyTreeFactory place of baptism.

2 _GODP

FamilyTreeFactory godparents. See About godparent coding below.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory baptism data source).

3 CONC

Continuation of baptism data source in the same line.

3 CONT

Continuation of baptism data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory baptism data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 DEAT

A 'Y' or 'Yes' behind this tag leads to FamilyTreeFactory date of death "deceased", if no DATE tag with a date of death is available.

2 CAUS

FamilyTreeFactory cause of death. See About cause of death below.

2 DATE

FamilyTreeFactory date of death.

2 PLAC

FamilyTreeFactory place of death.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory death data source).

3 CONC

Continuation of death data source in the same line.

3 CONT

Continuation of death data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory death data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 BURI

A 'Y' or 'Yes' behind this tag is not processed.

2 DATE

FamilyTreeFactory date of burial.

2 PLAC

FamilyTreeFactory place of burial.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory burial data source).

3 CONC

Continuation of burial data source in the same line.

3 CONT

Continuation of burial data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory burial data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 TITL

FamilyTreeFactory title.

1 OCCU

FamilyTreeFactory occupation. Under Gedcom Options, Import Options tab, you can specify whether every line or every attribute is followed by a period. If multiple OCCU tags are present, you can also specify whether only the first tag, all tags, or only the last tag should be accepted.

2 CONC

Continuation of FamilyTreeFactory occupation in the same line.

2 CONT

Continuation of FamilyTreeFactory occupation in a new line.

2 DATE

The occupation date is added to the FamilyTreeFactory occupation, if this has been specified under Gedcom Options, Import Options tab. The date format can be selected under Gedcom Options, Import Options tab.

2 PLAC

The occupation place is added to the FamilyTreeFactory occupation. The output language used for the word 'in' can be selected under Gedcom Options, Import Options tab.

Special setting for FTM Gedcom files, if this has been specified under Gedcom Options, Import Options tab: FamilyTreeFactory occupation.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory occupation data source).

3 CONC

Continuation of occupation data source in the same line.

3 CONT

Continuation of occupation data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory occupation data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 RESI

Data behind this tag will not be processed.

2 PLAC

FamilyTreeFactory place of residence.

2 ADDR

empty

3 CONT

FamilyTreeFactory contact data. See About contact data coding below.

1 _LEBENSORT

Special setting for AF2000 Gedcom files, if this has been specified under Gedcom Options, Import Options tab: FamilyTreeFactory place of residence.

1 _BUERGERORT

FamilyTreeFactory civil rights municipality. See About civil rights municipality coding below.

1 EMIG

Data behind this tag will not be processed.

2 DATE

The emigration date is added to the FamilyTreeFactory note, if this has been specified under Gedcom Options, Import Options tab. The date format can be selected under Gedcom Options, Import Options tab.

2 PLAC

The emigration place is added to the FamilyTreeFactory note, if this has been specified under Gedcom Options, Import Options tab. The output language used for the word 'to' and the handling of comma-separated place levels can be selected under Gedcom Options, Import Options tab.

1 NOTE

FamilyTreeFactory note (see also 'Note reference'). Under Gedcom Options, Import Options tab, you can specify whether every  line or every attribute is followed by a period.

2 CONC

Continuation of FamilyTreeFactory note in the same line.

2 CONT

Continuation of FamilyTreeFactory note in a new line.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory note data source).

3 CONC

Continuation of note data source in the same line.

3 CONT

Continuation of note data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory note data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 NOTE @XRef@

The note reference points to a note record. A maximum of 10 note references will be read.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory note data source).

3 CONC

Continuation of note data source in the same line.

3 CONT

Continuation of note data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory note data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory general data source).

2 CONC

Continuation of general data source in the same line.

2 CONT

Continuation of general data source in a new line.

2 TEXT

Source text.

3 CONC

Continuation of source text in the same line.

3 CONT

Continuation of source text in a new line.

1 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory general data source). A maximum of 10 source references will be read.

2 PAGE

Source page.

2 DATA

empty

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

1 IDNO

FamilyTreeFactory ID code, if this has been specified under Gedcom Options, Import Options tab. See also REFN, RFN, RIN, _UID and @XRef@ INDI.

1 REFN

FamilyTreeFactory ID code, if this has been specified under Gedcom Options, Import Options tab. See also IDNO, RFN, RIN, _UID and @XRef@ INDI.

1 RFN

FamilyTreeFactory ID code, if this has been specified under Gedcom Options, Import Options tab. See also IDNO, REFN, RIN, _UID and @XRef@ INDI.

1 RIN

FamilyTreeFactory ID code, if this has been specified under Gedcom Options, Import Options tab. See also IDNO, REFN, RFN, _UID and @XRef@ INDI.

1 _UID

FamilyTreeFactory ID code, if this has been specified under Gedcom Options, Import Options tab. See also IDNO, REFN, RFN, RIN and @XRef@ INDI.

1 OBJE

Data behind this tag will not be processed. See also 'Object reference'. A maximum of 25 OBJE tags will be read.

2 FORM

File extension; only used to check the file extension of the FamilyTreeFactory photo file or document file.

2 TITL

Only for FamilyTreeFactory document files: FamilyTreeFactory document title.

2 FILE

FamilyTreeFactory photo file name or document file name (without path).

2 _PRIM

Only for FamilyTreeFactory photo files: Special PAF5 tag for marking the primary photo among several photos. If marked with 'Y', the photo file name of this OBJE tag will be marked 'active' in the FamilyTreeFactory photo file list. If marked with 'N', the photo file name of this OBJE tag will not be marked 'active' in the FamilyTreeFactory photo file list. If no photo file name is marked 'active' in the FamilyTreeFactory photo file list, the first photo will automatically be marked 'active'. If more than one photo file name is marked 'active' in the FamilyTreeFactory photo file list, only the first of these will retain the 'active' marking.

2 _TYPE

Object type, defines the classification of the object as FamilyTreeFactory photo file (object type 'PHOTO') or as FamilyTreeFactory document file (object types  'DOCUMENT', 'TEXT', 'IMAGE', 'GRAPHIC', 'SOUND' and 'VIDEO'). For FamilyTreeFactory document files the type is saved as 'Gedcom Type': 'Document' for 'DOCUMENT', 'Text' for 'TEXT', 'Image' for 'IMAGE', 'Graphic' for 'GRAPHIC', 'Audio' for 'SOUND' and 'Video' for 'VIDEO'. If an object with the type 'PHOTO' is found, the image file type of which is not bitmap (*.bmp) and not JPEG file (*.jpg, *.jpeg), it will be classified as a document with the type 'IMAGE'.

1 OBJE @XRef@

The object reference points to an object record. A maximum of 25 object references will be read.

1 FAMS @XRef@

The partnership reference points to a family record in which the person is a partner. For multiple partnerships, the partnership references should be in chronological order. If more than 25 partnership references are saved for a person, conversion will be stopped. FamilyTreeFactory can only manage 25 partnerships per person.

1 FAMC @XRef@

The child reference points to a family record in which the person is a child. If more than 1 child reference is present per person, an additional dialog will ask which pair of parents is to be used for the tree structure. In the dialog, you can specify that the parents who were not used for the tree structure be mentioned in the FamilyTreeFactory note. A maximum of 5 child references will be read.

2 PEDI

PEDI defines the type of child relationship ('birth', 'adopted', 'foster', 'challenged', 'disproved', 'sealing'). This type of child relationship will be shown in the above-named additional dialog to make selection easier for multiple pairs of parents. Additionally this tag is evaluated by the automatic parents selection, if this has been specified under Gedcom Options, Import Options tab.

2 _PRIMARY

'Y' indicates the parents in the family record as 'Primary Parents' (definition of PAF5). This tag is evaluated by the automatic parents selection, if this has been specified under Gedcom Options, Import Options tab.

1 ADOP

Marks an adoption, only together with the tag that follows.

2 FAMC @XRef@

The child reference points to a family record in which the person is an adopted child.

Family record

Tag

Data content

0 @XRef@ FAM

empty

1 HUSB @XRef@

The husband/father reference refers to the individual record of the husband/father. The husband or father's record number becomes the FamilyTreeFactory partner record number for the wife, whose individual record is referenced by the following WIFE tag. The husband/father's record number becomes the FamilyTreeFactory father record number for the children, whose individual  records are referenced by the following CHIL tags.

1 WIFE @XRef@

The wife/mother reference refers to the individual record of the wife/mother. The wife or mother's record number becomes the FamilyTreeFactory partner record number for the husband, whose individual record is referenced by the following HUSB tag. The wife/mother's record number becomes the FamilyTreeFactory mother record number for the children, whose individual  records are referenced by the following CHIL tags.

1 CHIL @XRef@

The child reference refers to the individual record of a child. The child's record number becomes the FamilyTreeFactory child record number for both parents, whose individual records are referenced by the above-named HUSB or WIFE tags. Multiple child references should be listed in chronological order of birth.

1 _STAT

'MARRIED' sets the FamilyTreeFactory status of partnership to 'married'. 'NOT MARRIED' sets the FamilyTreeFactory status of partnership to 'not married'. See About status of partnership below.

1 MARR

A 'Y' or 'Yes' sets the FamilyTreeFactory status of partnership to 'married'. See About status of partnership and About marriage data coding below. Other data than 'Y' and 'Yes' behind this tag are not processed. If two MARR tags are present without a subordinate TYPE tag, both data will be accepted as 'civil' and 'religious' marriage data.

2 DATE

FamilyTreeFactory date of marriage.  'NOT MARRIED' sets the FamilyTreeFactory status of partnership to 'not married'. See About status of partnership below.

2 PLAC

FamilyTreeFactory place of marriage.

2 _WITN

FamilyTreeFactory witnesses. See About witness coding below.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory marriage data source).

3 CONC

Continuation of marriage data source in the same line.

3 CONT

Continuation of marriage data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory marriage data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 DIV

If DIV is 'Y' or 'Yes', FamilyTreeFactory attribute 'Divorced'.

2 DATE

FamilyTreeFactory date of divorce; the FamilyTreeFactory attribute 'Divorced' will also be marked.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory divorce data source).

3 CONC

Continuation of divorce data source in the same line.

3 CONT

Continuation of divorce data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory divorce data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

1 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory general marriage data source).

2 CONC

Continuation of general marriage data source in the same line.

2 CONT

Continuation of general marriage data source in a new line.

2 TEXT

Source text.

3 CONC

Continuation of source text in the same line.

3 CONT

Continuation of source text in a new line.

1 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory general marriage data source). A maximum of 10 source references will be read.

2 PAGE

Source page.

2 DATA

empty

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

Note record

Tag

Data content

0 @XRef@ NOTE

empty

1 CONC

Start or continuation of FamilyTreeFactory note in the same line.

1 CONT

Start or continuation of FamilyTreeFactory note in a new line.

2 SOUR

FamilyTreeFactory sources (entry including sub-tags as FamilyTreeFactory note data source).

3 CONC

Continuation of note data source in the same line.

3 CONT

Continuation of note data source in a new line.

3 TEXT

Source text.

4 CONC

Continuation of source text in the same line.

4 CONT

Continuation of source text in a new line.

2 SOUR @XRef@

The source reference points to a source record (entry including sub-tags as FamilyTreeFactory note data source). A maximum of 10 source references will be read.

3 PAGE

Source page.

3 DATA

empty

4 TEXT

Source text.

5 CONC

Continuation of source text in the same line.

5 CONT

Continuation of source text in a new line.

Object record

Tag

Data content

0 @XRef@ OBJE

empty

1 FORM

File extension; only used to check the file extension of the FamilyTreeFactory photo file or document file.

1 TITL

Only for FamilyTreeFactory document files: FamilyTreeFactory document title.

1 FILE

FamilyTreeFactory photo file name or document file name (without path).

1 _PRIM

Only for FamilyTreeFactory photo files: Special PAF5 tag for marking the primary photo among several photos. If marked with 'Y', the photo file name of this OBJE tag will be marked 'active' in the FamilyTreeFactory photo file list. If marked with 'N', the photo file name of this OBJE tag will not be marked 'active' in the FamilyTreeFactory photo file list. If no photo file name is marked 'active' in the FamilyTreeFactory photo file list, the first photo will automatically be marked 'active'. If more than one photo file name is marked 'active' in the FamilyTreeFactory photo file list, only the first of these will retain the 'active' marking.

1 _TYPE

Object type, defines the classification of the object as FamilyTreeFactory photo file (object type 'PHOTO') or as FamilyTreeFactory document file (object types  'DOCUMENT', 'TEXT', 'IMAGE', 'GRAPHIC', 'SOUND' and 'VIDEO'). For FamilyTreeFactory document files the type is saved as 'Gedcom Type': 'Document' for 'DOCUMENT', 'Text' for 'TEXT', 'Image' for 'IMAGE', 'Graphic' for 'GRAPHIC', 'Audio' for 'SOUND' and 'Video' for 'VIDEO'. If an object with the type 'PHOTO' is found, the image file type of which is not bitmap (*.bmp) and not JPEG file (*.jpg, *.jpeg), it will be classified as a document with the type 'IMAGE'.

Source record

Tag

Data content

0 @XRef@ SOUR

empty

1 AUTH

FamilyTreeFactory sources (entry in FamilyTreeFactory source descriptions including sub-tags as source author).

2 CONC

Continuation of source author in the same line.

2 CONT

Continuation of source author in a new line.

1 TITL

FamilyTreeFactory sources (entry in FamilyTreeFactory source descriptions including sub-tags as source title).

2 CONC

Continuation of source title in the same line.

2 CONT

Continuation of source title in a new line.

1 PUBL

FamilyTreeFactory sources (entry in FamilyTreeFactory source descriptions including sub-tags as source publication).

2 CONC

Continuation of source publication in the same line.

2 CONT

Continuation of source publication in a new line.

1 TEXT

FamilyTreeFactory sources (entry in FamilyTreeFactory source descriptions including sub-tags as source text).

2 CONC

Continuation of source text in the same line.

2 CONT

Continuation of source text in a new line.

1 NOTE

FamilyTreeFactory sources (entry in FamilyTreeFactory source descriptions including sub-tags as source comment).

2 CONC

Continuation of source comment in the same line.

2 CONT

Continuation of source comment in a new line.

About status of partnership:

The status of partnership read last from a tag overwrites a status of partnership read before. In principle, available marriage data or divorce data set the partnership status to 'married'.

About preferred given name coding:

Preferred given names are read from the Gedcom file in accordance with the settings under Gedcom Options, Preferred Given Name Coding tab.

If user-defined tags are activated and the user-defined preferred given name tag 'NICK' is used and a preferred given name is indicated after this type of tag and if this preferred given name is included among the person's given names, this preferred given name will overwrite any other preferred given names that may be present. This is helpful for users who use the NICK tag for preferred given names.

If user-defined tags are active and the user-defined preferred given name tag '_AKA tag-extension' is used (tag-extension such as 'PGName'), this tag will be accepted as a preferred given name tag and not as an _AKA tag. This is helpful for users who use the _AKA tag in PAF for preferred given names (for example, '2_AKA PGName Henry').

Otherwise, a preferred given names in a user-defined GIVN tag will overwrite any other preferred given name in user-defined tag. Also, a preferred given name from a user-defined attribute will overwrite any other preferred given name from an user-defined tag or from an user-defined GIVN tag.

The method 1 or 2 Special Characters in the NAME Tag can also detect a special coding pattern in which the preferred given name is repeated at the end of a list of given names and enclosed in special characters. In this case, the preferred given name is not marked within the list of given names. Example of this kind of NAME tag:

1 NAME GivenName1 GivenName2 GivenName3 "GivenName2" /Surname/

About married name coding:

Married names are read from the Gedcom file in accordance with the settings under Gedcom Options, Married Name Coding tab. Married names can also be read from a second NAME tag if this has been specified under Gedcom Options, Import Options tab.

A married name from a user-defined attribute overwrites any other married name from an user-defined tag. A married name from user-defined tags in the family record overwrites any other married name from an user-defined attribute or from an user-defined tag. A married name from a second NAME tag overwrites any other married name from an user-defined tag, from an user-defined attribute or from user-defined tags in the family record.

In the Gedcom Options, Import Options tab, Handling of Special Gedcom Tags and Data, you can define, that a married name is not accepted, if it equals the maiden name.

About marriage data coding:

Marriage data are read from the Gedcom file in accordance with the settings under Gedcom Options, Marriage Data Coding tab.

About Swiss civil rights municipality coding:

Swiss civil rights municipalities are read from the Gedcom file in accordance with the settings under Gedcom Options, Swiss Civil Rights Municipality Coding tab.

A civil rights municipality from a user-defined attribute will overwrite any other civil rights municipalities from an user-defined tag or from an user-defined tag with subordinate PLAC tag. A civil rights municipality from an user-defined tag with a subordinate PLAC tag overwrites any other civil rights municipalitiy from an user-defined tag.

About godparent coding:

Godparents are read from the Gedcom file in accordance with the settings under Gedcom Options, Godparent Coding tab.

The separator between multiple godparents can be selected in the Program Options, Miscellaneous tab. The separator can be a comma or a semicolon.

Godparent references that are read at a later time will overwrite those written earlier. A godchild reference overwrites other references. Godparent names that are read at a later time will overwrite those written earlier. Godchild names overwrite godparent references.

About witness coding:

Witnesses are read from the Gedcom file in accordance with the settings under Gedcom Options, Witness Coding tab.

The separator between multiple witnesses can be selected in the Program Options, Miscellaneous tab. The separator can be a comma or a semicolon.

Witness references that are read at a later time will overwrite those written earlier. A marriage reference overwrites other references. Witness names that are read at a later time will overwrite those written earlier. Witness names overwrite witness references.

About contact data coding:

Contact data are read from the Gedcom file in accordance with the settings under Gedcom Options, Contact Data Coding tab.

Contact data that are read at a later time will overwrite those written earlier.

About cause of death:

If the CAUS contains only the words 'Killed in action' or 'KIA', the record will be assigned the attribute 'Killed in action'. This will cause a different symbol to be used for text output in the person box. In this case the FamilyTreeFactory Cause of death remains empty.

If CAUS contains one of the texts, which have been entered in the Gedcom Options, Import Options tab, Handling of Special Gedcom Tags and Data, and if the checkbox in front of these texts has been marked, the record will be assigned the attribute 'Killed in action', too.

About DATE tags:

The possible date formats are described in the section Date Formats in FamilyTreeFactory Records and Gedcom Files.

Not evaluable or invalid date text phrases are placed in parentheses in the FamilyTreeFactory date fields. The presence of not evaluable or invalid date text phrases will be noted in the conversion log if the log level of detail has been set to 2 or higher under Gedcom Options, Import Options tab.

DATE tags with date entries from the Hebrew, Julian or French Revolutionary calendars will automatically be converted to date entries in the Gregorian calendar. For example:

About special characters:

The special character '\' is replaced in all Gedcom strings by '/', because this character is used in FamilyTreeFactory for internal programming purposes.

The special characters '<' and '>' are removed from all Gedcom family names and nicknames, because they are used in FamilyTreeFactory for marking preferred given names. Angle brackets around Gedcom date entries (such as '<23 May 1857>') are used in the PAF5 definition to indicate that the date has been calculated. These types of date entries are accepted into FamilyTreeFactory date fields in the same way as those with text additions (such as 'calculated 05/23/1857').

About character sets:

FamilyTreeFactory uses the UNICODE character set for internal operations. The program can read data in UTF-8, UNICODE, ASCII (DOS code pages 437 and 850), ANSEL and ANSI (code page based on installed locale) character sets.

The character set is read from the BOM (Byte Order Mark) of the file if possible. If the file has no BOM the character set is read from the CHAR tag if possible. When opening a file without a BOM and with missing or unknown character set entries in the CHAR tag, a dialog will appear to help you select the correct character set.