gedspec 0.2.0

data/spec/fixtures/tcg551_f5.ged

@@ -0,0 +1,11 @@
+0 @F5@ FAM
+1 HUSB @I9@
+1 WIFE @I15@
+1 CHIL @I10@
+1 CHIL @I11@
+1 CHIL @I12@
+1 NOTE @N36@
+1 RIN 5
+1 CHAN
+2 DATE 11 Jan 2001
+3 TIME 16:50:37

data/spec/fixtures/tcg551_head.ged

@@ -0,0 +1,147 @@
+0 HEAD
+1 SOUR GEDitCOM
+2 NAME GEDitCOM
+2 VERS 2.9.4
+2 CORP RSAC Software
+3 ADDR 7108 South Pine Cone Street
+4 CONT Salt Lake City, UT 84121
+4 CONT USA
+4 ADR1 RSAC Software
+4 ADR2 7108 South Pine Cone Street
+4 CITY Salt Lake City
+4 STAE UT
+4 POST 84121
+4 CTRY USA
+3 PHON +1-801-942-7768
+3 PHON +1-801-555-1212
+3 PHON +1-801-942-1148 (FAX) (last one!)
+2 DATA Name of source data
+3 DATE 1 JAN 1998
+3 COPR Copyright of source data
+1 SUBM @SUBMITTER@
+1 SUBN @SUBMISSION@
+1 _HME @PERSON1@
+1 DEST ANSTFILE
+1 DATE 1 JAN 1998
+2 TIME 13:57:24.80
+1 FILE TGC55C.ged
+1 COPR � 1997 by H. Eichmann, parts � 1999-2000 by J. A. Nairn.
+1 GEDC
+2 VERS 5.5
+2 FORM LINEAGE-LINKED
+1 LANG English
+1 CHAR ANSEL
+2 VERS ANSI Z39.47-1985
+1 PLAC
+2 FORM City, County, State, Country
+1 NOTE This file demonstrates all tags that are allowed in GEDCOM 5.5. Here are some comments about the HEADER record 
+2 CONC and comments about where to look for information on the other 9 types of GEDCOM records. Most other records will 
+2 CONC have their own notes that describe what to look for in that record and what to hope the importing software will find.
+2 CONT 
+2 CONT Many applications will fail to import these notes. The notes are therefore also provided with the files as a plain-text 
+2 CONC "Read-Me" file.
+2 CONT 
+2 CONT --------------------------
+2 CONT The HEADER Record:
+2 CONT      This record has all possible tags for a HEADER record. In uses one custom tag ("_HME") to see what the software 
+2 CONC will say about custom tags.
+2 CONT 
+2 CONT --------------------------
+2 CONT INDIVIDUAL Records:
+2 CONT      This file has a small number of INDIVIDUAL records. The record named "Joseph Tag Torture" has all possible 
+2 CONC tags for an INDIVIDUAL record. All remaining  individuals have less tags. Some test specific features; for example:
+2 CONT 
+2 CONT      Name: Standard GEDCOM Filelinks
+2 CONT      Name: Nonstandard Multimedia Filelinks
+2 CONT      Name: General Custom Filelinks
+2 CONT      Name: Extra URL Filelinks
+2 CONT           These records link to multimedia files mentioned by the GEDCOM standard and to a variety of other types of 
+2 CONC multimedia files, general files, or URL names.
+2 CONT 
+2 CONT      Name: Chris Locked Torture
+2 CONT           Has a "locked" restriction (RESN) tag - should not be able to edit this record it. This record has one set of notes 
+2 CONC that is used to test line breaking in notes and a few other text-parsing features of the GEDCOM software. Read those 
+2 CONC notes to see what they are testing.
+2 CONT 
+2 CONT      Name: Sandy Privacy Torture
+2 CONT           Has a "privacy" restriction (RESN) tag. Is the tag recognized and how is the record displayed and/or printed?
+2 CONT 
+2 CONT      Name: Chris Locked Torture
+2 CONT      Name: Sandy Privacy Torture
+2 CONT      Name: Pat Smith Torture
+2 CONT           The three children in this file have unknown sex (no SEX tag). An ancestor tree from each should give five 
+2 CONC generations of ancestors.
+2 CONT 
+2 CONT      Name: Charlie Accented ANSEL
+2 CONT      Name: Lucy Special ANSEL
+2 CONT           The notes in these records use all possible special characters in the ANSEL character set. The header of this file 
+2 CONC denotes this file as using the ANSEL character set. The importing software should handle these special characters in a 
+2 CONC reasonable way.
+2 CONT 
+2 CONT      Name: Torture GEDCOM Matriarch
+2 CONT            All individuals in this file are related and all are descendants (or spouses of descendants) of Torture GEDCOM 
+2 CONC Matriarch. A descendant tree or report from this individual should show five generations of descendants.
+2 CONT 
+2 CONT --------------------------
+2 CONT FAMILY Records:
+2 CONT      The FAMILY record for "Joseph Tag Torture" (husband) and "Mary First Jones" (wife) has all tags allowed in 
+2 CONC family records. All other family records use only a few tags and are used to provide records for extra family links in 
+2 CONC other records.
+2 CONT 
+2 CONT --------------------------
+2 CONT SOURCE Records:
+2 CONT      There are two SOURCE records in this file. The "Everything You Every Wanted to Know about GEDCOM Tags" 
+2 CONC source has all possible GEDCOM tags for a SOURCE record. The other source only has only a few tags.
+2 CONT 
+2 CONT --------------------------
+2 CONT REPOSITORY Record:
+2 CONT      There is just one REPOSITORY record and it uses all possible tags for such a record.
+2 CONT 
+2 CONT --------------------------
+2 CONT SUBMITTER Records:
+2 CONT      This file has three SUBMITTER records. The "John A. Nairn" record has all tags allowed in such records. The 
+2 CONC second and third submitter are to test how programs input files with multiple submitters. The GEDCOM standard does 
+2 CONC not allow for notes in SUBMITTER records. Look in the "Main Submitter" to verify all address data comes through, 
+2 CONC that all three phone numbers appear, and that the multimedia file link is preserved.
+2 CONT 
+2 CONT --------------------------
+2 CONT MULTIMEDIA OBJECT Record:
+2 CONT      The one MULTIMEDIA record has all possible tags and even has encoded data for a small image of a flower. There 
+2 CONC are no known GEDCOM programs that can read or write such records. The record is included here to test how 
+2 CONC programs might respond to finding multimedia records present. There are possible plans to eliminate encoded 
+2 CONC multimedia objects in the next version of GEDCOM. In the future all multimedia will be included by links to other files. 
+2 CONC To test current file links and extended file links, see the "Filelinks" family records described above.
+2 CONT 
+2 CONT --------------------------
+2 CONT SUBMISSION Record:
+2 CONT      The one (maximum allowed) SUBMISSION record in this file has all possible tags for such a record.
+2 CONT 
+2 CONT --------------------------
+2 CONT NOTE Records:
+2 CONT      This file has many NOTE records. These are all linked to other records.
+2 CONT 
+2 CONT --------------------------
+2 CONT TRLR Records:
+2 CONT      This file ends in the standard TRLR record.
+2 CONT 
+2 CONT --------------------------
+2 CONT ADDITIONAL NOTES
+2 CONT      This file was originally created by H. Eichmann at <h.eichmann@@mbox.iqo.uni-hannover.de> and posted on the 
+2 CONC Internet.
+2 CONT 
+2 CONT (NOTE: email addresses are listed here with double "at" signs. A rule of GEDCOM parsing is that these should be 
+2 CONC converted to single "at" at signs, but not many programs follow that rule. In addition, that rule is not needed and may be 
+2 CONC abandoned in a future version of GEDCOM).
+2 CONT 
+2 CONT This original file was extensively modified by J. A. Nairn using GEDitCOM 2.9.4 (1999-2001) at 
+2 CONC <support@@geditcom.com> and posted on the Internet at <http://www.geditcom.com>. Some changes included many 
+2 CONC more notes, the use or more tags, extensive testing of multimedia file links, and some notes to test all special ANSEL 
+2 CONC characters.
+2 CONT 
+2 CONT Feel free to copy and use this GEDCOM file for any  non-commercial purpose.
+2 CONT 
+2 CONT For selecting the allowed tags, the GEDCOM standard Release 5.5 (2 JAN 1996) was used. Copyright: The Church of 
+2 CONC Jesus Christ of Latter-Day Saints, <gedcom@@gedcom.org>.
+2 CONT 
+2 CONT You can download the GEDCOM 5.5 specs from: <ftp.gedcom.com/pub/genealogy/gedcom>. You can read the 
+2 CONC GEDCOM 5.5 specs on the Internet at <http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm>.

data/spec/fixtures/tcg551_i13.ged

@@ -0,0 +1,13 @@
+0 @I13@ INDI
+1 NAME Lucy Special /ANSEL/
+1 SEX F
+1 BIRT
+2 DATE 12 AUG 1905
+1 DEAT
+2 DATE 31 DEC 1990
+1 FAMS @F6@
+1 NOTE @N25@
+1 CHAN
+2 DATE 11 Jan 2001
+3 TIME 16:00:23
+1 RIN 2

data/spec/fixtures/tcg551_m1.ged

@@ -0,0 +1,19 @@
+0 @M1@ OBJE
+1 TITL Dummy Multimedia Object
+1 FORM PICT
+1 BLOB
+2 CONT .HM.......k.1..F.jwA.Dzzzzw............A....1.........0U.66..E.8
+2 CONT .......A..k.a6.A.......A..k.........../6....G.......0../..U.....
+2 CONT .w1/m........HC0..../...zzzzzzzz..5zzk..AnA..U..W6U....2rRrRrRrR
+2 CONT .Dw...............k.1.......1..A...5ykE/zzzx/.g//.Hxzk6/.Tzy/.k1
+2 CONT /Dw/.Tvz.E5zzUE9/kHz.Tw2/DzzzEEA.kE2zk5yzk2/zzs21.U2/Dw/.Tw/.Tzy
+2 CONT /.fy/.HzzkHzzzo21Ds00.E2.UE2.U62/.k./Ds0.UE0/Do0..E8/UE2.U62.U9w
+2 CONT /.Tx/.20.jg2/jo2..9u/.0U.6A.zk
+1 NOTE Here are some notes on this multimedia object.
+2 CONT If decoded it should be an image of a flower.
+1 REFN User Reference Number
+2 TYPE User Reference Type
+1 RIN 1
+1 CHAN
+2 DATE 14 Jan 2001
+3 TIME 14:10:31

data/spec/fixtures/tcg551_n2.ged

@@ -0,0 +1,20 @@
+0 @N2@ NOTE
+1 CONC Comments on "Family History Library" REPOSITORY Record.
+1 CONT 
+1 CONT This record uses all possible GEDCOM tags for a REPOSITORY record. Some 
+1 CONC things to look for are:
+1 CONT 
+1 CONT 1. The address is specified twice. Once in a multi-line address record and once in 
+1 CONC separate lines. The first method is usually enough. The second method is to be more 
+1 CONC specific about parts of the address. Is everything imported?
+1 CONT 
+1 CONT 2. There are multiple phone numbers. Are they all imported?
+1 SOUR @SOURCE1@
+2 PAGE 1
+2 DATA
+3 DATE 1 MAY 1999
+3 TEXT Text from the source about this repository.
+2 QUAY 3
+1 CHAN
+2 DATE 12 Mar 2000
+3 TIME 11:44:05

data/spec/fixtures/tcg551_r1.ged

@@ -0,0 +1,21 @@
+0 @R1@ REPO
+1 NAME Family History Library
+1 ADDR 35 North West Temple
+2 CONT Salt Lake City, UT 84111
+2 CONT USA
+2 ADR1 35 North West Temple
+2 ADR2 Across the street from Temple Square
+2 CITY Salt Lake City
+2 STAE Utah
+2 POST 84111
+2 CTRY USA
+1 PHON +1-801-240-2331 (information)
+1 PHON +1-801-240-1278 (gifts & donations)
+1 PHON +1-801-240-2584 (support)
+1 NOTE @N2@
+1 REFN User Ref Number
+2 TYPE Sample
+1 RIN 1
+1 CHAN
+2 DATE 12 Mar 2000
+3 TIME 10:36:02

data/spec/fixtures/tcg551_sm2.ged

@@ -0,0 +1,9 @@
+0 @SM2@ SUBM
+1 NAME Secondary Submitter
+1 ADDR Secondary Submitter Address 1
+2 CONT Secondary Submitter Address 2
+1 LANG English
+1 CHAN
+2 DATE 12 Mar 2000
+3 TIME 10:38:33
+1 RIN 2

data/spec/fixtures/tcg551_sr2.ged

@@ -0,0 +1,9 @@
+0 @SR2@ SOUR
+1 TITL All I Know About GEDCOM, I Learned on the Internet
+1 ABBR What I Know About GEDCOM
+1 AUTH Second Source Author
+1 NOTE @N16@
+1 CHAN
+2 DATE 11 Jan 2001
+3 TIME 16:21:39
+1 RIN 2

data/spec/gedcom/file_spec.rb

@@ -0,0 +1,72 @@
+require 'spec_helper'
+
+describe Gedspec::Gedcom::File do
+  let(:file) { Gedspec::Gedcom::File.new(fixture_file('/tcg551.ged')) }
+
+  it 'extracts head snippet' do
+    expect(file.head.to_gedcom).to eq fixture_content('tcg551_head.ged')
+  end
+
+  it 'extracts a specific subm snippet' do
+    expect(file.subm('SM2')).to eq fixture_content('tcg551_sm2.ged')
+  end
+
+  it 'extracts all subm snippets' do
+    expect(file.subm.size).to eq 3
+    expect(file.subm).to include(fixture_content('tcg551_sm2.ged'))
+  end
+
+  it 'extracts a specific indi snippet' do
+    expect(file.indi('I13')).to eq fixture_content('tcg551_i13.ged')
+  end
+
+  it 'extracts all indi snippets' do
+    expect(file.indi.size).to eq 15
+    expect(file.indi).to include(fixture_content('tcg551_i13.ged'))
+  end
+
+  it 'extracts a specific fam snippet' do
+    expect(file.fam('F5')).to eq fixture_content('tcg551_f5.ged')
+  end
+
+  it 'extracts all fam snippets' do
+    expect(file.fam.size).to eq 7
+    expect(file.fam).to include(fixture_content('tcg551_f5.ged'))
+  end
+
+  it 'extracts a specific repo snippet' do
+    expect(file.repo('R1')).to eq fixture_content('tcg551_r1.ged')
+  end
+
+  it 'extracts all repo snippets' do
+    expect(file.repo.size).to eq 455
+    expect(file.repo).to include(fixture_content('tcg551_r1.ged'))
+  end
+
+  it 'extracts a specific sour snippet' do
+    expect(file.sour('SR2')).to eq fixture_content('tcg551_sr2.ged')
+  end
+
+  it 'extracts all sour snippets' do
+    expect(file.sour.size).to eq 2
+    expect(file.sour).to include(fixture_content('tcg551_sr2.ged'))
+  end
+
+  it 'extracts a specific note snippet' do
+    expect(file.note('N2')).to eq fixture_content('tcg551_n2.ged')
+  end
+
+  it 'extracts all note snippets' do
+    expect(file.note.size).to eq 33
+    expect(file.note).to include(fixture_content('tcg551_n2.ged'))
+  end
+
+  it 'extracts a specific obje snippet' do
+    expect(file.obje('M1')).to eq fixture_content('tcg551_m1.ged')
+  end
+
+  it 'extracts all obje snippets' do
+    expect(file.obje.size).to eq 745
+    expect(file.obje).to include(fixture_content('tcg551_m1.ged'))
+  end
+end

data/spec/gedcom/structure_spec.rb

@@ -0,0 +1,25 @@
+require 'spec_helper'
+
+describe Gedspec::Gedcom::Structure do
+  let(:structure) { Gedspec::Gedcom::Structure.new }
+
+  describe '#get_level' do
+    describe 'when the input string contains a digit character (0123456789)' do
+      it 'returns the first digit character as an integer', :shared => true do
+        expect(structure.get_level('0 @I1@ INDI')).to eq 0
+      end
+    end
+
+    describe 'when the input string contains white-space before the digit' do
+      it 'returns the first digit character as an integer' do
+        expect(structure.get_level(' 0 @I1@ INDI')).to eq 0
+      end
+    end
+
+    describe 'when the input string does not contain a digit character' do
+      it 'should be nil if the the string does not contain a number' do
+        expect(structure.get_level('INDI')).to be_nil
+      end
+    end
+  end
+end

data/spec/gedspec/header_spec.rb

@@ -0,0 +1,48 @@
+require 'spec_helper'
+
+describe Gedspec::Header do
+  let(:head) do
+    Gedspec::Header.new <<-END
+      0 HEAD
+      1 SOUR GEDitCOM
+      2 NAME GEDitCOM
+      2 VERS 2.9.4
+      2 CORP RSAC Software
+      3 ADDR 7108 South Pine Cone Street
+      4 CONT Salt Lake City, UT 84121
+      4 CONT USA
+      4 ADR1 RSAC Software
+      4 ADR2 7108 South Pine Cone Street
+      4 CITY Salt Lake City
+      4 STAE UT
+      4 POST 84121
+      4 CTRY USA
+      3 PHON +1-801-942-7768
+      3 PHON +1-801-555-1212
+      3 PHON +1-801-942-1148 (FAX) (last one!)
+      2 DATA Name of source data
+      3 DATE 1 JAN 1998
+      3 COPR Copyright of source data
+      1 SUBM @SUBMITTER@
+      1 SUBN @SUBMISSION@
+      1 _HME @PERSON1@
+      1 DEST ANSTFILE
+      1 DATE 1 JAN 1998
+      2 TIME 13:57:24.80
+      1 FILE TGC55C.ged
+      1 COPR � 1997 by H. Eichmann, parts � 1999-2000 by J. A. Nairn.
+      1 GEDC
+      2 VERS 5.5
+      2 FORM LINEAGE-LINKED
+      1 LANG English
+      1 CHAR ANSEL
+      2 VERS ANSI Z39.47-1985
+      1 PLAC
+      2 FORM City, County, State, Country
+    END
+  end
+
+  it 'parses char' do
+    expect(head.char).to eq 'ANSEL'
+  end
+end

data/spec/gedspec/individual_spec.rb

@@ -0,0 +1,53 @@
+require 'spec_helper'
+
+describe Gedspec::Individual do
+  let(:indi) do
+    Gedspec::Individual.new <<-END
+      0 @I1@ INDI
+      1 RESN locked
+      1 SEX M
+      1 RFN R55
+      1 AFN AFN4
+      1 REFN T13
+      1 REFN L98
+      1 RIN A1
+      1 NAME John /Hancock/
+    END
+  end
+
+  it 'has many names' do
+    expect(indi.name).to eq 'John /Hancock/'
+  end
+
+  it 'parses xref' do
+    expect(indi.xref).to eq '@I1@'
+  end
+
+  it 'parses resn' do
+    expect(indi.resn).to eq 'locked'
+  end
+
+  it 'parses sex' do
+    expect(indi.sex).to eq 'M'
+  end
+
+  it 'parses rfn' do
+    expect(indi.rfn).to eq 'R55'
+  end
+
+  it 'parses afn' do
+    expect(indi.afn).to eq 'AFN4'
+  end
+
+  it 'parses refn' do
+    expect(indi.refn).to eq ['T13', 'L98']
+  end
+
+  it 'parses rin' do
+    expect(indi.rin).to eq 'A1'
+  end
+
+  it 'parses name' do
+    expect(indi.name).to eq 'John /Hancock/'
+  end
+end