The blood line relative always appears first - including adoptions.

When a female marries to begin a new branch of both her's and her husband's family trees, the new FAMILY NAME, IN ALLCAPS, always precedes the first name of the wife.  All SURNAMES should appear in ALLCAPS format, but older trees may not reflect this more recent decision.

Otherwise, LAST NAMES are shown only when the spelling is noteworthy or for branches unconnected to the main blood line.  When known, the spelling reflected on the most applicable document is used.  When unknown, and there's more than one indicated in varying source documents, the presumed most ancient spelling is used.  The french Ç takes precedence over the english S, and so on.  ( I'm unaware of the history behind the phonetically identical T and TH, but presume it's related to the way french was written in different regions of the country.  That doesn't mean the person with the name spelled that way came from that region - only that the person "writing the name" preferred that region's method.  In many cases, the surnamed individuals couldn't read nor write and were at the mercy of those who could. )

The CCYYMDD date format means Century Century Year Year Month Day Day

Century digits are shown only at the beginning of each entry, except for:
   deaths before adulthood
   persons living 100+ years.

When a birth/death date is unkown but the baptism/burial-2nd+Marriage is, then the - (minus sign) following the date may be indicative of same.  

Mulitiple marriages for either spouse are indicated by a b c d, etc., immediately preceding the (sur)name of the blood relative.

Marriages of two blood line spouses are reflected in each entry by the birth year sequenced 'blood line' ancestry; such as 1601-44-61-93-1711, which could also be shown as
  1601JeanTERRIAU
  -1644THIBODEAUjeanne
  -1661LANDRYmarie
  -1693LeBLANCfrancoise
  -1711GAUTEROTagnes
  (see1667GAUTEROT), but isn't unless required for discussion purposes outside the tree itself.

Children resulting from the marriages of two blood line spouses are reflected under the most ancient line, normally the husband's.

Exclamation points, oftentimes following dates, indicate that the supposed typo or duplication is in the source document.  Presumably, unless the source document comments on that duplication, it's a typo.

Non-standard (english) lettering, such as the french Ç or ç, is avoided within names upon which subsequent searches will be done.  The Acadian spellings have enough variety without adding foreign letters to make the process gometrically that much more complex!

Spaces are not used.  [ Trees get too big with them included.  Some other characters are not allowed by Windows Explorer within file/folder names and some others, which are allowed, such as the period '.' and double spaces cause problems during the BACKUP.EXE process and are avoided.  The total of any cumulative lineage within Windows Explorer using the BACKUP.EXE process should be less than around 228 characters.  What's seen in the uploaded images is a condensed version of what actually appears in the Family Tree Folder on the hard drive. ]

(Anything in parentheses is uncertain, an alternative to what's shown, or it's simply noteworthy.)

Conflicts are decided in favor of the source with more information.  For example, (1601-37-62-)1693cMELANÇON marie63123 & 91cPaulPierre74-m12n08 derived from the Terriot.ged file is listed in favor of 1687MELANSONmarie & 91PaulPierre74-m12n08 obtained from the Melanson.html file.  The detailed death date in the former, presumably more accurate french spelling of the phonetically identical name and more youthful age at marriage (given the subsequent number of children surviving into adulthood - nine) bias the initial decision in favor of the Terriot.ged data.
    In the example above, the four extant 1601-37-62-87-... references were changed to 1601-37-62-93-... in the main tree.  By the time the process is completed, the uploaded tree images should reflect the best guess dates.

• click the    x    under the column to place the object page there;

• click the middle image/URL to place the object page in an unframed window, or in the case of another menu, in the same left or right (smaller) menu frame now extant;
• click the  X  under the column to place the object page there;

(Re-sizing frames is always allowed by moving the vertical separation bar.  Closing frames mode is allowed by clicking the closeFrames image at the bottom of pages where it's found.)

The search engines, for example, are formatted to fit in one menu frame.  Searches on any given spelling of a name, with EACH SEPARATE SEARCH ENGINE, can be accomplished without losing the contents of the menu frame.  Users can repeatly click URLs in the to see the results without changing the contents of the , When that process gets too far along, one need merely reclick the original search request to get back to the starting point.  In addition, after an hour or so in the researching some facinating information, the user needn't remember what was already done in the , because the contents will still be there.