Home | Examples | Reviews | Free download | Purchase | Web page help | Program help

HtmlPedigree: How GEDCOM tags are interpreted: 2

Index | Logs | Style | Chart | Tags | Links | Images | Dates | Pages | Home | Search | Miscellaneous

Continued from page 1

Special behaviour

The simplest way of converting a line of a GEDCOM file into information on a web page is just to replace the opening tag by an English version, and to copy the rest of the line (the line's "value") unchanged. For example, the following line:

would be rendered on the web page as:

The program also offers more advanced ways of interpreting the lines of the GEDCOM file. These options can be selected by clicking the "Edit GEDCOM tags" item of the "Tools" menu, selecting a tag in one of the tables, and then clicking the adjacent "Special behaviour" button. This opens a dialogue box in which the behaviour can be specified.

The available options are:

  1. Process dates only. As described above, except that if the tag is "DATE", the date will be processed in the usual way. This is the default behaviour for most tags, except for the examples given below: "BLOB" (4), "EVEN" (9), "FILE" (8), "NAME" (10), "SEX" (6), "TYPE" (7).
  2. Leave value unchanged. This will force all values, including dates, to be copied to the web page unchanged.
  3. Omit this and following lines. The line, and any following lines that are related to it, will be omitted. For example, you may wish to omit from the web pages the identification numbers generated by your genealogy program (indicated by the "RIN" tag) or the record of when the information was last edited (indicated by the "CHAN" tag).
  4. Replace value with specified value. For all occurrences of the chosen tag, the value will be replaced by the one specified. For example, as the program does not process binary data embedded in a GEDCOM file, for the "BLOB" tag it replaces the value by "[Binary data]"
  5. If value matches, replace with corresponding value. If the value matches one of a specified list of values, it is replaced by the corresponding element in a list of replacement values.
  6. If first character matches, replace with corresponding value. If the first character of the value matches one of a list of possibilities, it is replaced by the corresponding element in a list of replacement values. For example, the default behaviour for the "SEX" tag is to replace any value starting with "M" by "Male", and any value starting with "F" by "Female".
  7. If value is a tag name, replace with interpretation. If the value matches one of the standard GEDCOM tags, it is replaced by the English equivalent of that tag. For example, the "TYPE" tag has this behaviour by default, so that
    • 1 TYPE BIRT
    is interpreted as:
    • Type: Birth
  8. If start of value matches, write as hyperlink. The value may be converted into a hyperlink, which will open a new browser window when clicked. This behaviour can be selected either for all occurrences of the tag, or for all cases where the start of the value matches one of a specified list of possibilities. This is the default behaviour for the "FILE" tag. For further information, including links to files on your hard disc, see the section on How files linked from the GEDCOM are processed.
  9. Take interpretation from a following line with a matching tag. The English interpretation of the tag is taken from the value of a following line whose tag matched the specified value. This is best illustrated by an example. The GEDCOM standard suggests that, rather than defining non-standard tags for unusual events, a format similar to this should be used:
    • 1 EVEN
    • 2 TYPE Coronation
    • 2 PLAC Westminster Abbey
    Therefore, by default, the program will take its interpretation of the "EVEN" tag from a following line with the tag "TYPE", and render the example above as:
    • Coronation:
      • Place: Westminster Abbey
  10. If preceding tag matches, process as a personal name. Provided the tag of the preceding line matches one of the specified value - or if no values are specified - the value of this line is treated as a personal name. This means that the surname, indicated in the GEDCOM file by "/.../", is rendered in bold type. For example, by default the program interprets lines containing the "NAME" tag in this way, provided they are preceded by "INDI" for individual, or "SUBM" for submitter.