Person ID: I11 | Tree: test1 |  Last Modified: 11 Jan 2001
Extra URL Filelinks
1875 -
Birth
1875
Father
Nobility title Prof. Joseph Tag Torture, Jr. b. 31 Dec 1965, Salt Lake City, UT, USA
Mother
Mary First Jones b. Bef 1970
Married
31 Dec 1997
The place
Agency: Catholic Church
Cause: Love
Address: A Church Main Street, USA
Divorced
31 Dec 1997
The place
Father
Standard GEDCOM Filelinks b. 1835
Mother
Torture GEDCOM Matriarch b. 12 Feb 1840
Nonstandard Multimedia Filelinks
1870 - Yes, date unknown
Birth
1870
Died
Yes, date unknown
Father
Standard GEDCOM Filelinks b. 1835
Mother
Torture GEDCOM Matriarch b. 12 Feb 1840
Children
1. Charlie Accented ANSEL b. 15 Jun 1900
Standard GEDCOM Filelinks
1835 -
Birth
1835
Family
Torture GEDCOM Matriarch b. 12 Feb 1840
Children
1. Extra URL Filelinks b. 1875
2. Nonstandard Multimedia Filelinks b. 1870
3. General Custom Filelinks b. 1872
Torture GEDCOM Matriarch
1840 - 1915 (Age 75)
Birth
12 Feb 1840
Died
15 Jun 1915
Family
Standard GEDCOM Filelinks b. 1835
Children
1. Extra URL Filelinks b. 1875
2. Nonstandard Multimedia Filelinks b. 1870
3. General Custom Filelinks b. 1872
This mod changes the layout of the Person Profile in several ways,
with the intent of making it easier to read. For example,
It moves some the profiled person's events below the person's Parent and Family data,
Adds headings (e.g. Parents, Family or Families, Media, Event Map) above each block of data, and
Moves 'metadata' (e.g. the personID, date of last change, and links to the Group Sheet and Family Chart) into headings.
It makes numerous additional changes, some of which are controlled by mod options.
See the Wiki article for details.
This mod changes the layout of Event dates and places,
combining them into one cell so that the date never wraps.
It also tries to move the event text (not the comment) onto that same line.
It's fairly subtle; see the mod's Wiki article for details.
Comments on "General Custom Filelinks" INDIVIDUAL Record.
File links in GEDCOM are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag. It does not make sense to limit file links to the small set of multimedia file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks" for those file types). The INDIVIDUAL record "Nonstandard Multimedia Filelinks" has sample links to other types of multimedia files not included in the standard GEDCOM list. This INDIVIDUAL record has links to some non-multimedia files types.
What will a genealogy program do when it encounters such logical extensions to GEDCOM file links? Good programs will follow the links. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).