Torture GEDCOM Matriarch

Family/Spouse: Standard GEDCOM Filelinks. Standard was born in 1835. [Group Sheet] [Family Chart]

Notes:

Comments on "Extra URL 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) or even to limit them to local files. This INDIVIDUAL record has a series of links with universal resource locators (URL) in the FILE tag and the file "URL" in the FORM tag.

The sample URL links include links to a web sites, a link to an FTP site, and a link to send email.

This extension of file links to URL links is non-standard GEDCOM. What will a genealogy program do when in encounters URL file links? Cleaver programs will find the file on the Internet using your default browser, FTP program, or email program. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).

Notes:

Comments on "Nonstandard Multimedia 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 file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks" for those file types). This INDIVIDUAL record has links to other types of multimedia files including movie files, other image file types, and some Macintosh file types.

What will a genealogy program do when in encounters to 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).

Some other possible multimedia file type not yet linked to this record are:
avi - Microsoft movie file
midi - sound file
mp3 - music file

Family/Spouse: Unknown. [Group Sheet] [Family Chart]

Notes:

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).

Notes:

Comments on "Charlie Accented ANSEL" INDIVIDUAL Record.

To represent accented characters, the ANSEL character set uses two-byte codes. The first byte is E0 to FB or FE (hexadecimal); the second byte is the letter to be accented.

These notes have all possible accented characters. How many of the characters are represented correctly? Even programs that fully support ANSEL will not draw all these accented characters correctly. Many of them correspond to accents that can not be found in any langauge and therefore do not correspond to any computer fonts.

code: E0 (Unicode: hook above, 0309) low rising tone mark