Database Section

Overview

The Database Section options determine what data is used to build the site.

Set Database...

Use the Set Database... button to choose a TMG database. TMG Version 4 datasets have the extension ".tmg". For TMG Version 5+ projects, select the project file. Project files have a ".pjc" extension. After you choose a dataset, Second Site displays the path to the dataset in a text field beneath the button.

For TMG Version 5+ projects that contain multiple datasets, Second Site asks which dataset to process. For all TMG Version 5+ projects, Second Site displays the dataset name under the project name.

Show Excluded Data

The Show Excluded Data checkbox controls whether singly-excluded data is included in the output. When unchecked, which is the default value, data preceded by "-" is excluded. When checked, data preceded by "-" is included. Data preceded by "--" (the double exclusion marker) is always excluded.

The Show Excluded Data option affects sentences as well as other data.

Second Site also suppresses data between TMG's sensitive data markers ("{}") and hidden codes ([HID:][:HID]). There is no way to include sensitive, hidden, or doubly-excluded data.

Name tags differ slightly from event tags with regard to exclusion markers in the tag sentence; see the Names section for more information.

Primary Tags Only

The Primary Tags Only checkbox controls whether all tags or primary tags only are included in the output. When unchecked, which is the default value, all tags are included. When checked, only primary tags are included.

Include Witnessed Events

The Include Witnessed Events checkbox controls whether witnessed events are included in the person page entry. The default is checked, and witnessed events are shown.

Tag List

The Tag List controls whether specific tag types are included in the output. Only checked tag types are included. The [Check All] button selects all the tag types. The [Uncheck All] button deselects all the tag types. The [Check BMDB Only] button selects all the Birth Group, Marriage Group, Death Group, and Burial Group tag types, and all other tag types are deselected.

The Tag List in the Database Section is the master Tag Type selection list. If a Tag Type is not selected in this list, tags of that Tag Type will not appear in the site even if a Tag Filter in a Person Entry Tag Group selects the Tag Type.

When new tag types are added to your TMG project, Second Site will select them by default. If you do not want those tag types included, make sure you uncheck the tag type in Second Site.

Omit SortDate-Only Birth Events

The Omit SortDate-Only Birth Events checkbox controls the inclusion of Birth Group events that specify a sortdate only. If checked, Second Site will ignore Birth Group events that

• have no date
• have no place data
• have no memo, and
• have no custom sentence

The default is unchecked.

Omit Non-Primary Parents

The Omit Non-Primary Parents checkbox controls the inclusion of non-primary parent tags. If checked, Second Site will ignore non-primary parent tags. The default is checked.

Some narrative-style Formats do not display parents unless they are included in events as witnesses or via a PAR variable and Omit Non-Primary Parents has no effect when using those Formats.

HTML Character Escapes

TMG's database is limited to the Windows 1252 character set. That character set is limited to about 220 characters, includes all ASCII characters and some other letters used mainly in western European cultures, but does not include the thousands of characters supported by Unicode. To get around that limitation, some TMG users enter HTML character escapes to represent characters that are not included in Windows 1252.

When reading a TMG project, Second Site will convert HTML character escapes in name and place parts to their Unicode equivalents. This provides some support for Unicode in a TMG project, but there are several limitations and other considerations.

• Second Site supports numeric character references only. The text must match one of the following patterns:
  1. A decimal numeric character reference of the form &#NNN; where "NNN" is a decimal number, three to five digits. For example, "←", which is the Unicode character "Left Pointing Arrow", "←".
  2. A hexadecimal numeric character reference of the form &#xHHHH; where "HHHH" is a hexadecimal number, two to four hexadecimal digits (0 to 9 or A to F). For example, "←", which is the Unicode character "Left Pointing Arrow", "←".
• Second Site is limited to 16-bit Unicode character codes. That should be adequate for most European cultures, but excludes some Asian cultures and many emoticons.
• As mentioned above, Second Site only converts HTML character escapes when they appear in name and place parts. HTML character escapes in other locations, such as event memos, will be passed-through as is. That will usually produce acceptable results. Second Site converts HTML character escapes in name and place parts to avoid issues with the Search User Item and the name and place indexes.

• Second Site does not perform Unicode normalization on strings. Even if there are multiple ways of rendering the same character, Second Site leaves the character(s) encoded as they were specified using HTML character escapes in the TMG data.

• If you use HTML character escapes, and you also customize Second Site font choices, make sure you choose fonts that include glyphs for the characters you specify.

Second Site's support for HTML character escapes does not provide full-featured support for Unicode characters in TMG databases. Converting HTML character escapes to Unicode avoids some issues but does not solve all the challenges associated with the lack of Unicode support in TMG.