<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <metadata name="menuStrip1.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
    <value>22, 1</value>
  </metadata>
  <data name="analyzeToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>The SQLite ANALYZE command gathers statistics about tables and indices 
and stores the collected information in special tables in the database 
where the SQLite query optimizer can use them to help make better query 
planning choices. After Analyze, some RMtrix and some RootsMagic 
operations may speed up.

After significant changes to the database, Analyze should be run again, to
collect new statistics for the optimizer.

Run De-Analyze to remove the tables Analyze has added to the database.</value>
  </data>
  <data name="setSameDateSortOrderToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Alters SortDates of a set of Fact types to a natural order 
when any pair or more occur on the same date, in this order: 
Stillborn, Birth, Christen, Baptism, Death, Funeral, Cremation, Burial, Obituary, Memorial.

Does not include Family events and cannot handle modified dates:
Before, After, etc.</value>
  </data>
  <data name="birthYearMismatchToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists individuals whose Birth Year is missing from the sidebar 
(and other views and reports where just the YEAR IS outputted) 
or 
mismatches the value that has been stored in the Date field of the Birth fact.</value>
  </data>
  <data name="deathYearMismatchToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists individuals whose Death Year is:
- missing from the NameTable 
(and thus missing from views and reports where just the YEAR is outputted) 
OR 
- mismatches the value that has been stored in the Date field of the Death fact.</value>
  </data>
  <data name="splitSharedToIndividualToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Converts shared events to Individual 'Share' events,
except Census, Residence fact types whose Fact Name is preserved. 

Creates a new Individual Fact Type named and abbreviated 'Share', without the quotes,
if none exists.

Witness not in File and their note is appended to the shared event note
and enclosed in privacy brackets, thus {** ... **}.</value>
  </data>
  <data name="uNDOSplitsAndRESHAREToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Reverses the changes made by SPLIT Shared to Individual.

Requires tables zTmpShareSplit and WitnessTableSafe from the Split query.

Deletes the new Indiv Share, Census and Residence events and 
related citations, media tags and webtags
and restores the Sharings. Sort of an UNDO... but not complete;
the appends to the original fact note remain.</value>
  </data>
  <data name="restoreFromSnapshotToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Restores the Fact Type settings from the snapshot.

If you have added Fact Types since the snapshot,
they should remain undisturbed.

If you have modified any Fact Types since the snapshot,
the modifications will be lost.

If there is no snapshot, you will get an error message.</value>
  </data>
  <data name="mediaListToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists all media and the key link ID to where used.

The results displayed can be copied and pasted 
to Excel which supports the synthesized Hyperlink
column for opening the media file.

A W-I-D-E spreadsheet so use Full Screen.</value>
  </data>
  <data name="rESETMediaTypeToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Sets the MediaType according to the file extension of the media file.

Users can mistakenly add image files to the Media Gallery with the 
wrong MediaType which prevents the images from being used in reports.</value>
  </data>
  <data name="copyFromSharedEventsToPersonToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Creates a media tag, for media already tagged to a shared event,
 to the Persons sharing the event. The Description contains
 the original Description appended with the Person's role name,
 the event the Person shared in and the name(s) of the Principal(s)
 in the event.
 
Use "MediaTags-Delete Personals duplicating Events" to delete tags 
of the sort created by this procedure.</value>
  </data>
  <data name="resolvedDuplicateNamesToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Resolved Duplicate Name Pairs, 
flagged as "Not a Problem" in the ExclusionTable,
resurface as unresolved after a transfer.

This list can help expedite the marking of pairs
in the destination database.</value>
  </data>
  <data name="namelessPeopleDELETEToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>These are records in the PersonTable
for whom there is no corresponding
record in the NameTable and are
irretrievably nameless.

Go ahead and delete them as they serve
no useful purpose and clutter up your
database. </value>
  </data>
  <data name="alternateNamesDELETEOrphansToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Deletes Alternate Names from NameTable
for which no Primary name exists in the 
database.

Orphaned Alternate Names are probably 
harmless, merely cluttering the table.
After deletion it is essential to use RM5's
Rebuild Indexes when resuming work.
DO NOT USE on RM4 databases.</value>
  </data>
  <data name="colorREDToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Deletes Persons and Families from PersonTable and FamilyTable 
respectively for persons with the color code RED.

N.B.: This procedure results in many types of 'phantoms' and should 
be followed by the procedure DeletePhantoms.sql</value>
  </data>
  <data name="groupNamedDELETEToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Deletes Persons and Families from PersonTable and FamilyTable respectively for 
all persons in specific Named Groups having a name starting with #DELETE# .

N.B.: This procedure results in many types of 'phantoms' and should be followed by
the procedure DeletePhantoms.sql </value>
  </data>
  <data name="errorsToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists all Place Details lacking a Place, showing those unused 
by an event (blank Name and Event fields), and those that are 
used by an event
PLUS
Events having Lost Places - no match to the PlaceID in the PlaceTable .

RootsMagic 5 does not preclude the entry in the Edit Person screen 
of a Place Detail for a blank Place.  However, that would seem to
be unintended because such a Place Detail cannot be accessed from
the Place List, despite coming out in a narrative report.

Other Place Details may have become orphaned or Places lost by merges 
and deletions. There is a suspected bug in the RM5.0.2.1  feature for 
splitting a Place into Place + Place Details and merging any resultant 
duplicate places.

The Name-RIN and Event help you to find and give a home to the 
orphan, using RootsMagic.

For those with SQLite savvy, the listed PlaceID values can help with your 
inspection of the database tables:

PlaceID(EventTbl) = PlaceID for the Place to be looked up in the PlaceTable
SiteID(EventTbl) = PlaceID of the Place Detail to be found in PlaceTable
PlaceID(PlaceTbl) should match a non-zero SiteID
MasterID(PlaceTbl) = PlaceID of the Place Detail's parent Place 
   0 = no Place or Place Detail assigned
 &gt;0 = a Place or Place Detail was assigned
 null = value not found
</value>
  </data>
  <data name="orphanedPlaceDetailsListToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists all Place Details lacking a Place,
showing those unused by an event
(blank Name and Event fields),
and those that are used by an event.

The Name-RIN and Event help you to
find and give a home to the orphan, using
RootsMagic.

For those with SQLite savvy, the listed 
PlaceID values can help with your 
inspection of the database tables:

SiteID = PlaceID of the orphaned Place Detail 
MasterID = PlaceID of the missing parent Place
   0 = no Place assigned
 &gt;0 = assigned Place is no longer in PlaceTable</value>
  </data>
  <data name="orphanedPlaceDetailsDeleteToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Deletes UNUSED Orphaned Place Details,
i.e., those in the list with a blank Person and Event, 
NOT those in use by an event.

RM5: use its Rebuild Indexes tool on return

RM4: DO NOT DELETE - risk of uncorrectable index corruption </value>
  </data>
  <data name="orphanedPlaceDetailsToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Place Details having no parent Place in the PlaceTable.

RootsMagic 5 does not preclude the entry in the Edit Person screen 
of a Place Detail for a blank Place.  However, that would seem to
be unintended because such a Place Detail cannot be accessed from
the Place List, despite coming out in a narrative report.

Other Place Details may have become orphaned by merges and 
deletions. There is a suspected bug in the RM5.0.2.1  feature to 
split a Place into Place + Place Details and merging any resultant 
duplicate places.</value>
  </data>
  <data name="paragraphingStripToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Strips out leading and trailing CR/LF and blank spaces from the 
custom fact sentences and fact notes for persons and families.

Repetition may be needed for multiple line feeds.

Paragraphing within the body of a note is unaffected.</value>
  </data>
  <data name="paragraphingAddToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Adds paragraphing after notes of person facts. 

Adds double CR/LFs at the end of each non-empty fact note and then 
attempts to strip them from the last note before the 
beginning of the family notes or children.

Does not yet do such paragraphing for family or children notes.

Run Paragraphing-Strip a couple of times before Add, to
clean out existing paragraphing.</value>
  </data>
  <data name="dummyFamilyAddToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Trick developed by Jerry Bryan to cause Narrative Descendant reports
to output childless, spouseless children in their own generation, along with their
married or parental siblings.
 
Adds dummy familyies for all such children to the FamilyTable.
 
After completing the report, run Dummy Family-Delete.

RISK-AVERSE? Run DF-Add on a copy of the database, do your reports
and then delete the copy rather than running DF-Delete on your
working database.
</value>
  </data>
  <data name="lifeLinesToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Lists all events for all persons whether 
in a database tree or not, including shared 
facts, date, fact detail, site and place, MRIN, 
other parties, and duplication indicator. 

Initially sorted by RIN and Sort Date.</value>
  </data>
  <data name="sourceListToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Go Full-Screen and be patient! 
This is a WIDE spreadsheet and will take a long time 
to re-size, let alone fill for the first time, 
if the database has lots of citations. 

Lists all citations of all sources.</value>
  </data>
  <data name="deletePhantomsToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Cleans database of unused records in many tables,
some of which may give rise to phantoms in displays and reports.

These arise from incomplete cleanup by RootsMagic when 
persons, families, places, sources are deleted directly or by merging 
and, most certainly, by simple SQLite deletions such as DeleteByColorCode.</value>
  </data>
  <data name="makeWebTagsFromCitationCommentsToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Inspects for Citation Comments beginning with "http://" and generates 
a corresponding WebTag. GEDCOMs downloaded from Ancestry.com have this 
characteristic, typically followed by two linefeed-carriage returns that 
are stripped by this query.

Due to limitations of SQLite, should the Comment contain more than the trailing
white space, the complete Comment is placed in the URL field and will 
almost certainly fail to open the web page.</value>
  </data>
  <data name="copyFromCitationsToPersonToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Generates a WebTag for the Individual from all WebTags attached to citations
of that Individual, the Family in which he/she is a spouse, all his/her events
and alternate names. This results in ready access to all the person's WebTags
from the button on the Edit Person screen.</value>
  </data>
  <data name="dELETEDuplicatesToolStripMenuItem.ToolTipText" xml:space="preserve">
    <value>Repeated use of MAKE WebTags from citation Comments 
will result in duplicate WebTags as may some other operations. 

This query eliminates the duplicates by copying the unique WebTags 
to a temporary table, deleting all records from URLTable, and 
copying the records from the temporary table back into URLTable.</value>
  </data>
  <metadata name="menuStrip2.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
    <value>137, 1</value>
  </metadata>
  <metadata name="openRmFileDialog.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
    <value>369, -1</value>
  </metadata>
  <metadata name="statusStrip1.TrayLocation" type="System.Drawing.Point, System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
    <value>520, -1</value>
  </metadata>
  <metadata name="$this.TrayHeight" type="System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
    <value>29</value>
  </metadata>
</root>