Release Notes for rootstrust, Version 0.9 beta, Build 379
1. GEDCOM import issues with Milennia Legacy:
a. The _PREF and _ORDER tags, which have no rootstrust counterparts, were erroneously being treated as Events. They are now ignored.
b. The “_MARRIED N” Event is converted to “Non-Marital Relationship”.
c. The _NONE tag is converted to a “Number of Children None” fact.
d. The _PLAC_DEFN tag is used to identify each Place referenced in the GEDCOM file. If the GEDCOM file references “San Francisco, CA” multiple times, for example, there will be only one _PLAC_DEFN for it. Subordinate to these _PLAC_DEFN tags can be found geocoordinates (latitude and longitude) and/or notes. Prior to this build rootstrust would freeze, if it encountered geocoordinates subordinate to a _PLAC_DEFN. That error has been corrected.
e. In a situation where both the birth parents on adoptive parents of a child are given, rootstrust was not creating the parent-child relationships correctly. This problem has been corrected.
f. rootstrust was not recognizing custom Event type declarations in version 5.5 GEDCOM files generated by older versions of Legacy (version 2.0 specifically). The custom Events were being displayed in the Event Summary with the Event field (Event type name) being blank. This problem has been corrected.
g. Legacy GEDCOM files can contain invalid, ambiguous dates with the format “01 JAN 2000-01 FEB 2000”. The GEDCOM specification permits:
i. “FROM 1 JAN TO 1 FEB 2000” meaning a period of time starting Jan. 1, 2000 and extending to
Feb. 1, 2000.
ii. “BET 1 JAN AND 1 FEB 2000” meaning some point in time between Jan. 1, 2000 and Feb. 1, 2000.
If rootstrust encounters a date in the invalid format, it converts it to the “FROM…TO” format and writes a message to the GEDCOM Import Log. You need to check each of these entries and change those to “type ii, above” that do not refer to an extended period of time.
2. Cameo Photo Management. The term ‘Cameo’ refers to the photo image that can be displayed in the small, square panel on the Person View located to the left of the Name plate. The process of preparing and installing a cameo photo has been greatly simplified. To create, select, replace or delete a cameo photo click the cameo panel with either the left or right mouse button to display a popup menu. The menu commands are:
a. Delete cameo photo. Deletes the cameo photo currently displayed replacing it with empty, light gray space.
b. Select a cameo photo. Displays a dialog box for selecting a photo image to be used as a cameo photo.
c. Create cameo by selecting, cropping & resizing a photo. Displays a dialog box for selecting a photo image. It then displays the selected image in a resizable form that has a square selection frame superimposed on top of the photo image. The selection frame can be resized using the mouse wheel and dragged around the image by clicking inside it and moving the mouse while the mouse button is depressed. When you have framed the portion of the selected photo that you would like to use as a cameo photo, click the OK button. The image inside the selection frame will be resized to 150 x 150 pixels, the exact size of the cameo photo panel, stored in a file within the current Person’s personal photo (or combined) directory and displayed in the cameo photo panel.
3. Right Click Menu Changes. The popup menu that is displayed in response to a right click of the mouse when a multi-line text field is in focus has been changed:
a. The accelerator keystrokes for the standard system editing operations (copy, cut, paste, find) have been changed to conform to operating system conventions:
Editing Pre-389 New New
Function Accelerator Windows & Linux Mac OS X
Copy Alt+C Ctrl+C command+C
Cut Alt+X Ctrl+X command+X
Paste Alt+V Ctrl+V command+V
Find Alt+F Ctrl+F command+F
b. Two new commands have been added:
Function Windows & Linux Mac OS X
Paste unformatted Ctrl+Alt+V command+alt+V
Visit website Alt+W alt+W
“Paste unformatted” allows you to paste text that you have copied from a web page but without any markup (font, color, underlining, bold, etc.)
“Visit website” replaces the older feature that automatically loaded a website into your browser when you right clicked on a text field the contained a web address. It turn out that that feature conflicted with the right click popup menu such that the menu could not be used if the text field contained a web address – each attempt to display the menu simply reloaded the website into the browser rather than displaying the menu. Now you must use the menu command or the accelerator (Alt W) to visit the website. For the sake of consistency, this behavior has also been applied to single-line text fields that do not support enhanced text.
4. GEDCOM-X. The FamilySearch Family Tree project was implemented using the GEDCOM-X specification which is considerably different from GEDCOM 5.1. In the process of modifying rootstrust to communicate with FamilySearch.org the following changes have been made for the sake of compatibility:
a. The following rootstrust Event type names have been modified in order to conform to the corresponding GEDCOM-X names:
i. Draft Notice → Military Draft Notice
ii. Draft Registration → Military Draft Registration
iii. Military → Military Service
iv. Stillborn → Stillbirth
b. The following new GEDCOM-X Event types have been added to rootstrust:
v. Gender Change
viii. Marital Status
ix. Marriage Notice
xi. Military Induction
xii. Multiple Birth
c. The following new GEDCOM-X Name types have been added to rootstrust:
i. Death name
ii. Formal name
d. The rootstrust general Event Role name ‘Subject’ has been changed to the GEDCOM-X value ‘Principal’.
5. New Demo Videos. I have added the following videos to the Demo Videos menu:
6. Miscellaneous Fixes and Modifications.
a. In order to prevent accidental termination of rootstrust, a confirmation dialog is now displayed in response to you attempting to exit via the menu command, the Alt+X accelerator or the system close button (the one next to the minimize and maximize buttons).
b. A program error was corrected that was preventing custom markers (Military, Public Service, Miscellaneous and Biomedical) from being saved to the database.
c. The GEDCOM Import Log values for "Convert '?' to 'possibly'” and "Convert periods to commas” were reversed. This has been corrected.
d. The Place column of the Event Summary on the Person View has been modified to accept the contents of the Event’s Description field, if no Place has been assigned to the Event. This is particularly useful if you have opted to display Attributes as Events and these Attributes have no Place but do have a value in the Description field (Occupation, Number of Children, Hair Color, etc.).
e. rootstrust was not recognizing input from 16-bit Unicode GEDCOM files. rootstrust initially opens the GEDCOM file as a UTF-8 (8-bit Unicode) file. A line in the header of the GEDCOM file specifies which character set was used, e.g. “1 CHAR UNICODE”. If it is not UTF-8, rootstrust closes the file and reopens it with the correct character set. If a 16-bit Unicode file is opened as though it had 8-bit encoding, the character set declaration appears as “1 C H A R U N I C O D E “ instead of “1 CHAR UNICODE”. rootstrust now recognizes that condition and switches properly to the Unicode character set.
f. A “Treat Attributes as Facts” check box has been added to the “User Interface” tab of the Preferences form. If checked, Attribute type Events that have neither date nor Place will be displayed in the Facts tab rather than the Events tab of the Person View.
g. When rootstrust was modified to allow for ‘unknown’ as a value for Sex in addition to ‘male’ and ‘female’, not all references to the two-sex system were updated to the three-sex system. Hopefully the changes made in this build have finalized that conversion.
h. The Place Preprocessor was terminating with a “null pointer exception” when processing a GEDCOM file from TMG with the “Structured” option for Places having been selected in the GEDCOM Import Wizard. This problem no longer occurs.
i. The Place Preprocessor now automatically converts abbreviations for states and provinces to the full names (NY à New York; ON à Ontario). However, standard abbreviations will still be used in the “Short Name” (Jamaica, NY; London, ON, Canada).
j. The Place index on the Place Merge form is now sorted irrespective of case. In Build 378 “new York, NY” and “New York, NY” would not have adjacent entries. “new York, NY” would have followed “Zimbabwe”.
k. GEDCOM import will now only save a “Long Name” field for a Place, if it different than the “Short Name”.
l. In prior builds, if a Person was married, the spouse’s name was not known and there were no known children, the text box or combo box next to the Spouse: label button would erroneously read “The father of” or The mother of” instead of being blank. This error has been corrected.
m. The data format “1 January 2000” was displaying as “1 JANUARY 2000”. This error has been corrected.
n. A typographical error in the sentence template for the Employment Event type has been corrected. ‘<Plave>’ was changed to ‘<Place>’.
o. The default female Event Role for the Baptism Event type was ‘Principal’ rather than ‘Recipient’, the default male role. They are now identical.
p. This build contains the latest version of Oracle Java (1.8 update 45).
7. What will be in the next build?
a. Fixes to any problems that you report.
b. Work on the rootstrust to FamilySearch interface continues, but at a disappointingly slow pace due to poor documentation.
c. As promised, I will complete the user interface for Facts. You currently can only view Facts. In the near future you will be able to add, edit and delete same.
d. I will try to implement an eighth view: the Descendant View. It will function in a manner similar to the Tree Chart View.