Person ID: I9 | Tree: test1 |  Last Modified: 11 Jan 2001
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
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
General Custom Filelinks
1872 - 1941 (Age 69)
Birth
1872
Died
7 Dec 1941
Father
Standard GEDCOM Filelinks b. 1835
Mother
Torture GEDCOM Matriarch b. 12 Feb 1840
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 "Standard GEDCOM Filelinks" INDIVIDUAL Record.
The GEDCOM standard lets you link records to multimedia objects kept in separate files. When GEDCOM 5.5 was released, it only mentioned allowing links to a small number of multimedia files types and some of them are Windows-only file types. The recommended list is
bmp - Windows but map file
gif - Bit map, 256 color GIF files (common on the Internet)
jpeg - Bit-mapped files developed for photographs (also common on the Internet)
ole - Linked object
pcx - Windows paintbrush file
tiff - Tagged image format file
wav - Windows sound file
This INDIVIDUAL record has links to this limited set of multimedia files (except for ole). These links 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 files links to this small set of file types. It does not allow for future file types and, for example, it ignores movie files types. You can visit the "Nonstandard Multimedia Filelinks" record to see links to other types of multimedia files. You can visit the "General Custom Filelinks" and the "Extra URL Filelinks" records to see links to any file type and to universal resource locators.
NOTE: The path names for the linked files here are just the file names. A good GEDCOM program should search for the files and might look first in the same folder as this test GEDCOM file. A weaker program might be unable to locate these files and you will have to enter the full path names.
EMBEDDED Multimedia Object:
GEDCOM 5.5 has a method for encoding multimedia objects and storing them in MULTIMEDIA Records. This INDIVIDUAL has a link to such an embedded object. The object has encoded data, written using the GEDCOM 5.5 encoding algorithm, for the image of a small flower. To my knowledge, there are no genealogy programs that can actually read and decode such objects. The main reason for inclusion of the object here is to see how programs will treat this record. Good programs will leave them in the file (it is bad manners to delete someone's data). Bad programs will simple delete the object from the file.