Results area
The results area include a number of fields with information about each file. This was actually created to help find test files of certain types for Behold, and was left in to be a useful tool for anyone using Behold.
You can sort by any column by clicking on the column header. Clicking the same header again will sort in reverse order. The small arrow up or down (shown above at the right of the Path section of the column header) tells you what is currently the sort column and whether it is sorted up or down.
You can make columns wider or narrower by grabbing and moving the small line between the column headers, or you can double-click on that line to quickly make the column the right size to show the widest entry.
There are other columns to the right. Use the horizontal scroll bar at the bottom of the Results Area to view those columns. For the above example they look like this:
Each row contains:
1. Name: the file name.
2. Path: The folder it is in.
3. Size: The size of the file.
4. Date modified: The same as what Windows explorer gives you.
5. Log File Date: This column will only appear if you have the program Behold installed on your computer. When you read a file with Behold, Behold creates a log file. The date and time the log file was created will be in this column. This allows you to see the last time you loaded that file into Behold.
6. Type: Tells you the type of file. The determination of the type of file is non-trivial, and makes use of many of the best practices developed by Tamura Jones on his Modern Software Experience website at: www.tamurajones.net. The type will identify and display important information about the file. Some genealogy software may have trouble reading or not be able to some of these types of files. Type information includes:
GEDCOM - if it is a standard GEDCOM file
FTW TEXT - a file created by early versions of Family TRee Maker that used full-word descriptive tags instead of short GEDCOM tags
Event GEDCOM - an alternative to GEDCOM created by CommSoft
GEDCOMsp - is a GEDCOM file, but the first line "0 HEAD" has a space at the end of the line, which is technically illegal
Embedded GEDCOM - is a GEDCOM file where the file contains data prior to the "0 HEAD" line that should be first. These files can be created by saving a web page that displays a GEDCOM file to one's computer, or through other accidents.
Version number - The version number of the above file types is displayed. GEDCOM File Finder can display versions right back to GEDCOM 1.0 using the rules of Tamura Jones.
(Not Version number) - The program may claim in its GEDCOM header to be one version, but it sometimes states the wrong version. If this is so, then the incorrect version it states will be listed in parentheses after the correct version, e.g.: 5.5.1 (Not 5.5) - GEDCOM File Finder only searches the header section of the file and if it cannot disagree with the claimed version, then it will not be corrected, e.g.: 5.5. If the program did not claim its version when it should have, then GEDCOM File Finder will display: (not provided)
LINEAGE_LINKED: The GEDCOM header should state in a specific place that it is LINEAGE-LINKED (case does not matter, but the dash does). Some programs mispell the word. If they do, this is displayed after the version number.
Nothing found - is displayed if none of the above is found in a file with a .ged extension.
7. Program: This program and the version number of the program that created the file.
8. Dest: This is the program that the GEDCOM was destined for. Some programs can export their GEDCOM into slightly modified version of GEDCOM that will allow intended programs to read some data in extended formats, but few do this properly. That doesn't really matter though, because most programs do not do take into account the Dest value when reading the data.
9. Char: This is the character set that the GEDCOM specifies it is using. Behold can read all the different character sets. Legal character sets specified in GEDCOM files are: ANSEL, ASCII, UNICODE and UTF-8. Illegal character sets include ANSI, IBM, ISO, LATIN, MAC and variations of both the legal and illegal sets. Typically, most genealogy programs will read files with illegal character sets. Most illegal character sets use the same coding for the basic alphabet, numbers and punctuation. But they may incorrectly display accented characters and other special characters not in common with ASCII.
10. BOM (Byte Order Mark): These are extra characters that are added at the beginning of some files to indicate the encoding of the characters in the file to the operating system. Unicode files usually require these to allow correct interpretation of the particular Unicode format being used. BOMs for most GEDCOM files include: none, UTF-8, UTF-16 big-endian, and UTF16 little-endian. The BOM may or may not conflict with the character set specified in the GEDCOM file if the file was modified in some way, as the BOM and overall encoding of the file can be changed by text editing, emailing, or other means. Usually the BOM can be ignored because the operating system handles it invisibly, but it can cause problems for some genealogy programs.
|