/[ghosts]/ghosts/gedcomparser/tests/save/gedcomsave.out_ref
ViewVC logotype

Diff of /ghosts/gedcomparser/tests/save/gedcomsave.out_ref

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.1 by cpcp, Thu Sep 25 19:27:12 2003 UTC revision 1.2 by cpcp, Thu Oct 30 20:05:45 2003 UTC
# Line 0  Line 1 
1    SepMarJunJJJJJJJJJJJFebJJJJJunJunJunJJJJJMarMayMarJMarMayJunJunJunJunMarMarJunMarMarJMarJJJunJunJJunJunJunJJJJJJJJJJJJ0 HEAD  
2    1 SOUR GEDitCOM
3    2 VERS 2.9.4
4    2 NAME GEDitCOM
5    2 CORP RSAC Software
6    3 ADDR
7    4 CONT 7108 South Pine Cone Street
8    4 CONT Salt Lake City, UT 84121
9    4 CONT USA
10    4 ADR1 RSAC Software
11    4 ADR2 7108 South Pine Cone Street
12    4 CITY Salt Lake City
13    4 STAE UT
14    4 POST 84121
15    4 CTRY USA
16    3 PHON +1-801-942-7768+1-801-555-1212+1-801-942-1148 (FAX) (last one!)
17    2 DATA Name of source data
18    3 DATE 1 JAN 1998
19    3 COPR Copyright of source data
20    1 DEST ANSTFILE
21    1 DATE 1 JAN 1998
22    2 TIME 13:57:24.80
23    1 SUBM @SUBMITTER@
24    1 SUBN @SUBMISSION@
25    1 FILE TGC55C.ged
26    1 COPR à 1997 by H. Eichmann, parts à 1999-2000 by J. A. Nairn.
27    1 GEDC  
28    2 VERS 5.5
29    2 FORM LINEAGE-LINKED
30    1 CHAR ANSEL
31    2 VERS ANSI Z39.47-1985
32    1 LANG English
33    1 PLAC  
34    2 FORM City, County, State, Country
35    1 NOTE This file demonstrates all tags that are allowed in GEDCOM 5.5. Here are some comments about the HEADER record and comments about where to look for information on the other 9 types of GEDCOM records. Most other records will have their own notes that descr
36    2 CONC ibe what to look for in that record and what to hope the importing software will find.
37    2 CONT
38    2 CONT Many applications will fail to import these notes. The notes are therefore also provided with the files as a plain-text "Read-Me" file.
39    2 CONT
40    2 CONT --------------------------
41    2 CONT The HEADER Record:
42    2 CONT      This record has all possible tags for a HEADER record. In uses one custom tag ("_HME") to see what the software will say about custom tags.
43    2 CONT
44    2 CONT --------------------------
45    2 CONT INDIVIDUAL Records:
46    2 CONT      This file has a small number of INDIVIDUAL records. The record named "Joseph Tag Torture" has all possible tags for an INDIVIDUAL record. All remaining  individuals have less tags. Some test specific features; for example:
47    2 CONT
48    2 CONT      Name: Standard GEDCOM Filelinks
49    2 CONT      Name: Nonstandard Multimedia Filelinks
50    2 CONT      Name: General Custom Filelinks
51    2 CONT      Name: Extra URL Filelinks
52    2 CONT           These records link to multimedia files mentioned by the GEDCOM standard and to a variety of other types of multimedia files, general files, or URL names.
53    2 CONT
54    2 CONT      Name: Chris Locked Torture
55    2 CONT           Has a "locked" restriction (RESN) tag - should not be able to edit this record it. This record has one set of notes that is used to test line breaking in notes and a few other text-parsing features of the GEDCOM software. Read those notes
56    2 CONC  to see what they are testing.
57    2 CONT
58    2 CONT      Name: Sandy Privacy Torture
59    2 CONT           Has a "privacy" restriction (RESN) tag. Is the tag recognized and how is the record displayed and/or printed?
60    2 CONT
61    2 CONT      Name: Chris Locked Torture
62    2 CONT      Name: Sandy Privacy Torture
63    2 CONT      Name: Pat Smith Torture
64    2 CONT           The three children in this file have unknown sex (no SEX tag). An ancestor tree from each should give five generations of ancestors.
65    2 CONT
66    2 CONT      Name: Charlie Accented ANSEL
67    2 CONT      Name: Lucy Special ANSEL
68    2 CONT           The notes in these records use all possible special characters in the ANSEL character set. The header of this file denotes this file as using the ANSEL character set. The importing software should handle these special characters in a reas
69    2 CONC onable way.
70    2 CONT
71    2 CONT      Name: Torture GEDCOM Matriarch
72    2 CONT            All individuals in this file are related and all are descendants (or spouses of descendants) of Torture GEDCOM Matriarch. A descendant tree or report from this individual should show five generations of descendants.
73    2 CONT
74    2 CONT --------------------------
75    2 CONT FAMILY Records:
76    2 CONT      The FAMILY record for "Joseph Tag Torture" (husband) and "Mary First Jones" (wife) has all tags allowed in family records. All other family records use only a few tags and are used to provide records for extra family links in other records.
77    2 CONT
78    2 CONT --------------------------
79    2 CONT SOURCE Records:
80    2 CONT      There are two SOURCE records in this file. The "Everything You Every Wanted to Know about GEDCOM Tags" source has all possible GEDCOM tags for a SOURCE record. The other source only has only a few tags.
81    2 CONT
82    2 CONT --------------------------
83    2 CONT REPOSITORY Record:
84    2 CONT      There is just one REPOSITORY record and it uses all possible tags for such a record.
85    2 CONT
86    2 CONT --------------------------
87    2 CONT SUBMITTER Records:
88    2 CONT      This file has three SUBMITTER records. The "John A. Nairn" record has all tags allowed in such records. The second and third submitter are to test how programs input files with multiple submitters. The GEDCOM standard does not allow for notes
89    2 CONC in SUBMITTER records. Look in the "Main Submitter" to verify all address data comes through, that all three phone numbers appear, and that the multimedia file link is preserved.
90    2 CONT
91    2 CONT --------------------------
92    2 CONT MULTIMEDIA OBJECT Record:
93    2 CONT      The one MULTIMEDIA record has all possible tags and even has encoded data for a small image of a flower. There are no known GEDCOM programs that can read or write such records. The record is included here to test how programs might respond to
94    2 CONC finding multimedia records present. There are possible plans to eliminate encoded multimedia objects in the next version of GEDCOM. In the future all multimedia will be included by links to other files. To test current file links and extended file links,
95    2 CONC see the "Filelinks" family records described above.
96    2 CONT
97    2 CONT --------------------------
98    2 CONT SUBMISSION Record:
99    2 CONT      The one (maximum allowed) SUBMISSION record in this file has all possible tags for such a record.
100    2 CONT
101    2 CONT --------------------------
102    2 CONT NOTE Records:
103    2 CONT      This file has many NOTE records. These are all linked to other records.
104    2 CONT
105    2 CONT --------------------------
106    2 CONT TRLR Records:
107    2 CONT      This file ends in the standard TRLR record.
108    2 CONT
109    2 CONT --------------------------
110    2 CONT ADDITIONAL NOTES
111    2 CONT      This file was originally created by H. Eichmann at <h.eichmann@@mbox.iqo.uni-hannover.de> and posted on the Internet.
112    2 CONT
113    2 CONT (NOTE: email addresses are listed here with double "at" signs. A rule of GEDCOM parsing is that these should be converted to single "at" at signs, but not many programs follow that rule. In addition, that rule is not needed and may be abandoned in
114    2 CONC a future version of GEDCOM).
115    2 CONT
116    2 CONT This original file was extensively modified by J. A. Nairn using GEDitCOM 2.9.4 (1999-2001) at <support@@geditcom.com> and posted on the Internet at <http://www.geditcom.com>. Some changes included many more notes, the use or more tags, extensive t
117    2 CONC esting of multimedia file links, and some notes to test all special ANSEL characters.
118    2 CONT
119    2 CONT Feel free to copy and use this GEDCOM file for any  non-commercial purpose.
120    2 CONT
121    2 CONT For selecting the allowed tags, the GEDCOM standard Release 5.5 (2 JAN 1996) was used. Copyright: The Church of Jesus Christ of Latter-Day Saints, <gedcom@@gedcom.org>.
122    2 CONT
123    2 CONT You can download the GEDCOM 5.5 specs from: <ftp.gedcom.com/pub/genealogy/gedcom>. You can read the GEDCOM 5.5 specs on the Internet at <http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm>.
124    0 @SUBMISSION@ SUBN
125    1 SUBM @SUBMITTER@
126    1 FAMF NameOfFamilyFile
127    1 TEMP Abbreviated Temple Code
128    1 ANCE 1
129    1 DESC 1
130    1 ORDI yes
131    1 RIN 1
132    0  FAM
133    1 HUSB @PERSON1@
134    1 WIFE @PERSON8@
135    1 CHIL @PERSON7@
136    1 NOTE @N35@
137    1 RIN 4
138    1 CHAN  
139    2 DATE 13 Jun 2000
140    3 TIME 17:01:46
141    0 @ADOPTIVE_PARENTS@ FAM
142    1 WIFE @PERSON6@
143    1 CHIL @PERSON1@
144    1 NOTE @N34@
145    1 RIN 3
146    1 CHAN  
147    2 DATE 13 Jun 2000
148    3 TIME 17:01:18
149    0 @F5@ FAM
150    1 HUSB @I9@
151    1 WIFE @I15@
152    1 CHIL @I10@
153    1 CHIL @I11@
154    1 CHIL @I12@
155    1 NOTE @N36@
156    1 RIN 5
157    1 CHAN  
158    2 DATE 11 Jan 2001
159    3 TIME 16:50:37
160    0 @F6@ FAM
161    1 HUSB @I14@
162    1 WIFE @I13@
163    1 CHIL @PERSON5@
164    1 NOTE @N37@
165    1 RIN 6
166    1 CHAN  
167    2 DATE 11 Jan 2001
168    3 TIME 16:51:48
169    0 @F7@ FAM
170    1 WIFE @I10@
171    1 CHIL @I14@
172    1 NOTE @N38@
173    1 RIN 7
174    1 CHAN  
175    2 DATE 11 Jan 2001
176    3 TIME 16:52:53
177    0 @PARENTS@ FAM
178    1 HUSB @PERSON5@
179    1 CHIL @PERSON1@
180    1 NOTE @N33@
181    1 RIN 2
182    1 CHAN  
183    2 DATE 13 Jun 2000
184    3 TIME 17:00:35
185    0 @I10@ INDI
186    1 NAME Nonstandard Multimedia /Filelinks/
187    2 GIVN Nonstandard Multimedia
188    2 SURN Filelinks
189    1 SEX F
190    1 BIRT  
191    2 DATE 1870
192    1 FAMC @F5@
193    1 FAMS @F7@
194    1 OBJE  
195    2 FORM PICT
196    2 TITL Macintosh PICT file
197    2 FILE ImgFile.PIC
198    1 OBJE  
199    2 FORM PNTG
200    2 TITL Macintosh MacPaint file
201    2 FILE ImgFile.MAC
202    1 OBJE  
203    2 FORM TPIC
204    2 TITL TGA image file
205    2 FILE ImgFile.TGA
206    1 OBJE  
207    2 FORM aiff
208    2 TITL Macintosh sound file
209    2 FILE enthist.aif
210    1 OBJE  
211    2 FORM mov
212    2 TITL QuickTime movie file
213    2 FILE suntun.mov
214    1 OBJE  
215    2 FORM 8BPS
216    2 TITL Adobe Photoshop file
217    2 FILE ImgFile.PSD
218    1 OBJE  
219    2 FORM mpeg
220    2 TITL Mpeg Movie File
221    2 FILE top.mpg
222    1 NOTE @N21@
223    1 RIN 6
224    1 CHAN  
225    2 DATE 11 Jan 2001
226    3 TIME 16:00:39
227    0 @I11@ INDI
228    1 NAME General Custom /Filelinks/
229    2 GIVN General Custom
230    2 SURN Filelinks
231    1 SEX M
232    1 BIRT  
233    2 DATE 1872
234    1 DEAT  
235    2 DATE 7 DEC 1941
236    1 FAMC @F5@
237    1 OBJE  
238    2 FORM TEXT
239    2 TITL Plain TEXT document
240    2 FILE Document.tex
241    1 OBJE  
242    2 FORM W8BN
243    2 TITL Microsoft Word document
244    2 FILE Document.DOC
245    1 OBJE  
246    2 FORM RTF
247    2 TITL Rich text format document
248    2 FILE Document.RTF
249    1 OBJE  
250    2 FORM PDF
251    2 TITL Portable document format file
252    2 FILE Document.pdf
253    1 NOTE @N22@
254    1 RIN 5
255    1 CHAN  
256    2 DATE 11 Jan 2001
257    3 TIME 16:01:03
258    0 @I12@ INDI
259    1 NAME Extra URL /Filelinks/
260    2 GIVN Extra URL
261    2 SURN Filelinks
262    1 SEX F
263    1 BIRT  
264    2 DATE 1875
265    1 FAMC @F5@
266    1 OBJE  
267    2 FORM URL
268    2 TITL GEDCOM 5.5 documentation web site
269    2 FILE http://homepages.rootsweb.com/~pmcbride/gedcom/55gctoc.htm
270    1 OBJE  
271    2 FORM URL
272    2 TITL FTP site with many GEDCOM files
273    2 FILE ftp://ftp.genealogy.org/genealogy/GEDCOM/
274    1 OBJE  
275    2 FORM URL
276    2 TITL GEDitCOM Macintosh genealogy software home page
277    2 FILE http://www.geditcom.com
278    1 OBJE  
279    2 FORM URL
280    2 TITL Email comments on this GEDCOM file to here
281    2 FILE mailto:support@geditcom.com
282    1 NOTE @N23@
283    1 RIN 4
284    1 CHAN  
285    2 DATE 11 Jan 2001
286    3 TIME 16:01:19
287    0 @I13@ INDI
288    1 NAME Lucy Special /ANSEL/
289    2 GIVN Lucy Special
290    2 SURN ANSEL
291    1 SEX F
292    1 BIRT  
293    2 DATE 12 AUG 1905
294    1 DEAT  
295    2 DATE 31 DEC 1990
296    1 FAMS @F6@
297    1 NOTE @N25@
298    1 RIN 2
299    1 CHAN  
300    2 DATE 11 Jan 2001
301    3 TIME 16:00:23
302    0 @I14@ INDI
303    1 NAME Charlie Accented /ANSEL/
304    2 GIVN Charlie Accented
305    2 SURN ANSEL
306    1 SEX M
307    1 BIRT  
308    2 DATE 15 JUN 1900
309    1 DEAT  
310    2 DATE 5 JUL 1974
311    1 FAMC @F7@
312    1 FAMS @F6@
313    1 NOTE @N24@
314    1 RIN 1
315    1 CHAN  
316    2 DATE 11 Jan 2001
317    3 TIME 16:00:06
318    0 @I15@ INDI
319    1 NAME Torture GEDCOM /Matriarch/
320    2 GIVN Torture GEDCOM
321    2 SURN Matriarch
322    1 SEX F
323    1 BIRT  
324    2 DATE 12 FEB 1840
325    1 DEAT  
326    2 DATE 15 JUN 1915
327    1 FAMS @F5@
328    1 RIN 9
329    1 CHAN  
330    2 DATE 11 Jan 2001
331    3 TIME 16:01:59
332    0 @I9@ INDI
333    1 NAME Standard GEDCOM /Filelinks/
334    2 GIVN Standard GEDCOM
335    2 SURN Filelinks
336    1 SEX M
337    1 BIRT  
338    2 DATE 1835
339    1 FAMS @F5@
340    1 OBJE  
341    2 FORM bmp
342    2 TITL Windows bit mapped image file
343    2 FILE ImgFile.BMP
344    1 OBJE  
345    2 FORM gif
346    2 TITL GIF image file
347    2 FILE ImgFile.GIF
348    1 OBJE  
349    2 FORM jpeg
350    2 TITL JPEG image file
351    2 FILE ImgFile.JPG
352    1 OBJE  
353    2 FORM tiff
354    2 TITL Tagged image format file
355    2 FILE ImgFile.TIF
356    1 OBJE  
357    2 FORM pcx
358    2 TITL Windows paint brush file
359    2 FILE ImgFile.PCX
360    1 OBJE  
361    2 FORM wav
362    2 TITL Windows sound File
363    2 FILE force.wav
364    1 OBJE @M1@
365    1 NOTE @N18@
366    1 RIN 7
367    1 CHAN  
368    2 DATE 11 Jan 2001
369    3 TIME 16:02:06
370    0 @PERSON1@ INDI
371    1 NAME Joseph/Torture/
372    2 NPFX Prof.
373    2 GIVN Joseph
374    2 NICK Joe
375    2 SPFX Le
376    2 SURN Torture
377    2 NSFX Jr.
378    2 SOUR @SOURCE1@
379    3 PAGE 42
380    2 NOTE These are notes about the first NAME structure in this record. These notes are embedded in the INDIVIDUAL record itself.
381    3 CONT
382    3 CONT The second name structure in this record uses all possible tags for a personal name structure.
383    3 CONT
384    3 CONT NOTE: many applications are confused by two NAME structures.
385    1 NAME William John /Smith/
386    2 GIVN William John
387    2 SURN Smith
388    2 SOUR @SOURCE1@
389    3 PAGE 55
390    3 EVEN Event type cited in source
391    4 ROLE Role in cited event
392    3 DATE 1 Jan 1900
393    3 TEXT
394    4 CONT Here is some text from the source specific to this source citation.
395    4 CONT Here is more text but on a new line.
396    3 QUAY 0
397    3 OBJE  
398    4 FORM jpeg
399    4 TITL Multimedia link about this source
400    4 FILE ImgFile.JPG
401    4 NOTE @N26@
402    3 NOTE @N7@
403    2 NOTE This is a second personal NAME structure in a single INDIVIDUAL record which is allowed in GEDCOM. This second NAME structure has all possible fields for a NAME structure.
404    3 CONT
405    3 CONT These notes are embedded in the INDIVIDUAL record.
406    1 SEX M
407    1 BIRT  
408    2 TYPE Normal
409    2 DATE 31 DEC 1965
410    2 PLAC Salt Lake City, UT, USA
411    2 ADDR
412    3 CONT St. Marks Hospital
413    3 CONT Salt Lake City, UT
414    3 CONT USA
415    2 AGNC none
416    2 NOTE @N8@
417    2 OBJE  
418    3 FORM tiff
419    3 TITL Link to multimedia file
420    3 FILE ImgFile.TIF
421    2 NOTE @N8@
422    2 FAMC @PARENTS@
423    1 DEAT  
424    2 TYPE slow
425    2 DATE ABT 15 JAN 2001
426    2 PLAC New York, New York, USA
427    3 SOUR @SOURCE1@
428    3 NOTE The place structure has more detail than usually used for places
429    2 ADDR
430    3 CONT at Home
431    2 AGE 76
432    2 AGNC none
433    2 CAUS Cancer
434    2 NOTE A death event note.
435    2 OBJE  
436    3 FORM jpeg
437    3 TITL Multimedia link about the death event
438    3 FILE ImgFile.JPG
439    2 NOTE A death event note.
440    1 BAPM  
441    2 TYPE BAPM
442    2 DATE ABT 31 DEC 1997
443    2 PLAC The place
444    2 ADDR
445    3 CONT Church Name
446    3 CONT Street Address
447    3 CONT City Name, zip
448    3 CONT Country
449    2 AGE 3 months
450    2 AGNC The Church
451    2 CAUS Birth
452    2 NOTE A baptism event note (the event of baptism (not LDS), performed in infancy or later. See also BAPL and CHR).
453    2 OBJE  
454    3 FORM jpeg
455    3 TITL JPEG File Link
456    3 FILE ImgFile.JPG
457    2 NOTE A baptism event note (the event of baptism (not LDS), performed in infancy or later. See also BAPL and CHR).
458    1 CHR  
459    2 TYPE CHR
460    2 DATE CAL 31 DEC 1997
461    2 PLAC The place
462    2 NOTE Christening event note (the religious event (not LDS) of baptizing and/or naming a child).
463    2 NOTE Christening event note (the religious event (not LDS) of baptizing and/or naming a child).
464    2 FAMC @ADOPTIVE_PARENTS@
465    1 CHR  
466    2 TYPE CHR
467    2 DATE EST 30 DEC 1997
468    2 PLAC The place
469    2 NOTE Alternative christening event note. GEDOM allows more than one of the same type of event.
470    2 NOTE Alternative christening event note. GEDOM allows more than one of the same type of event.
471    1 BLES  
472    2 TYPE BLES
473    2 DATE BEF 31 DEC 1997
474    2 PLAC The place
475    2 NOTE Blessing event note (a religious event of bestowing divine care or intercession. Sometimes given in connection with a naming ceremony)
476    2 NOTE Blessing event note (a religious event of bestowing divine care or intercession. Sometimes given in connection with a naming ceremony)
477    1 BARM  
478    2 TYPE BARM
479    2 DATE AFT 31 DEC 1997
480    2 PLAC The place
481    2 NOTE Bar Mitzvah event note (the ceremonial event held when a Jewish boy reaches age 13).
482    2 NOTE Bar Mitzvah event note (the ceremonial event held when a Jewish boy reaches age 13).
483    1 BASM  
484    2 TYPE BASM
485    2 DATE FROM 31 DEC 1997
486    2 PLAC The place
487    2 NOTE Bas Mitzvah event note (the ceremonial event held when a Jewish girl reaches age 13, also known as "Bat Mitzvah").
488    2 NOTE Bas Mitzvah event note (the ceremonial event held when a Jewish girl reaches age 13, also known as "Bat Mitzvah").
489    1 ADOP  
490    2 TYPE ADOP
491    2 DATE TO 31 DEC 1997
492    2 PLAC The place
493    2 NOTE Adoption event note (pertaining to creation of a child-parent relationship that does not exist biologically).
494    2 NOTE Adoption event note (pertaining to creation of a child-parent relationship that does not exist biologically).
495    2 FAMC @ADOPTIVE_PARENTS@
496    3 ADOP BOTH
497    1 CHRA  
498    2 TYPE CHRA
499    2 DATE BET 31 DEC 1997 AND 1 FEB 1998
500    2 PLAC The place
501    2 NOTE Adult christening event note (the religious event (not LDS) of baptizing and/or naming an adult person).
502    2 NOTE Adult christening event note (the religious event (not LDS) of baptizing and/or naming an adult person).
503    1 CONF  
504    2 TYPE CONF
505    2 DATE FROM 31 DEC 1997 TO 2 JAN 1998
506    2 PLAC The place
507    2 NOTE CONFIRMATION event note (the religious event (not LDS) of conferring the gift of the Holy Ghost and, among protestants, full church membership).
508    2 NOTE CONFIRMATION event note (the religious event (not LDS) of conferring the gift of the Holy Ghost and, among protestants, full church membership).
509    1 FCOM  
510    2 TYPE FCOM
511    2 DATE INT 31 DEC 1997 (a test)
512    2 PLAC The place
513    2 NOTE First communion event note (a religious rite, the first act of sharing in the Lord's supper as part of church worship).
514    2 NOTE First communion event note (a religious rite, the first act of sharing in the Lord's supper as part of church worship).
515    1 ORDN  
516    2 TYPE ORDN
517    2 DATE (No idea of the date)
518    2 PLAC The place
519    2 NOTE Ordination event note (a religious event of receiving authority to act in religious matters).
520    2 NOTE Ordination event note (a religious event of receiving authority to act in religious matters).
521    1 GRAD  
522    2 TYPE GRAD
523    2 DATE 31 DEC 1997
524    2 PLAC The place
525    2 NOTE Graduation event note (an event of awarding educational diplomas or degrees to individuals).
526    2 NOTE Graduation event note (an event of awarding educational diplomas or degrees to individuals).
527    1 EVEN  
528    2 TYPE EMIG
529    2 DATE 1997
530    2 PLAC The place
531    2 NOTE Emigration event note (an event of leaving one's homeland with the intent of residing elsewhere).
532    2 NOTE Emigration event note (an event of leaving one's homeland with the intent of residing elsewhere).
533    1 IMMI  
534    2 TYPE IMMI
535    2 DATE DEC 1997
536    2 PLAC The place
537    2 NOTE Immigration event note (an event of entering into a new locality with the intent of residing there).
538    2 NOTE Immigration event note (an event of entering into a new locality with the intent of residing there).
539    1 EMIG  
540    2 TYPE NATU
541    2 DATE 5 AUG 1100 B.C.
542    2 PLAC The place
543    2 NOTE Naturalization event note (the event of obtaining citizenship).
544    2 NOTE Naturalization event note (the event of obtaining citizenship).
545    1 CENS  
546    2 TYPE CENS
547    2 DATE 2 TVT 5758
548    2 PLAC The place
549    2 NOTE Census event note (the event of the periodic count of the population for a designated locality, such as a national or state Census).
550    2 NOTE Census event note (the event of the periodic count of the population for a designated locality, such as a national or state Census).
551    1 RETI  
552    2 TYPE RETI
553    2 DATE 11 NIVO 0006
554    2 PLAC The place
555    2 NOTE Retirement event note (an event of exiting an occupational relationship with an employer after a qualifying time period).
556    2 NOTE Retirement event note (an event of exiting an occupational relationship with an employer after a qualifying time period).
557    1 PROB  
558    2 TYPE PROB
559    2 DATE FROM 25 SVN 5757 TO 26 IYR 5757
560    2 PLAC The place
561    2 NOTE Probate event note (an event of judicial determination of the validity of a will. May indicate several related court activities over several dates).
562    2 NOTE Probate event note (an event of judicial determination of the validity of a will. May indicate several related court activities over several dates).
563    1 BURI  
564    2 TYPE BURI
565    2 DATE 5 VEND 0010
566    2 PLAC The place
567    2 NOTE Burial event note (the event of the proper disposing of the mortal remains of a deceased person).
568    2 NOTE Burial event note (the event of the proper disposing of the mortal remains of a deceased person).
569    1 WILL  
570    2 TYPE WILL
571    2 DATE INT 2 TVT 5758 (interpreted Hebrew date)
572    2 PLAC The place
573    2 NOTE Will event note (a legal document treated as an event, by which a person disposes of his or her estate, to take effect after death. The event date is the date the will was signed while the person was alive. See also Probate).
574    2 NOTE Will event note (a legal document treated as an event, by which a person disposes of his or her estate, to take effect after death. The event date is the date the will was signed while the person was alive. See also Probate).
575    1 EVEN  
576    2 TYPE EVEN
577    2 DATE 5 MAY 0005
578    2 PLAC The place
579    2 NOTE Generic event note (a noteworthy happening related to an individual, a group, or an organization). The TYPE tag specifies the type of event.
580    2 NOTE Generic event note (a noteworthy happening related to an individual, a group, or an organization). The TYPE tag specifies the type of event.
581    2 TYPE RESI
582    2 DATE 31 DEC 1997
583    2 PLAC The place
584    2 ADDR
585    3 CONT Address in Free Form Line 1
586    3 CONT Address in Free Form Line 2
587    3 CONT Address in Free Form Line 3
588    3 ADR1 Special Address Line 1
589    3 ADR2 Special Address Line 2
590    3 CITY City Name
591    3 STAE State name
592    3 POST Postal Code
593    3 CTRY USA
594    2 PHON +1-800-555-5555
595    2 AGE 35
596    2 AGNC None
597    2 CAUS Needed housing
598    2 NOTE Residence attribute note (the act of dwelling at an address for a period of time).
599    2 NOTE Residence attribute note (the act of dwelling at an address for a period of time).
600    1 OCCU Occupation
601    2 TYPE OCCU
602    2 DATE 31 DEC 1997
603    2 PLAC The place
604    2 ADDR
605    3 CONT Work address line 1
606    3 CONT Work address line 2
607    3 CONT Work address line 3
608    2 AGE 40
609    2 AGNC Employer
610    2 CAUS Need for money
611    2 NOTE Occupation attribute note (the type of work or profession of an individual).
612    2 OBJE  
613    3 FORM gif
614    3 TITL GIF Image File
615    3 FILE ImgFile.GIF
616    2 NOTE Occupation attribute note (the type of work or profession of an individual).
617    1 OCCU Another occupation
618    2 TYPE OCCU
619    2 DATE 31 DEC 1998
620    2 PLAC The place
621    2 NOTE Occupation attribute note. This is the second occupation attribute in the record.
622    2 NOTE Occupation attribute note. This is the second occupation attribute in the record.
623    1 EDUC Education
624    2 TYPE EDUC
625    2 DATE 31 DEC 1997
626    2 PLAC The place
627    2 NOTE Education attribute note (indicator of a level of education attained).
628    2 NOTE Education attribute note (indicator of a level of education attained).
629    1 DSCR Physical description
630    2 TYPE PHYS
631    2 DATE 31 DEC 1997
632    2 PLAC The place
633    2 NOTE Physical description attribute note (the physical characteristics of a person, place, or thing).
634    2 NOTE Physical description attribute note (the physical characteristics of a person, place, or thing).
635    1 RELI Religion
636    2 TYPE RELI
637    2 DATE 31 DEC 1997
638    2 PLAC The place
639    2 NOTE Religion attribute note (a religious denomination to which a person is affiliated or for which a record applies).
640    2 NOTE Religion attribute note (a religious denomination to which a person is affiliated or for which a record applies).
641    1 SSN 6942
642    2 TYPE SSN
643    2 DATE 31 DEC 1997
644    2 PLAC The place
645    2 NOTE Social security number attribute note (a number assigned by the United States Social Security Administration. Used for tax identification purposes).
646    2 NOTE Social security number attribute note (a number assigned by the United States Social Security Administration. Used for tax identification purposes).
647    1 IDNO 6942
648    2 TYPE IDNO
649    2 DATE 31 DEC 1997
650    2 PLAC The place
651    2 NOTE National identification number attribute note (a number assigned to identify a person within some significant external system).
652    2 NOTE National identification number attribute note (a number assigned to identify a person within some significant external system).
653    1 PROP Possessions
654    2 TYPE PROP
655    2 DATE 31 DEC 1997
656    2 PLAC The place
657    2 NOTE Possessions or property attribute note (pertaining to possessions such as real estate or other property of interest).
658    2 NOTE Possessions or property attribute note (pertaining to possessions such as real estate or other property of interest).
659    1 CAST Cast name
660    2 TYPE CAST
661    2 DATE 31 DEC 1997
662    2 PLAC The place
663    2 NOTE Caste name attribute note (the name of an individual's rank or status in society, based on racial or religious differences, or differences in wealth, inherited rank, profession, occupation, etc).
664    2 NOTE Caste name attribute note (the name of an individual's rank or status in society, based on racial or religious differences, or differences in wealth, inherited rank, profession, occupation, etc).
665    1 NCHI 42
666    2 TYPE NCHI
667    2 DATE 31 DEC 1997
668    2 PLAC The place
669    2 NOTE Number of children attribute note.
670    2 NOTE Number of children attribute note.
671    1 NMR 42
672    2 TYPE NMR
673    2 DATE 31 DEC 1997
674    2 PLAC The place
675    2 NOTE Number of marriages attribute note.
676    2 NOTE Number of marriages attribute note.
677    1 TITL Nobility title
678    2 TYPE TITL
679    2 DATE 31 DEC 1997
680    2 PLAC The place
681    2 NOTE Title attribute note (a description of a specific writing or other work, such as the title of a book when used in a source context, or a formal designation used by an individual in connection with positions of royalty or other social status,
682    3 CONT such as Grand Duke).
683    2 NOTE Title attribute note (a description of a specific writing or other work, such as the title of a book when used in a source context, or a formal designation used by an individual in connection with positions of royalty or other social status,
684    3 CONT such as Grand Duke).
685    1 NATI National or tribe origin
686    2 TYPE NATI
687    2 DATE 31 DEC 1997
688    2 PLAC The place
689    2 NOTE Nationality attribute note (the national heritage of an individual).
690    2 NOTE Nationality attribute note (the national heritage of an individual).
691    1 BAPL  
692    2 STAT Cleared
693    2 DATE 5 MAY 0005 B.C.
694    2 TEMP Mormon Temple
695    2 PLAC Salt Lake City
696    2 SOUR @SOURCE1@
697    2 NOTE @N5@
698    1 CONL  
699    1 ENDL  
700    2 DATE BET 5 APR 1712/13 AND 28 SEP 1714/15
701    1 SLGC  
702    2 DATE 27 OCT 1699/00
703    2 FAMC @PARENTS@
704    1 FAMC @PARENTS@
705    2 NOTE Note about this link to his parents family record.
706    2 NOTE Another note about this link to his parents family record
707    1 FAMC @ADOPTIVE_PARENTS@
708    2 PEDI adopted
709    2 NOTE Note about the link to his adoptive parents family record.
710    1 FAMS @FAMILY1@
711    2 NOTE Note about the link to the family record with his first spouse.
712    2 NOTE Another note about the link to the family record with his first spouse.
713    1 FAMS @FAMILY2@
714    1 SUBM @SUBMITTER@
715    1 ASSO @I9@
716    1 ASSO @PERSON5@
717    1 RELA Father
718    2 NOTE Note on association link.
719    2 SOUR @SOURCE1@
720    3 PAGE 42
721    3 DATE 31 Déc 1900
722    3 TEXT
723    4 CONT Sample text about this source on an association.
724    1 ALIA @I9@
725    1 ANCI @SUBMITTER@
726    1 DESI @SUBMITTER@
727    1 SOUR
728    2 CONT This source is embedded in the record instead of being a link to a separate SOURCE record.
729    2 CONT The source description can use any number of lines
730    2 TEXT
731    3 CONT Text from a source. The preferred approach is to cite sources by links to SOURCE records.
732    3 CONT Here is a new line of text from the source.
733    2 NOTE @N17@
734    1 SOUR @SR2@
735    2 NOTE @N12@
736    1 SOUR @SOURCE1@
737    2 PAGE 42
738    2 DATE 31 Déc 1900
739    2 TEXT
740    3 CONT Some sample text from the first source on this record.
741    2 QUAY 0
742    2 NOTE A source note.
743    1 OBJE  
744    2 FORM gif
745    2 TITL GIF Image File
746    2 FILE ImgFile.GIF
747    1 NOTE This is a second set of notes for this single individual record. It is embedded in the INDIVIDUAL record instead of being in a separate NOTE record.
748    2 CONT
749    2 CONT These notes also have a source citation to a SOURCE record. In GEDCOM this source can only be a single line and links to a SOURCE record.
750    2 SOUR @SOURCE1@
751    1 NOTE @N4@
752    2 SOUR @SOURCE1@
753    1 RFN Record File Number
754    1 AFN Ancestral File Number
755    1 REFN User reference number
756    2 TYPE Type of user number
757    1 RIN 12
758    1 CHAN  
759    2 DATE 12 Feb 2001
760    3 TIME 19:16:42
761    0 @PERSON2@ INDI
762    1 NAME Mary First /Jones/
763    2 GIVN Mary First
764    2 SURN Jones
765    1 SEX F
766    1 BIRT  
767    2 DATE BEF 1970
768    1 DEAT  
769    2 DATE AFT 2000
770    1 FAMS @FAMILY1@
771    1 NOTE @N31@
772    1 RIN 8
773    1 CHAN  
774    2 DATE 11 Jan 2001
775    3 TIME 15:58:16
776    0 @PERSON3@ INDI
777    1 RESN locked
778    1 NAME Chris Locked /Torture/
779    2 GIVN Chris Locked
780    2 SURN Torture
781    1 BIRT  
782    2 DATE MAR 1999
783    2 PLAC Las Vegas, Nevada USA
784    1 FAMC @FAMILY1@
785    1 NOTE @N20@
786    1 RIN 11
787    1 CHAN  
788    2 DATE 11 Jan 2001
789    3 TIME 15:55:43
790    2 NOTE This date is the last time this record was changed
791    0 @PERSON4@ INDI
792    1 RESN privacy
793    1 NAME Sandy Privacy /Torture/
794    2 GIVN Sandy Privacy
795    2 SURN Torture
796    1 BIRT  
797    2 DATE 15 FEB 2000
798    2 PLAC Chicago, IL, USA
799    1 FAMC @FAMILY1@
800    1 NOTE @N29@
801    1 RIN 14
802    1 CHAN  
803    2 DATE 11 Jan 2001
804    3 TIME 15:56:15
805    0 @PERSON5@ INDI
806    1 NAME William Joseph /Torture/
807    2 GIVN William Joseph
808    2 SURN Torture
809    1 SEX M
810    1 BIRT  
811    2 DATE ABT 1930
812    1 DEAT  
813    2 DATE INT 1995 (from estimated age)
814    2 AGE 65
815    2 CAUS Old age
816    1 FAMC @F6@
817    1 FAMS @PARENTS@
818    1 NOTE @N28@
819    1 RIN 15
820    1 CHAN  
821    2 DATE 11 Jan 2001
822    3 TIME 15:59:40
823    0 @PERSON6@ INDI
824    1 NAME Teresa Mary /Caregiver/
825    2 GIVN Teresa Mary
826    2 SURN Caregiver
827    1 SEX F
828    1 BIRT  
829    2 DATE 6 JUN 1944
830    1 FAMS @ADOPTIVE_PARENTS@
831    1 NOTE @N27@
832    1 RIN 3
833    1 CHAN  
834    2 DATE 11 Jan 2001
835    3 TIME 16:03:05
836    0 @PERSON7@ INDI
837    1 NAME Pat Smith /Torture/
838    2 GIVN Pat Smith
839    2 SURN Torture
840    1 BIRT  
841    2 DATE 1 JAN 2001
842    2 PLAC London, UK
843    1 FAMC @FAMILY2@
844    1 NOTE @N30@
845    1 RIN 13
846    1 CHAN  
847    2 DATE 11 Jan 2001
848    3 TIME 15:56:49
849    0 @PERSON8@ INDI
850    1 NAME Elizabeth Second /Smith/
851    2 GIVN Elizabeth Second
852    2 SURN Smith
853    1 SEX F
854    1 BIRT  
855    2 DATE BET MAY 1979 AND AUG 1979
856    1 DEAT  
857    2 DATE FROM APR 2000 TO 5 MAR 2001
858    1 FAMS @FAMILY2@
859    1 NOTE @N32@
860    1 RIN 10
861    1 CHAN  
862    2 DATE 11 Jan 2001
863    3 TIME 15:58:58
864    0 @M1@ OBJE
865    1 FORM PICT
866    1 TITL Dummy Multimedia Object
867    1 NOTE Here are some notes on this multimedia object.
868    2 CONT If decoded it should be an image of a flower.
869    1 BLOB .HM.......k.1..F.jwA.Dzzzzw............A....1.........0U.66..E.8.......A..k.a6.A.......A..k.........../6....G.......0../..U......w1/m........HC0..../...zzzzzzzz..5zzk..AnA..U..W6U....2rRrRrRrR.Dw...............k.1.......1..A...5ykE/zzzx/.g//.Hxzk6/.Tzy/.k
870    2 CONC 1/Dw/.Tvz.E5zzUE9/kHz.Tw2/DzzzEEA.kE2zk5yzk2/zzs21.U2/Dw/.Tw/.Tzy/.fy/.HzzkHzzzo21Ds00.E2.UE2.U62/.k./Ds0.UE0/Do0..E8/UE2.U62.U9w/.Tx/.20.jg2/jo2..9u/.0U.6A.zk
871    1 REFN User Reference Number
872    2 TYPE User Reference Type
873    1 RIN 1
874    1 CHAN  
875    2 DATE 14 Jan 2001
876    3 TIME 14:10:31
877    0 @N11@ NOTE A possessions source note.
878    1 CHAN  
879    2 DATE 18 Jun 2000
880    3 TIME 1:37:42
881    0 @N12@ NOTE This is a second source citation in this record.
882    1 CHAN  
883    2 DATE 6 Mar 2000
884    3 TIME 22:18:51
885    0 @N14@ NOTE These notes can be used to add more information about the multimedia file linked to this SOURCE record.
886    1 CHAN  
887    2 DATE 12 Mar 2000
888    3 TIME 9:49:23
889    0 @N15@ NOTE Comments on "Everything You Every Wanted to Know about GEDCOM Tags" SOURCE Record.
890    
891    This is a set of notes about this SOURCE record. These notes are for anything else needed. There are other places to enter notes about the storage of the source (in the Repository link) and about the data in the source (in the DATA structure).
892    
893    This particular SOURCE record uses all possible GEDCOM tags for a SOURCE record. Some things to check are:
894    
895    1. Are the separate notes structures in the Repository link and the DATA structure preserved on importing?
896    
897    2. Does the software recognize two sets of event types in the DATA structure?
898    
899    3. Are the multimedia links preserved?
900    
901    4. This record as two sets of notes - this one in a separate record and a second one embedded in the SOURCE record. Are they both imported and kept separate?
902    1 CHAN  
903    2 DATE 13 Jun 2000
904    3 TIME 17:04:24
905    0 @N16@ NOTE Comments on "All I Know About GEDCOM, I Learned on the Internet" SOURCE record.
906    
907    This is another SOURCE record. How does the importing software handle multiple sources in the GEDCOM file? This source only fills a few GEDCOM structures.
908    1 CHAN  
909    2 DATE 12 Mar 2000
910    3 TIME 12:46:21
911    0 @N17@ NOTE How does software handle embedded SOURCE records on import? Such source citations are common in old GEDCOM files. More modern GEDCOM files should use source citations to SOURCE records.
912    1 CHAN  
913    2 DATE 12 Mar 2000
914    3 TIME 10:56:56
915    0 @N18@ NOTE Comments on "Standard GEDCOM Filelinks" INDIVIDUAL Record.
916    
917    The GEDCOM standard lets you link records to multimedia objects kept in separate files. When GEDCOM 5.5 was released, it only mentioned allowing links to a small number of multimedia files types and some of them are Windows-only file types. The recommended list is
918    
919         bmp - Windows but map file
920         gif - Bit map, 256 color GIF files (common on the Internet)
921         jpeg - Bit-mapped files developed for photographs (also common on the Internet)
922         ole - Linked object
923         pcx - Windows paintbrush file
924         tiff - Tagged image format file
925         wav - Windows sound file
926    
927    This INDIVIDUAL record has links to this limited set of multimedia files (except for ole). These links are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag.
928    
929    It does not make sense to limit files links to this small set of file types. It does not allow for future file types and, for example, it ignores movie files types. You can visit the "Nonstandard Multimedia Filelinks" record to see links to other types of multimedia files. You can visit the "General Custom Filelinks" and the "Extra URL Filelinks" records to see links to any file type and to universal resource locators.
930    
931    NOTE: The path names for the linked files here are just the file names. A good GEDCOM program should search for the files and might look first in the same folder as this test GEDCOM file. A weaker program might be unable to locate these files and you will have to enter the full path names.
932    
933    EMBEDDED Multimedia Object:
934         GEDCOM 5.5 has a method for encoding multimedia objects and storing them in MULTIMEDIA Records. This INDIVIDUAL has a link to such an embedded object. The object has encoded data, written using the GEDCOM 5.5 encoding algorithm, for the image of a small flower. To my knowledge, there are no genealogy programs that can actually read and decode such objects. The main reason for inclusion of the object here is to see how programs will treat this record. Good programs will leave them in the file (it is bad manners to delete someone's data). Bad programs will simple delete the object from the file.
935    1 REFN User Reference Number
936    2 TYPE User Reference Type
937    1 RIN 1
938    1 CHAN  
939    2 DATE 11 Jan 2001
940    3 TIME 15:41:51
941    0 @N19@ NOTE A note about this LDS spouse sealing source.
942    1 CHAN  
943    2 DATE 12 Mar 2000
944    3 TIME 12:32:13
945    0 @N1@ NOTE Test link to a graphics file about the main Submitter of this file.
946    1 CHAN  
947    2 DATE 24 May 1999
948    3 TIME 16:39:55
949    0 @N20@ NOTE Comments on "Chris Locked Torture" record.
950    
951    These notes test line breaking in note records with multiple lines. These notes are for a locked individual and thus you should not be able to edit them.
952    
953    TEST #1: Line breaks in the middle of a word
954         These lines appear together. The word TEST should appear as a single word and not be broken onto two lines.
955    
956    TEST #2: Translation of "at" signs
957         The GEDCOM standard says the "@@" sign should appear in any text in the file as double "@@@@" signs. This recommendation is superfluous, because there is never a case when an "@@" sign in data can be confused with other GEDCOM uses of the "@@" sign. The question here is how does the software import:
958    
959         A single @@ sign in some notes entered by using two characters.
960    
961    If all "at" signs above appear above as 2 or 4 at signs, that GEDCOM software is not converting double at signs to single at signs.
962    
963    TEST #3: Bad line breaks between word but a forgotten space
964         A little below, the words "End" and "Start" are on two lines in the note record. The line with "End," however, forgot the required trailing blank. Thus, a proper importing of these bad notes should combine the two words with no space between "End" and "Start". Here is EndStart as described above. They should appear as one word.
965    
966    TEST #4: Blank lines
967         The above paragraphs should have blank lines between them.
968    1 CHAN  
969    2 DATE 11 Jan 2001
970    3 TIME 15:35:25
971    0 @N21@ NOTE Comments on "Nonstandard Multimedia Filelinks" INDIVIDUAL Record.
972    
973    File links in GEDCOM are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag. It does not make sense to limit file links to the small set of file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks"  for those file types). This INDIVIDUAL record has links to other types of multimedia files including movie files, other image file types, and some Macintosh file types.
974    
975    What will a genealogy program do when in encounters to logical extensions to GEDCOM file links? Good programs will follow the links. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).
976    
977    Some other possible multimedia file type not yet linked to this record are:
978       avi - Microsoft movie file
979       midi - sound file
980       mp3 - music file
981    1 CHAN  
982    2 DATE 11 Jan 2001
983    3 TIME 15:43:04
984    0 @N22@ NOTE Comments on "General Custom Filelinks" INDIVIDUAL Record.
985    
986    File links in GEDCOM are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag. It does not make sense to limit file links to the small set of multimedia file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks" for those file types). The INDIVIDUAL record "Nonstandard Multimedia Filelinks" has sample links to other types of multimedia files not included in the standard GEDCOM list. This INDIVIDUAL record has links to some non-multimedia files types.
987    
988    What will a genealogy program do when it encounters such logical extensions to GEDCOM file links? Good programs will follow the links. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).
989    1 CHAN  
990    2 DATE 20 Jun 2000
991    3 TIME 1:06:34
992    0 @N23@ NOTE Comments on "Extra URL Filelinks" INDIVIDUAL Record.
993    
994    File links in GEDCOM are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag. It does not make sense to limit file links to the small set of multimedia file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks" for those file types) or even to limit them to local files. This INDIVIDUAL record has a series of links with universal resource locators (URL) in the FILE tag and the file "URL" in the FORM tag.
995    
996    The sample URL links include links to a web sites, a link to an FTP site, and a link to send email.
997    
998    This extension of file links to URL links is non-standard GEDCOM. What will a genealogy program do when in encounters URL file links? Cleaver programs will find the file on the Internet using your default browser, FTP program, or email program. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).
999    1 CHAN  
1000    2 DATE 20 Jun 2000
1001    3 TIME 1:09:48
1002    0 @N24@ NOTE Comments on "Charlie Accented ANSEL" INDIVIDUAL Record.
1003    
1004    To represent accented characters, the ANSEL character set uses two-byte codes. The first byte is E0 to FB or FE (hexadecimal); the second byte is the letter to be accented.
1005    
1006    These notes have all possible accented characters. How many of the characters are represented correctly? Even programs that fully support ANSEL will not draw all these accented characters correctly. Many of them correspond to accents that can not be found in any langauge and therefore do not correspond to any computer fonts.
1007    
1008    code: E0 (Unicode: hook above, 0309) low rising tone mark
1009         àAàBàCàDàEàFàGàHàIàJàKàLàM
1010         àNàOàPàQàRàSàTàUàVàWàXàYàZ
1011         àaàbàcàdàeàfàgàhàiàjàkàlàm
1012         ànàoàpàqàràsàtàuàvàwàxàyàz
1013    
1014    code: E1 (Unicode: grave, 0300) grave accent
1015         áAáBáCáDáEáFáGáHáIáJáKáLáM
1016         áNáOáPáQáRáSáTáUáVáWáXáYáZ
1017         áaábácádáeáfágáháiájákálám
1018         ánáoápáqárásátáuáváwáxáyáz
1019    
1020    code: E2 (Unicode: acute, 0301) acute accent:
1021         âAâBâCâDâEâFâGâHâIâJâKâLâM
1022         âNâOâPâQâRâSâTâUâVâWâXâYâZ
1023         âaâbâcâdâeâfâgâhâiâjâkâlâm
1024         ânâiâpâqârâsâtâuâvâwâxâyâz
1025    
1026    code: E3 (Unicode: circumflex, 0302) circumflex accent
1027         ãAãBãCãDãEãFãGãHãIãJãKãLãM
1028         ãNãOãPãQãRãSãTãUãVãWãXãYãZ
1029         ãaãbãcãdãeãfãgãhãiãjãkãlãm
1030         ãnãoãpãqãrãsãtãuãvãwãxãyãz
1031    
1032    code: E4 (Unicode: tilde, 0303) tilde
1033         äAäBäCäDäEäFäGäHäIäJäKäLäM
1034         äNäOäPäQäRäSäTäUäVäWäXäYäZ
1035         äNäbäcädäeäfägähäiäjäkäläm
1036         änäoäpäqäräsätäuäväwäxäyäz
1037    
1038    code: E5 (Unicode: macron, 0304) macron
1039         åAåBåCåDåEåFåGåHåIåJåKåLåM
1040         åNåOåPåQåRåSåTåUåVåWåXåYåZ
1041         åaåbåcådåeåfågåhåiåjåkålåm
1042         ånåoåpåqåråsåtåuåvåwåxåyåz
1043    
1044    code: E6 (Unicode: breve, 0306) breve
1045         æAæBæCæDæEæFæGæHæIæJæKæLæM
1046         æNæOæPæQæRæSæTæUæVæWæXæYæZ
1047         æaæbæcædæeæfægæhæiæjækælæm
1048         ænæoæpæqæræsætæuævæwæxæyæz
1049    
1050    code: E7 (Unicode: dot above, 0307) dot above
1051         çAçBçCçDçEçFçGçHçIçJçKçLçM
1052         çNçOçPçQçRçSçTçUçVçWçXçYçZ
1053         çaçbçcçdçeçfçgçhçiçjçkçlçm
1054         çnçoçpçqçrçsçtçuçvçwçxçyçz
1055    
1056    code: E8 (Unicode: diaeresis, 0308) umlaut (dieresis)
1057         èAèBèCèDèEèFèGèHèIèJèKèLèM
1058         èNèOèPèQèRèSèTèUèVèWèXèYèZ
1059         èaèbècèdèeèfègèhèièjèkèlèm
1060         ènèoèpèqèrèsètèuèvèwèxèyèz
1061    
1062    code: E9 (Unicode: caron, 030C) hacek
1063         éAéBéCéDéEéFéGéHéIéJéKéLéM
1064         éNéOéPéQéRéSéTéUéVéWéXéYéZ
1065         éaébécédéeéfégéhéiéjékélém
1066         énéoépéqérésétéuévéwéxéyéz
1067    
1068    code: EA (Unicode: ring above, 030A) circle above (angstrom)
1069         êAêBêCêDêEêFêGêHêIêJêKêLêM
1070         êNêOêPêQêRêSêTêUêVêWêXêYêZ
1071         êaêbêcêdêeêfêgêhêiêjêkêlêm
1072         ênêoêpêqêrêsêtêuêvêwêxêyêz
1073    
1074    code: EB (Unicode: ligature left half, FE20) ligature, left half
1075         ëAëBëCëDëEëFëGëHëIëJëKëLëM
1076         ëNëOëPëQëRëSëTëUëVëWëXëYëZ
1077         ëaëbëcëdëeëfëgëhëiëjëkëlëm
1078         ënëoëpëqërësëtëuëvëwëxëyëz
1079    
1080    code: EC (Unicode: ligature right half, FE21) ligature, right half
1081         ìAìBìCìDìEìFìGìHìIìJìKìLìM
1082         ìNìOìPìQìRìSìTìUìVìWìXìYìZ
1083         ìaìbìcìdìeìfìgìhìiìjìkìlìm
1084         ìnìoìpìqìrìsìtìuìvìwìxìyìz
1085    
1086    code: ED (Unicode: comma above right, 0315) high comma, off center
1087         íAíBíCíDíEíFíGíHíIíJíKíLíM
1088         íNíOíPíQíRíSíTíUíVíWíXíYíZ
1089         íaíbícídíeífígíhíiíjíkílím
1090         íníoípíqírísítíuívíwíxíyíz
1091    
1092    code: EE (Unicode: double acute, 030B) double acute accent
1093         îAîBîCîDîEîFîGîHîIîJîKîLîM
1094         îNîOîPîQîRîSîTîUîVîWîXîYîZ
1095         îaîbîcîdîeîfîgîhîiîjîkîlîm
1096         înîoîpîqîrîsîtîuîvîwîxîyîz
1097    
1098    code: EF (Unicode: candrabindu, 0310) candrabindu
1099         ïAïBïCïDïEïFïGïHïIïJïKïLïM
1100         ïNïOïPïQïRïSïTïUïVïWïXïYïZ
1101         ïaïbïcïdïeïfïgïhïiïjïkïlïm
1102         ïnïoïpïqïrïsïtïuïvïwïxïyïz
1103    
1104    code: F0 (Unicode: cedilla, 0327) cedilla
1105         ðAðBðCðDðEðFðGðHðIðJðKðLðM
1106         ðNðOðPðQðRðSðTðUðVðWðXðYðZ
1107         ðaðbðcðdðeðfðgðhðiðjðkðlðm
1108         ðnðoðpðqðrðsðtðuðvðwðxðyðz
1109    
1110    code: F1 (Unicode: ogonek, 0328) right hook
1111         ñAñBñCñDñEñFñGñHñIñJñKñLñM
1112         ñNñOñPñQñRñSñTñUñVñWñXñYñZ
1113         ñañbñcñdñeñfñgñhñiñjñkñlñm
1114         ñnñoñpñqñrñsñtñuñvñwñxñyñz
1115    
1116    code: F2 (Unicode: dot below, 0323) dot below
1117         òAòBòCòDòEòFòGòHòIòJòKòLòM
1118         òNòOòPòQòRòSòTòUòVòWòXòYòZ
1119         òaòbòcòdòeòfògòhòiòjòkòlòm
1120         ònòoòpòqòròsòtòuòvòwòxòyòz
1121    
1122    code: F3 (Unicode: diaeresis below, 0324) double dot below
1123         óAóBóCóDóEóFóGóHóIóJóKóLóM
1124         óNóOóPóQóRóSóTóUóVóWóXóYóZ
1125         óaóbócódóeófógóhóiójókólóm
1126         ónóoópóqórósótóuóvówóxóyóz
1127    
1128    code: F4 (Unicode: ring below, 0325) circle below
1129         ôAôBôCôDôEôFôGôHôIôJôKôLôM
1130         ôNôOôPôQôRôSôTôUôVôWôXôYôZ
1131         ôaôbôcôdôeôfôgôhôiôjôkôlôm
1132         ônôoôpôqôrôsôtôuôvôwôxôyôz
1133    
1134    code: F5 (Unicode: double low line, 0333) double underscore
1135         õAõBõCõDõEõFõGõHõIõJõKõLõM
1136         õNõOõPõQõRõSõTõUõVõWõXõYõZ
1137         õaõbõcõdõeõfõgõhõiõjõkõlõm
1138         õnõoõpõqõrõsõtõuõvõwõxõyõz
1139    
1140    code: F6 (Unicode: line below, 0332) underscore
1141         öAöBöCöDöEöFöGöHöIöJöKöLöM
1142         öNöOöPöQöRöSöTöUöVöWöXöYöZ
1143         öaöböcödöeöfögöhöiöjökölöm
1144         önöoöpöqörösötöuövöwöxöyöz
1145    
1146    code: F7 (Unicode: comma below, 0326) left hook
1147         ÷A÷B÷C÷D÷E÷F÷G÷H÷I÷J÷K÷L÷M
1148         ÷N÷O÷P÷Q÷R÷S÷T÷U÷V÷W÷X÷Y÷Z
1149         ÷a÷b÷c÷d÷e÷f÷g÷h÷i÷j÷k÷l÷m
1150         ÷n÷o÷p÷q÷r÷s÷t÷u÷v÷w÷x÷y÷z
1151    
1152    code: F8 (Unicode: left half ring below, 031C) right cedilla
1153         øAøBøCøDøEøFøGøHøIøJøKøLøM
1154         øNøOøPøQøRøSøTøUøVøWøXøYøZ
1155         øaøbøcødøeøføgøhøiøjøkøløm
1156         ønøoøpøqørøsøtøuøvøwøxøyøz
1157    
1158    code: F9 (Unicode: breve below, 032E) half circle below
1159         ùAùBùCùDùEùFùGùHùIùJùKùLùM
1160         ùNùOùPùQùRùSùTùUùVùWùXùYùZ
1161         ùaùbùcùdùeùfùgùhùiùjùkùlùm
1162         ùnùoùpùqùrùsùtùuùvùwùxùyùz
1163    
1164    code: FA (Unicode: double tilde left half, FE22) double tilde, left half
1165         úAúBúCúDúEúFúGúHúIúJúKúLúM
1166         úNúOúPúQúRúSúTúUúVúWúXúYúZ
1167         úaúbúcúdúeúfúgúhúiújúkúlúm
1168         únúoúpúqúrúsútúuúvúwúxúyúz
1169    
1170    code: FB (Unicode: double tilde right half, FE23) double tilde, right half
1171         ûAûBûCûDûEûFûGûHûIûJûKûLûM
1172         ûNûOûPûQûRûSûTûUûVûWûXûYûZ
1173         ûaûbûcûdûeûfûgûhûiûjûkûlûm
1174         ûnûoûpûqûrûsûtûuûvûwûxûyûz
1175    
1176    code: FE (Unicode: comma above, 0313) high comma, centered
1177         þAþBþCþDþEþFþGþHþIþJþKþLþM
1178         þNþOþPþQþRþSþTþUþVþWþXþYþZ
1179         þaþbþcþdþeþfþgþhþiþjþkþlþm
1180         þnþoþpþqþrþsþtþuþvþwþxþyþz
1181    1 CHAN  
1182    2 DATE 12 Jan 2001
1183    3 TIME 0:32:24
1184    0 @N25@ NOTE Comments on "Lucy Special ANSEL" INDIVIDUAL Record.
1185    
1186    The following are the special characters supported by the ANSEL character set. The first two letters are the Hex code. The following text describes the character. Finally, that character, or a character as close as possible to that character, should appear in the parentheses.
1187    
1188    A1 slash l - uppercase (¡)
1189    A2 slash o - uppercase (¢)
1190    A3 slash d - uppercase (£)
1191    A4 thorn - uppercase (¤)
1192    A5 ligature ae - uppercase (¥)
1193    A6 ligature oe - uppercase (¦)
1194    A7 single prime (§)
1195    A8 middle dot (¨)
1196    A9 musical flat (©)
1197    AA registered sign (ª)
1198    AB plus-or-minus («)
1199    AC hook o - uppercase (¬)
1200    AD hook u - uppercase (­)
1201    AE left half ring (®)
1202    BO right half ring (°)
1203    B1 slash l - lowercase (±)
1204    B2 slash o - lowercase (²)
1205    B3 slash d - lowercase (³)
1206    B4 thorn - lowercase (´)
1207    B5 ligature ae - lowercase (µ)
1208    B6 ligature oe - lowercase (¶)
1209    B7 double prime (·)
1210    B8 dotless i - lowercase (¸)
1211    B9 british pound (¹)
1212    BA eth (º)
1213    BC hook o - lowercase (¼)
1214    BD hook u - lowercase (½)
1215    BE empty box - LDS extension (¾)
1216    BF black box - LDS extensions (¿)
1217    CO degree sign (À)
1218    C1 script l (Á)
1219    C2 phonograph copyright mark (Â)
1220    C3 copyright symbol (Ã)
1221    C4 musical sharp (Ä)
1222    C5 inverted question mark (Å)
1223    C6 inverted exclamation mark (Æ)
1224    CD midline e - LDS extension (Í)
1225    CE midline o - LDS extension (Î)
1226    CF es zet (Ï)
1227    1 CHAN  
1228    2 DATE 13 Jun 2000
1229    3 TIME 16:28:45
1230    0 @N26@ NOTE These are some notes of this multimedia link in the NAME structure.
1231    1 CHAN  
1232    2 DATE 16 Jun 2000
1233    3 TIME 1:20:11
1234    0 @N27@ NOTE Comments on "Teresa Mary Caregiver" INDIVIDUAL Record.
1235    
1236    This record is the adoptive mother of "Joseph Tag Torture". She is linked to a family record, but there is no husband in that record.
1237    1 CHAN  
1238    2 DATE 13 Jun 2000
1239    3 TIME 17:14:28
1240    0 @N28@ NOTE Comments on "William Joseph Torture" INDIVIDUAL Record.
1241    
1242    This record is the natural father of "Joseph Tag Torture". He is linked to a family record, but there is no wife in that record.
1243    1 CHAN  
1244    2 DATE 11 Jan 2001
1245    3 TIME 15:31:12
1246    0 @N29@ NOTE Comments on "Sandy Privacy Torture" INDIVIDUAL Record.
1247    
1248    This record has a restriction setting of "privacy." In public applications of GEDCOM files, "privacy" records should be hidden from all viewing and printing. It is less clear how GEDCOM software on your own PC reading your own copies of GEDCOM files should treat "privacy" records. At a minimum, it should import and preserve the "privacy" setting.
1249    1 CHAN  
1250    2 DATE 11 Jan 2001
1251    3 TIME 15:36:50
1252    0 @N2@ NOTE Comments on "Family History Library" REPOSITORY Record.
1253    
1254    This record uses all possible GEDCOM tags for a REPOSITORY record. Some things to look for are:
1255    
1256    1. The address is specified twice. Once in a multi-line address record and once in separate lines. The first method is usually enough. The second method is to be more specific about parts of the address. Is everything imported?
1257    
1258    2. There are multiple phone numbers. Are they all imported?
1259    1 SOUR @SOURCE1@
1260    2 PAGE 1
1261    2 DATE 1 Mai 1999
1262    2 TEXT
1263    3 CONT Text from the source about this repository.
1264    2 QUAY 3
1265    1 CHAN  
1266    2 DATE 12 Mar 2000
1267    3 TIME 11:44:05
1268    0 @N30@ NOTE Comments on "Pat Smith Torture" INDIVIDUAL Record.
1269    
1270    The record simply provides a child to "Joseph Tag Torture" in his family with "Mary First Jones" as his spouse.
1271    1 CHAN  
1272    2 DATE 11 Jan 2001
1273    3 TIME 15:40:04
1274    0 @N31@ NOTE Comments on "Mary First Jones" INDIVIDUAL Record.
1275    
1276    This record is used to provide the first wife to "Joseph Tag Torture." Not many other tags are used.
1277    1 CHAN  
1278    2 DATE 11 Jan 2001
1279    3 TIME 15:38:17
1280    0 @N32@ NOTE Comments on "Elizabeth Second Smith" INDIVIDUAL Record.
1281    
1282    This record is used to provide a second wife to "Joseph Tag Torture." Not many other tags are used.
1283    1 CHAN  
1284    2 DATE 11 Jan 2001
1285    3 TIME 15:38:55
1286    0 @N33@ NOTE Comments on "William Joseph Torture-<unknown>" FAMILY Record.
1287    
1288    This record has the natural father of "Joseph Tag Torture." The wife is not known.
1289    1 CHAN  
1290    2 DATE 11 Jan 2001
1291    3 TIME 16:49:33
1292    0 @N34@ NOTE Comments on "<unknown>-Teresa Mary Caregiver" FAMILY Record.
1293    
1294    This record has the adoptive mother of "Joseph Tag Torture." The husband is not known.
1295    1 CHAN  
1296    2 DATE 11 Jan 2001
1297    3 TIME 16:50:06
1298    0 @N35@ NOTE Comments on "Joseph Tag Torture-Elizabeth Second Smith" FAMILY Record.
1299    
1300    This record has a second marriage for "Joseph Tag Torture" and the family has one child.
1301    1 CHAN  
1302    2 DATE 11 Jan 2001
1303    3 TIME 16:50:21
1304    0 @N36@ NOTE Comments on "Standard GEDCOM Filelinks-Torture GEDCOM Matriarch" FAMILY record.
1305    
1306    The children in this family test logical extensions to the GEDCOM method for linking to a multimedia file.
1307    1 CHAN  
1308    2 DATE 11 Jan 2001
1309    3 TIME 16:51:33
1310    0 @N37@ NOTE Comments on "Charlie Accented ANSEL-Lucy Special ANSEL" FAMILY Record.
1311    
1312    The two spouses in this family test reading of the ANSEL character set.
1313    1 CHAN  
1314    2 DATE 11 Jan 2001
1315    3 TIME 16:52:38
1316    0 @N38@ NOTE Comments on "<unknown>-Nonstandard Multimedia Filelinks" FAMILY Record.
1317    
1318    The record is simply used to make family connections between records in this file.
1319    1 CHAN  
1320    2 DATE 11 Jan 2001
1321    3 TIME 16:53:38
1322    0 @N4@ NOTE Comments on "Joseph Tag Torture" INDIVIDUAL Record.
1323    
1324    This record contains all possible types of data that can be stored in an INDIVIDUAL (INDI) GEDCOM record. Here are some comments on the data tested here and things to look for when this file is imported into any GEDCOM application:
1325    
1326    1. This record has two NAME structures. How will a program handle this type of data which is allowed in GEDCOM? (Because some GEDCOM files get very bothered by a second name, the files TGC551.ged and TGC551LF files are identical to the TGC55.ged and TGC55LF.ged files except only one name structure is used for this individual - hence the "1" in their names).
1327    
1328    2. The first NAME structure has all possible subordinate tags for a NAME structure including source and notes a source citation and some notes. The second NAME structure (when used) has a source citation and some notes. Are these all imported?
1329    
1330    3. The Birth and Death events use all possible fields including subordinate tags, sources, multimedia links (in Birth), and notes. The birth data has an attached family link which is sometimes needed in case of ambiguous parentage.
1331    
1332    4. This individual has two spouses. The links to the spouses have attached notes.
1333    
1334    5. This individual has two sets of parents - natural parents and adoptive parents. Each parent link has attached notes. The adoptive parents has a subordinate pedigree (PEDI) tag.
1335    
1336    6. This individual has all possible events (including a generic event or EVEN structure). The GEDCOM tags for the events are given in the TYPE tag of each event. Some comments are:
1337         a. The baptism record has all possible tags for event detail.
1338         b. There are 2 christening records to see how programs react to duplicate events (which are allowed).
1339         c. The adoption event has a family link to give more information about adoptive parentage.
1340         d. The cremation event (CREM) has no data except a "Y" in the first line to indicate that the event has occurred. The importing software should keep this event in this record even though it contains no data (The GEDCOM tag is not in this TYPE tag).
1341         e. The LDS Baptism event tests all possible detail tags for an LDS ordinance.
1342         f. The LDS confirmation has no data except a "Y" in the first line to indicate that the event has occurred. The importing software should keep this event in this record even though it contains no data.
1343         g. The date fields in the various events test the possible GEDCOM methods for expressing dates, approximate dates, date ranges, and interpreted dates. There are also a few Hebrew dates, French Republic dates. and "B.C" dates.
1344    
1345    7. The residence structure use all possible subordinate tags in the address part of the residence.
1346    
1347    8. This individual has all possible attributes. The GEDCOM tags for the attributes are given in the TYPE tag of each attribute. Some notes are:
1348         a. There are 2 occupation attributes to test how programs handle multiple tags of the same type (which is allowed).
1349         b. The first OCCU attribute uses all possible subordinate tags for an attribute.
1350    
1351    9. This record has three note structures. The first is this set of notes which is in a separate NOTE record. The other two are NOTE structures embedded in the record. Are all imported and kept separate? Furthermore, the two embedded note structures have subordinate source citations. The second set of notes has a source citation to a SOURCE record and the third set of notes has an embedded source citation.
1352    
1353    10. This record has three source citations. Two are citations to a SOURCE record; one is an embedded source citation (used in older GEDCOM files).
1354    
1355    11. This record has one link to a multimedia file. For more testing of multimedia links, see the "Standard GEDCOM Filelinks," "Nonstandard Multimedia Filelinks," "General Custom Filelinks," and "Extra URL Filelinks" INDIVIDUAL records.
1356    
1357    12. This individual has one alias and two associations. All possible tags in the first association link are used.
1358    
1359    13. This record is linked to a submitter and to two submitters with interest in the ancestors and descendants of this individual.
1360    
1361    14. This record has all remaining tags allowed in individual records for user reference number, record ID, record file number, ancestral file number, and the changed date.
1362    1 CHAN  
1363    2 DATE 12 Jan 2001
1364    3 TIME 0:36:39
1365    0 @N5@ NOTE Notes on this LDS event. All possible LDS ordinance detail tags are used in this event.
1366    1 CHAN  
1367    2 DATE 6 Mar 2000
1368    3 TIME 22:05:42
1369    0 @N6@ NOTE Notes on this LDS Spouse Sealing Event.
1370    1 SOUR @SOURCE1@
1371    1 CHAN  
1372    2 DATE 26 May 1999
1373    3 TIME 22:38:25
1374    0 @N7@ NOTE This source citation has all fields possible in a source citation to a separate SOURCE record. Besides the link to the SOURCE record there are possible fields about this citation (e.g., PAGE, TEXT, etc.)
1375    
1376    These notes on the source citation are in a separate NOTE record.
1377    1 CHAN  
1378    2 DATE 13 Jun 2000
1379    3 TIME 16:02:33
1380    0 @N8@ NOTE Some specific note about the birth event.
1381    
1382    These notes are in a separate NOTE record. These notes also have their own source citation structure.
1383    1 SOUR @SR2@
1384    2 PAGE 102
1385    2 EVEN Event type cited in source
1386    3 ROLE Role in cited event
1387    2 DATE 1 Juin 1945
1388    2 TEXT
1389    3 CONT Here is some text from the source. The source is about the notes for the birth event.
1390    2 QUAY 3
1391    2 NOTE @N9@
1392    1 CHAN  
1393    2 DATE 18 Jun 2000
1394    3 TIME 1:09:46
1395    0 @N9@ NOTE These are notes in a NOTE record. It is a bit redundant, but you can add source citations directly to NOTE records in addition to adding source citations to the initial GEDCOM structure that the notes are about.
1396    
1397    This example source citation in a NOTE record has all possible source citation fields filled in.
1398    1 CHAN  
1399    2 DATE 9 Jun 1999
1400    3 TIME 13:16:57
1401    0 @R1@ REPO
1402    1 NAME Family History Library
1403    1 ADDR
1404    2 CONT 35 North West Temple
1405    2 CONT Salt Lake City, UT 84111
1406    2 CONT USA
1407    2 ADR1 35 North West Temple
1408    2 ADR2 Across the street from Temple Square
1409    2 CITY Salt Lake City
1410    2 STAE Utah
1411    2 POST 84111
1412    2 CTRY USA
1413    1 PHON +1-801-240-2331 (information)+1-801-240-1278 (gifts & donations)+1-801-240-2584 (support)
1414    1 NOTE @N2@
1415    1 REFN User Ref Number
1416    2 TYPE Sample
1417    1 RIN 1
1418    1 CHAN  
1419    2 DATE 12 Mar 2000
1420    3 TIME 10:36:02
1421    0  SOUR
1422    1 DATA  
1423    2 EVEN BIRT, CHR
1424    3 DATE FROM 1 JAN 1980 TO 1 FEB 1982
1425    3 PLAC Anytown, Anycounty, USA
1426    2 EVEN DEAT
1427    3 DATE FROM 1 JAN 1980 TO 1 FEB 1982
1428    3 PLAC County Some, Ireland
1429    1 AGNC Responsible agency for data in this source
1430    1 NOTE A note about data in source.
1431    2 CONT
1432    2 CONT This note includes a blank line before this text. These notes are used to describe the data in this source. Notes about the source itself are usually entered in a different set of notes.
1433    1 AUTH
1434    2 CONT Author or Authorss of this Source using multiple lines if necessary.
1435    2 CONT Here is a new line in this field
1436    1 TITL
1437    2 CONT Everything You Every Wanted to Know about GEDCOM Tags, But Were Afraid to Ask!
1438    2 CONT You can start new lines in this field too.
1439    1 ABBR All About GEDCOM Tags
1440    1 PUBL
1441    2 CONT Details of the publisher of this source using multiple lines if necessary.
1442    2 CONT Here is a new line in this field
1443    1 TEXT
1444    2 CONT This section is used to generic text from the course. It will usually be a quote from the text that is relevant to the use of this source in the current GEDCOM file.
1445    2 CONT
1446    2 CONT It may use as many lines as needed.
1447    1 REPO @R1@
1448    2 NOTE A short note about the repository link. This note is about the repository (if more information is needed other than call number and simple description). Notes about the Source itself are usually entered elsewhere.
1449    2 CALN 920.23
1450    3 MEDI Book (or other description of this source)
1451    1 OBJE  
1452    2 FORM jpeg
1453    2 TITL JPEG image file link
1454    2 FILE ImgFile.JPG
1455    2 NOTE @N14@
1456    1 NOTE @N15@
1457    1 NOTE These are notes embedded in the SOURCE Record instead of in a separate NOTE RECORD.
1458    1 REFN User Reference Number
1459    2 TYPE User Reference Type
1460    1 RIN 1
1461    1 CHAN  
1462    2 DATE 14 Jan 2001
1463    3 TIME 14:29:25
1464    0 @SR2@ SOUR
1465    1 AUTH
1466    2 CONT Second Source Author
1467    1 TITL
1468    2 CONT All I Know About GEDCOM, I Learned on the Internet
1469    1 ABBR What I Know About GEDCOM
1470    1 PUBL
1471    1 TEXT
1472    1 NOTE @N16@
1473    1 RIN 2
1474    1 CHAN  
1475    2 DATE 11 Jan 2001
1476    3 TIME 16:21:39
1477    0  SUBM
1478    1 NAME John A. Nairn
1479    1 ADDR
1480    2 CONT Submitter address line 1
1481    2 CONT Submitter address line 2
1482    2 CONT Submitter address line 3
1483    2 CONT Submitter address line 4
1484    2 ADR1 Submitter address line 1
1485    2 ADR2 Submitter address line 2
1486    2 CITY Submitter address city
1487    2 STAE Submitter address state
1488    2 POST Submitter address ZIP code
1489    2 CTRY Submitter address country
1490    1 PHON Submitter phone number 1Submitter phone number 2Submitter phone number 3 (last one!)
1491    1 OBJE  
1492    2 FORM jpeg
1493    2 TITL Submitter Multimedia File
1494    2 FILE ImgFile.JPG
1495    2 NOTE @N1@
1496    1 LANG English
1497    1 RFN Submitter Registered RFN
1498    1 RIN 1
1499    1 CHAN  
1500    2 DATE 7 Sep 2000
1501    3 TIME 8:35:36
1502    0 @SM2@ SUBM
1503    1 NAME Secondary Submitter
1504    1 ADDR
1505    2 CONT Secondary Submitter Address 1
1506    2 CONT Secondary Submitter Address 2
1507    1 LANG English
1508    1 RIN 2
1509    1 CHAN  
1510    2 DATE 12 Mar 2000
1511    3 TIME 10:38:33
1512    0 @SM3@ SUBM
1513    1 NAME H. Eichmann
1514    1 ADDR
1515    2 CONT email: h.eichmann@@mbox.iqo.uni-hannover.de
1516    2 CONT or: heiner_eichmann@@h.maus.de (no more than 16k!!!!)
1517    1 RIN 3
1518    1 CHAN  
1519    2 DATE 13 Jun 2000
1520    3 TIME 17:07:32
1521    0 TRLR  
1522    

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26