The following hardware and software is required for UncleGED 9:
Supported Operating Systems: Windows 2000 Service Pack 3; Windows 98; Windows 98 Second Edition; Windows ME; Windows Server 2003; Windows Vista Business; Windows Vista Business 64-bit edition; Windows Vista Enterprise; Windows Vista Enterprise 64-bit edition; Windows Vista Home Basic; Windows Vista Home Basic 64-bit edition; Windows Vista Home Premium; Windows Vista Home Premium 64-bit edition; Windows Vista Starter; Windows Vista Ultimate; Windows Vista Ultimate 64-bit edition; Windows XP Service Pack 2
Optional Requirements:
Run Uncle GED by selecting from the Start Menu | Programs |Uncle GED.
The configuration options dialog is divided into nine sections:
When you first run UncleGED you may need to make adjustments to the configuration options.
These configuration options are saved in a UncleGED Project file (.ugproj). The default project file is called "_default.ugproj". With project files you can create "projects" with different settings, different GEDCOM input files, and different HTML target directories.
Use the "Open Project" menu item to open other previously saved projects. The "Save Project" menu item saves the currently opened project. The "Save Project As…" menu item saves the currently opened project with a different filename.
For details on each of the configuration options in UncleGED see page 19.
For more information please visit the Frequently Asked Questions (FAQ) page at http://gatheringleaves.org/content/view/102/119/
After making any changes to the configuration settings, click the "Build Pages" button to start reading the GEDCOM file and building your web pages.
The HTML files will be created in the html directory (normally "My Documents\My UncleGED\html").
Each time you generate HTML pages UncleGED will write those pages to the directory that you specify on the "Projects" tab of the Configuration Options dialog.
If the page style is set to Family Pages…
For each family found your GEDCOM file there will be a corresponding famxxx.html file. In other words if there are 300 families in your GEDCOM file, you will find 300 files labeled fam001.html to fam300.html.
If the page style is to Person Pages…
UncleGED will build one or more pages depending on the number of individuals in your GEDCOM. Each page will contain an person entry for each individuals up to number of max individuals per page as specified on the Person Page tab.
sources.html |
Sources from your GEDCOM file |
surnames.html |
A listing of all of the surnames found in your GEDCOM file |
ind_indx.html |
Alphabetical index of all individuals found in you GEDCOM file. |
index.htm |
This acts as a Table Contents for all of the HTML files produced by UncleGED. |
You will also find the following files depending on options that were selected: stats.htm, occupations.htm, locations.htm, and chronology.htm
You may view these files using a web-browser such as Internet Explorer or Netscape Navigator.
Where's does the output go? By default it goes into the "html" sub-directory under the UncleGED directory. By default this would be "My Documents\My UncleGED\html". However this directory can be changed to any valid directory by changing the "HtmlPath" entry.
Use any web browser to to view the HTML pages produced by UncleGED.
As of UncleGED 4.01 you may now specify the main page title.
Extra text to be displayed on the main table of contents page.
If you fill in home page setting under Author's information a link to this page will be added to the table contents page (index.htm). Prior to rel. 4.01 this pointed to ../index.htm. You may now link to any page that you wish. if left blank, the link will not be added to the page.
This option setting is found on the Author tab just beneath the "Home Page". If this option is selected then all "Home" and "Table of Contents" links will point the URI specified in the "Home Page" entry. If this option is not selected then default index.htm becomes the target of "Home" and "Table of Contents".
When this option is selected, Uncle GED displays the Author's name and email within a copyright statement at the bottom of each page.
Use background image (images/ug_bkgrd.gif).
With this option the ug_bkgrd.gif file will be used as the background for all HTML files produced by UncleGED.
Use banner image (images/ug_banner.gif).
With this option the ug_banner.gif file will be used as the banner for all HTML files produced by UncleGED.
When this option is selected, Uncle GED creates a listing file when HTML pages are created. This listing file is a comma-delimited file that lists the individual's name, their RIN, and which HTML they appear in. Look for list.txt in the UncleGED application directory.
When this option is selected, Uncle GED creates a statistics page that lists the following item. Look for stats.htm in the HTML directory :
When this option is selected, Uncle GED creates a GENDEX file called GENDEX.txt in the html directory.
Other report files created by UncleGED are:
Mark information for individuals currently living as private. With this option on any data (notes, etc.) for individual with a valid birth date less than 80 years will be marked as private. [private]. However to best address privacy issues it better to filter your GEDCOM at the time that you export it from your genealogy software.
Excludes notes from HTML pages. With option set to true any notes found in the GEDCOM file are excluded from the HTML pages
Display Most Recent Change Date On Family Pages - When this option is selected, Uncle GED displays the most recent change date at the bottom of each family page.
Example:
The most recent update of information contained on this page was on: 15 July 2001
The date displayed here is determined by examining the change dates stored in the GEDCOM file for each of the individuals displayed uniquely on this page.
Display Last Update For Individual On Index - Besides displaying the individual's name and birth date on the index, Uncle GED optionally displays the last date that this individuals record was updated.
Make Bold Most Recent Updates On Index - When this option is selected along with the option described above, Uncle GED will display all changes made in the last 90 days in formatting in bold.
NOTE: The change dates are provided in GEDCOM files created with PAF and may not be in files produced by other software vendors. For change dates UncleGED looks for something like the following in the GEDCOM file:
1 CHAN
2 DATE 24 Feb 2002
3 TIME 12:34:12
Display RIN After Name - When this option is selected, Uncle GED displays the RIN (individual reference number) after each individuals name.
Display MRIN After Marriage - When this option is selected, Uncle GED displays the MRIN in the title of the family HTML page.
Displays surnames in upper-case.
When this option is selected, Uncle GED adds all surnames found with a count greater than five to the Meta sections of the index page….
Example….
<META NAME="keywords" CONTENT="genealogy,geneology,GENEALOGY,GENEOLOGY,ancestry,family history,heritage,family tree ,DEBACKER,LEE,DOBBS,O'MALLEY,GAUME,DEDONDER,PESSEMIER,KOLLROS,BANNON,SMITH, NIX,FAIVER,LINDEMAN,REBILLOT,PROTHRO"> <META HTTP-EQUIV="keywords" CONTENT="genealogy geneology GENEALOGY GENEOLOGY ancestry family history heritage family tree">
When this option is selected, Uncle GED adds a count to each surname displayed on the surname page.
Create Chronology Of Events Page - When this option is selected, Uncle GED will create a Chronology of Events page.
The following options are available for creating a listing of locations and place names. An example of this page can be found at Example Locations Page. Selecting the "Create Locations Page" option will not only create this style of HTML page, but will also create a file called "loc_report.txt". The "loc_report.txt" provides a listing of all locations and place names found in your GEDCOM file and can be useful in locating problems with place names in the GEDCOM.
Create Locations Page - creates the files listed in the paragraph above.
List Locations In Reverse Order - when selected an entry such as "Houston, Harris, Texas" will be displayed as "Texas, Harris, Houston".
Display Event Dates On Locations Page - displays a date (if available) between the individuals name and the event description.
Estimated Locations - Although not a part of the GEDCOM specification, there is a format used by the LDS in Ancestral files for entering "estimated" locations and that is to enter the location surrounded by the "<" and ">" characters. UncleGED automatically converts the "<" and ">" characters to "[" and "]" characters.
The following options regarding estimated locations are as follows:
Do Not List Estimated Locations - locations surrounded by the "[" and "]" characters are not displayed.
Treat Estimated Locations The Same As Actual Locations - the "[" and "]" characters are dropped from the estimated locations and all locations are displayed together.
List Estimated Locations At Bottom Of Page - locations surrounded by the "[" and "]" characters are retained and are displayed at the bottom of the page.
The following options are available for creating a listing of occupations. An example of this page can be found at Example Occupations Page.
Create Occupations Page - creates the occupation.html file.
Do Not Print Occupations On Locations Page - Occupation listing are excluded from the Locations page (If the source of your GEDCOM file is FTW (Family Tree Maker) then set this option to true; otherwise leave cleared ).
Occupation Location Equals Occupation Text - This rather wordy option basically means that both the location and the description of the occupation are within the same field in the GEDCOM file. (If the source of your GEDCOM file is FTW (Family Tree Maker) then set this option to true; otherwise leave it cleared).
Numbering of family page files is dependent on the family record number (MRIN). Each family stored in a GEDCOM file is assigned a MRIN. How these numbers are assigned depends on the software that you are using to create the GEDCOM. Normally MRIN #1 would the first family you created in your database, but some genealogy software programs are not consistent with maintaining MRINs. Therefore there may or may not be a fam001.htm.
On the table contents page created by UncleGED (index.htm) there is a link labeled "Family Pages". This link points to the lowest numbered family (MRIN) found in your GEDCOM.
I tried the following experiment involving MRINs and the numbering of family pages. I built a test database in both FTW and PAF. I added individuals/families to both databases in exactly the same order and at various steps I exported both files out to a GEDCOM and compared the two. In no case did either of the programs change the MRINs. I tried all sorts of additions to both files and could not get them to change the MRINs.
However I did find a case where FTW will change the MRIN. The version of FTW that I have (7.0) basically only gives me two options for exporting out to GEDCOM: export everything or export one particular branch. With PAF I can use filters to select individuals based on certain criteria. The filter that I used for my webpages is only if the birth date is earlier than 1910.
I did an full export from FTW and compared that with a partial (single branch) export from FTW and sure enough the MRINs were changed. I also noticed that from within FTW I can't even see what the RINs/MRINs are. Whereas PAF both are displayed all over the place. I think that basically the architecture of the FTW database does not care about MRINs, whereas PAF is closely tied to maintaining the MRINs. So there's really no blame to FTW; it's just built differently.
Can the MRIN be changed? No, neither PAF, FTW, nor Legacy allows you to do this.
The list report file will allow you track which HTML file an individual appears in. For each individual this will list either display the individual's parent's family file or the individual's family file depending on the individual's recorded marriage status.
The help authoring tool from Microsoft, HTML Help Workshop, can be used as an easy-to-use system for compiling your HTML files into a standard format used by the Microsoft Operating system for displaying on-line documentation (aka Help Files).
In order to compile your HTML files you will need to download and install the free HTML Help Workshop from Microsoft.
To compile your HTML files using UncleGED:
With the "Compile HTML" option selected UncleGED will create all of the files needed to produce the compiled HTML file (.chm) and will invoke the HTML Help Compiler after it has completed the generation of the HTML files. The compiled HTML file will be located in the same directory as the HTML files and will have the same name as your GEDCOM file with the .chm extension.
Below are some frequently asked questions regarding UncleGED:
No. However there are the configuration options in UncleGED that do some filtering: the "Privacy" option and the "ExcludeNotes" options , but these options either mark an individual as private (displaying only the indvidual's name), exclude all notes or excludes an individual (and associated information) based on birth date. It is best to use whatever export filtering options that your genealogy software provides. It some cases you may need to edit the GEDCOM file by-hand which I realize may be daunting task for some.
2. I have recently upgraded the operating system on my PC and I use older genealogy software that does not run under the new operating system. As a result I cannot open my Family Tree files. Will using Uncle GED allow me to do this?
UncleGED is designed to do one thing: read and process a GEDCOM and output the information found in the GEDCOM file to HTML format. If your "family tree" files are in GEDCOM format then UncleGED can read the files, but that is probably not what you actually want to do. Different genealogy software packages store the genealogy data in a native format specific to each program. Some store the data in a proprietary format; while others may use some standard format such as Dbase or MS Access. Some genealogy programs can read the native format of other genealogy programs and allow you to import directly from the other guy's format. For the most part all genealogy programs can import and export the GEDCOM format. Therefore the best advice is to back-up your genealogy data by exporting it to GEDCOM. This way if you switch from one genealogy program to another you should be able to import your GEDCOM file into the new program with little effort.
3. UncleGED takes too long to process my GEDCOM file. Is there anything that I can do to speed things up?
Yes, two things a) Run UncleGED on a PC with a faster processor and more memory or b) Use a GEDCOM file with fewer families and individuals
4. UncleGED produces way too many HTML files. Is there anything that I can do to reduce the number of HTML files produced by UncleGED?
Yes, use a GEDCOM file with fewer families and individuals.
5. I have noticed that the first "family" file (famxxx.html) produced by UncleGED is not named "fam001.html". Also the numbering of the files seems to skip in places. Why is this?
UncleGED numbers each family file using the MRIN (marriage reference identifier) assigned to each family in the GEDCOM file. This numbering is controlled by two factors a) the genealogy program that was used to produce the file and b) any filtering that was applied to the data when the GEDCOM file was exported. In most genealogy programs you have no control over the MRIN numbering and MRINs are usually assigned on a first-come/first-serve basis. If you export only a sub-set of your genealogy data out to GEDCOM the resulting file may or may not have an MRIN # 1 in the file and there may be gaps in the numbering of HTML files.
6. How can I find out which HTML file has a specific individual in it?
When UncleGED builds the HTML files it creates a text file called "list.txt". This file can be found in the UncleGED application directory (the directory where UncleGED is installed). This file lists the individual by name, REFN, and html file.
7. I have 300 families in my database, yet after running UncleGED I find that there are more than 300 famxxx.html files in the html output directory. Why is this?
Each time you run UncleGED it writes the html files into the html directory. If there are already html files in the directory, UncleGED will over-write existing files with new files of the same name. If none of the existing html files correspond to the new files they will remain untouched. You can sort the directory contents to determine which ones are new files and which ones are left-overs, but it is probably best to just delete all of the existing html files before doing new run.
8. I used UncleGED to create a set of HTML files for my website. On other web-pages on my website I provided links to specific famxxx.html pages created by UncleGED. Later on I made changes to my genealogy database, generated a new GEDCOM file and processed this file with UncleGED. Now the links on my other pages are broken. The file numbering has changed. What happened?
Two things can cause this to happen: 1) Not all genealogy software packages use the MRIN numbering system used in the GEDCOM format. In this case the genealogy software generates the MRIN numbers when you export the file out to GEDCOM and in most cases the MRIN numbering will not change from export to export, but some changes made to the database such as the deletion of families can cause the MRIN numbers to changes. 2) Importing one GEDCOM into an existing genealogy database will cause the existing MRIN numbering in the import file to change. (see also response to question #5).
9. Okay, I created the HTML files, now what? How do I publish these files to the World Wide Web? 10. I have a website. How do I get all of these HTML files on to my website? 11. UncleGED produced a ton of HTML files and I've tried uploading the files to my website via FTP, but it is just not working. Why is that?
Before you can publish to the World Wide Web you first need a website where you can publish the files. For this you will need to either check with your ISP (internet service provider) to see if they have already provided you with a website or space on a website or contact a IPP (internet presence provider) and inquire about establishing your own domain name and website. Once you have a place to put your files you'll need to know how upload (install) the files on your website. Again check with your ISP or IPP to find out how this is done. Problems with uploading a large number of files via FTP to a website are quite common. Many IPPs limit the amount of data that can be uploaded per day or per month. Some limit the duration of each FTP session to few minutes. Also you need to consider how much space is available to you on your website. You can determine how much space is required for the HTML files generated by UncleGED by using the Windows Explorer. Right-click the html directory and from the pop-up menu select properties. The properties dialog box will tell you how space the contents of the html directory take-up.
12. There are notes in my genealogy database that are either not showing up in the HTML files produced by UncleGED or they are showing up the wrong places. Why is that?
Not all genealogy software packages handle notes in the same way. Notes that appear in one field in a GEDCOM export may appear under a different field in another GEDCOM export depending on the genealogy program used to produce the GEDCOM file. Compounding this is the fact that not all users of genealogy software use the documentation features of the genealogy program in the same way. UncleGED uses a couple of tricks to try and get around these differences and attempt to find the notes in a GEDCOM file. One example of this is the "OccLocEqualsOccText" option in the UncleGED configuration. When this option is set to true it will correct a problem found in GEDCOM files produced with Family Tree Maker (FTW) where the occupation location and occupation description are found in the same field in the GEDCOM file. Similar issues have been noticed in other genealogy software such as Legacy or PAF and UncleGED does look for a "signature" in the header portion of the GEDCOM to determine which genealogy software was used to produce the GEDCOM. UncleGED recognizes Family Tree Maker, Legacy and PAF and adjusts accordingly to deal with differences between these software programs and the way in which each one "does" notes. As these are the only genealogy software programs that I have access to, I am not able to design UncleGED to deal with the particular way in which any other programs output their data to GEDCOM. If all else fails, try sending me a sample GEDCOM to look at and I will see about making changes to UncleGED to handle these differences in other programs. Don't just send a partial GEDCOM file as I will need to test with a complete GEDCOM file. Also, the sample GEDCOM need not be and probably should NOT be a full export from your database.
There is also a command-line version of UncleGED (uged.exe) available in the directory where UncleGED is installed. The command-line version works exactly like the GUI version and can be used for batch operations.
UncleGED - Ver. 9.0.12.2 (RELEASE)
GEDCOM-To-HTML
Copyright c 1999-2007 D. M. DeBacker
USAGE: uged.exe /f[gedcom file] {/c[config]}|{options}
/w - Used alone to create a default XML config file
OPTIONS:
BOOLEAN OPTIONS - These act as switches that reverses the default setting
-ac - AddUserCopyright (default:False)
-ak - AddKeywords (default:True)
-an - AddSpaceToConc (default:False)
-as - AddSurnameCount (default:True)
-cl - ChronoLinks (default:True)
-cp - CreateChronoPage (default:True)
-de - DoDateEstimation (default:False)
-dm - DisplayMRIN (default:True)
-dr - DisplayRIN (default:True)
-gf - CreateGendexFile (default:False)
-hr - HiLiteMostRecent (default:True)
-io - IgnoreOccupations (default:True)
-ld - LocDisplayEventDates (default:False)
-lo - LocReverseOrder (default:True)
-lp - CreateLocPage (default:True)
-lr - CreateListReport (default:True)
-lt - OccLocEqualsOccText (default:False)
-mi - MostRecentOnIndex (default:True)
-mp - MostRecentOnPage (default:True)
-op - CreateOccupationsPage (default:True)
-pr - Privacy (default:True)
-sc - SurnamesAllCaps (default:True)
-sp - CreateStatsPage (default:True)
-st - LocStripTrailingPunc (default:False)
-ub - UseBackground (default:True)
-ur - UseBanner (default:True)
-ut - UseTagToText (default:False)
-xl - ExcludeLivingIndividualsAfterBirthCutOff (default:False)
-xn - ExcludeNotes (default:False)
COMMAND OPTIONS - These require additional input
-b[BackgroundFile] - BackgroundFile
-c[ChronoCutOff] - ChronoCutOff
-e[AuthorsEmail] - AuthorsEmail
-h[HtmlPath] - HtmlPath
-m[MaxIndiPerPage] - MaxIndiPerPage
-n[AuthorsName] - AuthorsName
-p[FamFilePrefix] - FamFilePrefix
-r[BannerFile] - BannerFile
-s[0|1|2] - LocEstimateMethod
-t[MainPageTitle] - MainPageTitle
-u[AuthorsUrl] - AuthorsUrl
-y[BirthCutOffYears] - BirthCutOffYears
-w[0|1] - [Web]PageStyle
HINT: uged /?| MORE displays Help one screen at a time.
See the documentation for more details regarding uged options
Below are all of the configuration options for UncleGED release 9. These options are listed by the key name as found in the project configuration file (EX. _default.ugproj).
false |
The GEDCOM tag CONC is meant to be an indication that the current text is to be concatenated with any previous note text however many genealogy software package do ignore this rule and use CONC when they should use CONT. The prevent the text from the previous note text being concatenated with the the current line of note text set this property to true.
"" |
Extra text to appears on the Chronology of Events page.
"Chronology Of Events" |
The title of the Chronology of Events page.
Allows you to change the wording or even the language of the labels that appear of the Persons pages
"" |
Extra text to appears on the Locations page.
"Locations" |
The title of the Locations page.
"" |
Extra text that appears of the main table of contents page.
"+" |
Mark "symbol" that appears on the persons page beside a person's name which indicates that more information appears on the linked page for this person.
50 |
Specifies the maximum number of persons to display on the persons page.
0 |
Specifies whether the file extension for the web pages where zero (0) = .html and 1 = .htm.
0 |
Specifies the page style where 0 = the classic Family Pages and 1 = the Persons Pages introduced in rls 9.
"" |
Extra text to appears on the Stats page.
"Statistics" |
The title of the Stats page.
false |
The tag-to-text file (tagtotext.txt) allows for changing the wording or even the language for GEDCOM tags found the GEDCOM data file.
false |
This option setting is found on the Author tab just beneath the "Home Page". if this option is selected then all "Home" and "Table of Contents" links will point the URI specified in the "Home Page" entry. If this option is not selected then default index.htm becomes the target of "Home" and "Table of Contents".
false |
This option setting is found on the Persons Page tab. If this option is selected then all small, three level pedigree is displayed on for each person on the person pages.
FALSE |
Surnames As Keywords On Index Page. When this option is selected, Uncle GED adds all surnames found with a count greater than five to the Meta sections of the index page….
FALSE |
Add Surname Count to Surnames Page. When this option is selected, Uncle GED adds a count to each surname displayed on the surname page.
FALSE |
When this option is set to TRUE, Uncle GED displays the Author's name and email within a copyright statement at the bottom of each page. See AuthorsEmail and AuthorsName.
{blank} |
The email address of the web pages' author
{blank} |
The web pages' author's name
{blank} |
A link to this page will be added to the table contents page (index.htm). Prior to rel. 4.01 this pointed to ../index.htm. You may now link to any page (URL) that you wish. If left blank, the link will not be added to the page.
images/ug_bkgrd.gif |
Relative or absolute URL location of background file
images/ug_banner.gif |
Relative or absolute URL location of banner file
1900 |
Last date (year) for the chronology listings. Any year after the ChronoCutOff date will not be listed in the chronology.
TRUE |
Adds links for the family pages to the chronology, occupations and locations pages.
FALSE |
Create Chronology Of Events Page - When this option is selected, Uncle GED will create a Chronology of Events page.
FALSE |
When this option is selected, Uncle GED creates a GENDEX file called GENDEX.txt in the HTML directory. For more information on GENDEX files and their purpose visit
Welcome to GENDEX .
FALSE |
When this option is set to TRUE, Uncle GED creates a listing file when HTML pages are created. This listing file is a comma-delimited file that lists the individual's name, their RIN, and which HTML they appear in. Look for list.txt in the HTML directory.
FALSE |
There are a number of options available for creating a listing of locations and place names. Selecting the "Create Locations Page" option will not only create this style of HTML page, but will also create a file called "loc_report.txt". The "loc_report.txt" provides a listing of all locations and place names found in your GEDCOM file and can be useful in locating problems with place names in the GEDCOM. Setting CreateLocPage to true creates the files listed above.
FALSE |
Create Occupations Page - creates the occupation.html file.
FALSE |
When this option is selected, Uncle GED creates a statistics page that lists the statistics for the GEDCOM file. Look for stats.htm in the HTML directory.
FALSE |
Display MRIN after marriage - When this option is selected, Uncle GED displays the MRIN (marriage reference number) in the title of the family HTML page.
FALSE |
Display RIN after name - When this option is selected, Uncle GED displays the RIN (individual reference number) after each individuals name.
FALSE |
Excludes notes from HTML pages. With option set to true any notes found in the GEDCOM file are excluded from the HTML pages
fam |
As of UncleGED 5, the "family file prefix" feature allows the user to designate a 3 character naming convention for the files. This is useful if you want to split your maternal and paternal lines. For example I have one set of files that follow the pattern of debxxx.html for my father's side and another set with the pattern dobxxx.html for my mother's. If you set this three character prefix to something other than "fam" (for example "deb") then all famxxx.html files become debxxx.html and the other files will have the family file prefix prepended to them (for example locations.html becomes deb_locations.html and so forth).
TRUE |
Make Bold Most Recent Updates On Index - When this option is selected along with the MostRecentOnIndex option, Uncle GED will display all changes made in the last 90 days in formatting in bold. NOTE: The change dates are provided in GEDCOM files created with PAF and may not be in files produced by other software vendors. For change dates UncleGED looks for something like the following in the GEDCOM file: 1 CHAN 2 DATE 24 Feb 2002 3 TIME 12:34:12
{app path\}html |
Specify the directory to which the family pages and other HTML files (UncleGED output) will be written.
FALSE |
Do Not Print Occupations On Locations Page - Occupation listing are excluded from the Locations page (If the source of your GEDCOM file is FTW (Family Tree Maker) then set this option to TRUE; otherwise leave FALSE).
FALSE |
Display Event Dates On Locations Page - displays a date (if available) between the individuals name and the event description.
0 |
Estimated Locations - Although not a part of the GEDCOM specification, there is a format used by the LDS in Ancestral files for entering "estimated" locations and that is to enter the location surrounded by the "<" and ">" characters. UncleGED automatically converts the "<" and ">" characters to "[" and "]" characters. The following options regarding estimated locations are as follows: 0. Do Not List Estimated Locations - locations surrounded by the "[" and "]" characters are not displayed. 1. Treat Estimated Locations The Same As Actual Locations - the "[" and "]" characters are dropped from the estimated locations and all locations are displayed together. 2. List Estimated Locations At Bottom Of Page - locations surrounded by the "[" and "]" characters are retained and are displayed at the bottom of the page.
TRUE |
List Locations In Reverse Order - when selected an entry such as "Houston, Harris, Texas" will be displayed as "Texas, Harris, Houston".
Family Page |
As of UncleGED 4.01 you may now specify the main page title.
TRUE |
Display Last Update For Individual On Index - Besides displaying the individual's name and birth date on the index, Uncle GED optionally displays the last date that this individuals record was updated.
TRUE |
Display Most Recent Change Date On Family Pages - When this option is selected, Uncle GED displays the most recent change date at the bottom of each family page. Example: The most recent update of information contained on this page was on: 15 July 2001. The date displayed here is determined by examining the change dates stored in the GEDCOM file for each of the individuals displayed uniquely on this page.
FALSE |
Occupation Location Equals Occupation Text - This rather wordy option basically means that both the location and the description of the occupation are within the same field in the GEDCOM file. (If the source of your GEDCOM file is FTW (Family Tree Maker) then set this option to true; otherwise leave cleared ).
TRUE |
Mark information for individuals currently living as private. With this option on any data (notes, etc.) for individual with a valid birth date less than 80 years the birth date only will be marked as private. [private]. However to best address privacy issues it better to filter your GEDCOM at the time that you export it from your genealogy software.
FALSE |
Display Surnames In Upper-Case
TRUE |
When set to true the Sources ("Bibliography ") Page is opened in a new browser window.
FALSE |
Use background image (images/ug_bkgrd.gif). With this option the ug_bkgrd.gif file located normally "C:\PROGRAM FILES\UNCLEGED\HTML\IMAGES" will be used as the background for all HTML files produced by UncleGED. NOTE: As of UncleGED 4.01, you may specify any background image and location for that image that you wish.
FALSE |
Use banner image (images/ug_banner.gif). With this option the ug_banner.gif file located normally "C:\PROGRAM FILES\UNCLEGED\HTMl\IMAGES" will be used as the banner for all HTML files produced by UncleGED. NOTE: As of UncleGED 4.01, you may specify any banner image and location for that image that you wish. The size that I used for my banner is 224 X 38, but you may use any size that you like.
FALSE |
Use cascading style sheet - When set to true UncleGED will add the following line to each web page:
<LINK REL = stylesheet TYPE = text/css href=uged.css>
This will allow you to use a cascading style sheet named uged.css to change the appearance of the web pages that UncleGED produces. Example if the uged.css file contains:
body{font-family: Arial;}
This will change the font from the default to Arial.
DIV.HOUSEHOLD |
section at top of family page that describes the household. |
DIV.CHILDREN |
section in family page that lists the children in household |
DIV.OTHERMARRIAGES |
section of family page that begins "Other Marriages for…" |
DIV.EVENTS |
section of family page that begins "Notes for…" |
DIV.NOTES |
section of family page where note text is displayed. |
DIV.SOURCES |
section of family page that begins "Sources for…" |
TABLE.CHILDRENTABLE |
table of children in the household |
DIV.UPDATE |
section at bottom of page that has the line "Last Updated On…" |
DIV.MENU |
section at bottom of page that lists a menu of back links |
DIV.COPYRIGHT |
section at bottom of page that displays the copyright |
DIV.INDSECTION |
section of Person page for each individual |
DIV.INDINFO |
section of Invidual that appears as for example F, #I1, b. 24 May 1819, d. 22 January 1901 |
DIV.FAMILYSECTION |
section of invidual listing family details |
DIV.EXTRATEXT |
section of Extra text that appears on pages |
H2.INDNAME |
Name of each individual appearing on Persons page |
Below is a sample CSS that will display a silver 'Lucida Calligraphy' font on maroon background:
body
{
color: silver;
font-family: 'Lucida Calligraphy';
background-color: maroon;
}
A:link
{
color: #99ffcc;
}
A:visited
{
color: #ff66cc;
}
A:active
{
color: red;
}
DIV.HOUSEHOLD
{
}
DIV.CHILDREN
{
}
DIV.OTHERMARRIAGES
{
}
DIV.EVENTS
{
}
DIV.NOTES
{
font-size: larger;
}
DIV.SOURCES
{
}
TABLE.CHILDRENTABLE
{
font-variant: small-caps;
}
DIV.UPDATE
{
}
DIV.MENU
{
}
DIV.COPYRIGHT
{
font-size: 10pt;
font-style: italic;
}
DIV.INDSECTION
{
}
DIV.INDINFO
{
}
DIV.FAMILYSECTION
{
}
DIV.EXTRATEXT
{
}
H2.INDNAME
{
}