« back to all changes in this revision
Viewing changes to docs/ll-userguide.xml
- browse files at revision 4
- compare with another revision
- download diff
- download tarball
- view history from revision 4
- Committer: Bazaar Package Importer
- Author(s): Felipe Augusto van de Wiel (faw)
- Date: 2007-05-23 23:49:53 UTC
- mfrom: (3.1.3 edgy)
- Revision ID: james.westby@ubuntu.com-20070523234953-ogno9rnbmth61i7p
Tags: 3.0.50-2etch1
* Changing docs/ll-reportmanual.xml and docs/ll-userguide.xml to fix
documentation build problems (Closes: #418347).
* lifelines-reports
- Adding a dependency to lifelines >= 3.0.50 to prevent file conflict.
(Closes: #405500).
* Updating French translation. Thanks to Bernard Adrian. (Closes: #356671).
documentation build problems (Closes: #418347).
* lifelines-reports
- Adding a dependency to lifelines >= 3.0.50 to prevent file conflict.
(Closes: #405500).
* Updating French translation. Thanks to Bernard Adrian. (Closes: #356671).
- files added:
- debian/patches/004_Makefile.am.dpatch
- reports/desc-tex2
- reports/novel
- reports/pedtex
- reports/ps-fan
- files removed:
- debian/patches/001_french-update.dpatch
- files modified:
- .linesrc
added
removed
docs/ll-userguide.xml
1
<?xml version='1.0' encoding='iso-8859-1'?>
2
3
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
4
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"
5
[<!ENTITY llversion '3.0.37'>]>
6
7
<book id="docbook">
8
9
<bookinfo>
10
11
12
<!--
13
14
this is lifelines.xml
15
16
To use this file with SGML software, replace the text above
17
this comments section with the following:
18
19
_________________________________________________________
20
21
<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
22
<!entity llversion "3.0.36">
23
]>
24
25
<book id="docbook">
26
<?dbhtml filename="ll-doc.htm">
27
<bookinfo>
28
_________________________________________________________
29
30
31
Rafal Prinke <rafalp@amu.edu.pl> 1-Apr-200
32
- Converted original LifeLines Reference Guide to DocBook SGML.
33
34
35
Marc Nozell <marc@nozell.com> 26-Jul-2001
36
- Changed <simpara> to <para>. Newer docbook likes it better.
37
38
Marc Nozell <marc@nozell.com> 21-Sep-2000
39
- updated license info
40
- point to lifelines.sourceforge.net
41
- change references from lines302 to llines
42
- make most lines less than 80 characters wide
43
44
Rafal Prinke <rafalp@amu.edu.pl> 30-Dec-2001
45
- Converted to XML.
46
- closed all <para> elements
47
- defined and corrected llversion entity
48
- closed empty tag <void />
49
- converted all tags to lower case
50
- replaced ampersands with entities
51
- added space at end of line
52
- parsed against DocBook 4.1.2 DTD
53
54
-->
55
<!-- ================================================= -->
56
57
<title>
58
59
<application>LifeLines</application> Documentation
60
</title>
61
62
<authorgroup>
63
<author>
64
<firstname>Thomas T. </firstname>
65
<surname>Wetmore </surname>
66
<lineage>IV</lineage>
67
</author>
68
</authorgroup>
69
70
<subtitle><application>LifeLines</application> Version &llversion;</subtitle>
71
</bookinfo>
72
73
<chapter>
74
75
<title>
76
77
Users' Manual
78
79
</title>
80
81
<sect1>
82
83
84
<title>
85
86
INTRODUCTION
87
88
</title>
89
90
91
92
<para>
93
94
<application>LifeLines</application> is a genealogy program
95
that runs on <acronym>UNIX</acronym> systems. It maintains
96
genealogical records (persons, families, sources, events and
97
others) in a database, and generates reports from those
98
records. There are no practical limits on the number of
99
records that can be stored in a
100
<application>LifeLines</application> database, nor on the
101
amounts or kinds of data that can be kept in the
102
records. <application>LifeLines</application> does not contain
103
built-in reports. Instead it provides a programming subsystem
104
that you use to program your own reports and charts. The
105
programming subsystem also lets you query your databases and
106
process your data in any
107
way. <application>LifeLines</application> uses the terminal
108
independent features of <acronym>UNIX</acronym> to provide a
109
screen and menu based user interface.
110
111
</para>
112
113
114
115
<para>
116
117
<application>LifeLines</application> is a non-commercial,
118
experimental system that is use at your own risk software. I
119
developed <application>LifeLines</application> for personal
120
use and shared it with friends. Enough of a demand arose
121
through word of mouth and internet, that I have made the
122
<application>LifeLines</application> source code and other
123
information freely available under an MIT-style license
124
reproduced below:
125
126
</para>
127
128
<para>
129
<quote>
130
Copyright (c) 1991-1999 Thomas T. Wetmore IV
131
132
Permission is hereby granted, free of charge, to any person obtaining
133
a copy of this software and associated documentation files (the
134
"Software"), to deal in the Software without restriction, including
135
without limitation the rights to use, copy, modify, merge, publish,
136
distribute, sublicense, and/or sell copies of the Software, and to
137
permit persons to whom the Software is furnished to do so, subject to
138
the following conditions:
139
140
The above copyright notice and this permission notice shall be
141
included in all copies or substantial portions of the Software.
142
143
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
144
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
145
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
146
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
147
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
148
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
149
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
150
151
</quote>
152
153
</para>
154
155
<para>
156
157
The source code, documentation and a collection of report
158
scripts are located at <ulink url="http://lifelines.sourceforge.net/">
159
http://lifelines.sourceforge.net/</ulink>. You can also find
160
binary kits for some platforms. If you are a developer and
161
wish to contribute enhancements, please sign up on sourceforge
162
and contact <ulink url="mailto:marc@nozell.com"> Marc
163
Nozell</ulink> who is currently managing the project.
164
</para>
165
166
<note>
167
<para>
168
Prior to 1999, Lifelines was available on the ftp sites,
169
<ulink url="ftp://ftp.cac.psu.edu">ftp.cac.psu.edu</ulink> and
170
<ulink url="ftp://hoth.stsci.edu">hoth.stsci.edu</ulink>.
171
Please use sourceforge instead.
172
</para>
173
</note>
174
175
</sect1>
176
177
178
179
<sect1>
180
181
<title>
182
INSTALLATION
183
</title>
184
185
<para>
186
You may be installing <application>LifeLines</application>
187
from a source distribution package or as an executable program
188
already prepared for your <acronym>UNIX</acronym>
189
(or <acronym>MS-Windows</acronym>) system. The
190
source distribution comes with the readme, build script and
191
make files necessary to build
192
<application>LifeLines</application>. Follow the instructions
193
in the readme file. A number of executables are built
194
which can be put it in a
195
directory in your execution path. If you get the program in
196
executable form, follow whatever instructions came with it.
197
</para>
198
<glosslist>
199
<glossentry><glossterm><command>llines</command></glossterm><glossdef>
200
<para>
201
the <application>LifeLines</application> program with full user interface
202
</para>
203
</glossdef></glossentry>
204
205
<glossentry><glossterm><command>llexec</command></glossterm><glossdef>
206
<para>
207
a stripped down version of the
208
<application>LifeLines</application> program, without the user interface
209
for non-interactive processing of report programs
210
</para>
211
</glossdef></glossentry>
212
213
<glossentry><glossterm><command>dbverify</command></glossterm><glossdef>
214
<para>
215
a utility program to verify <application>LifeLines</application> databases.
216
</para>
217
</glossdef></glossentry>
218
</glosslist>
219
220
<para>
221
The source distribution package also contains documentation
222
and some <application>LifeLines</application> programs.
223
Included with these in the reports directory is a brief overview
224
of the reports in the file index.html.
225
</para>
226
227
228
</sect1>
229
230
231
232
<sect1>
233
234
235
236
<title>
237
238
STARTING <application>LIFELINES</application> AND CREATING DATABASES
239
240
</title>
241
242
243
244
<para>
245
246
You normally start <application>LifeLines</application> with
247
the command: <userinput><command>lines</command> <replaceable class="parameter">database</replaceable></userinput> where
248
database is the name of a <application>LifeLines</application>
249
database. If <application>LifeLines</application> finds the
250
database, <application>LifeLines</application> opens the
251
database and takes you to the program's main menu. If the
252
database doesn't exist, <application>LifeLines</application>
253
asks whether it should create it, and if you answer yes, does
254
so. You may create any number of databases, but only one can
255
be accessed by <application>LifeLines</application> at a
256
time. If you built the <application>LifeLines</application>
257
executable from the source package, the executable may be
258
named <command>llines</command> rather than
259
<command>lines</command>. You may either change its name or
260
invoke <application>LifeLines</application> by using the
261
command <command>llines</command> instead.
262
263
</para>
264
265
266
267
<para>
268
269
The full command line interface to
270
<application>LifeLines</application> is:
271
272
<synopsis>
273
<command>lines</command> <option>[-acdfiklnortuwxzCFI]</option><replaceable class="parameter">[database]</replaceable>
274
</synopsis>
275
276
</para>
277
278
279
280
<para>
281
282
The following options are supported:
283
284
</para>
285
286
<informaltable pgwide='0' frame='none'>
287
<tgroup cols='2'>
288
<colspec colwidth='0.5in'></colspec>
289
<tbody>
290
291
<row>
292
<entry>-C</entry>
293
<entry>Specify configuration file location (e.g.
294
-C/home/bill/lifelines/.linesrc2 )</entry>
295
</row>
296
297
<row>
298
<entry>-F</entry>
299
<entry>Finnish option (only available if so compiled)
300
</entry>
301
</row>
302
303
<row>
304
<entry>-I</entry>
305
<entry>
306
Specify a user property (e.g. -ILLEDITOR=gvim )
307
</entry>
308
</row>
309
310
<row>
311
<entry>-a</entry>
312
<entry>log dynamic memory operation (for debugging)</entry>
313
</row>
314
315
<row>
316
<entry>-c</entry>
317
<entry>supply cache values (eg, -ci400,4000f400,4000 sets direct indi & fam
318
caches to 400, and indirect indi & fam caches to 4000)
319
</entry>
320
</row>
321
322
<row>
323
<entry>-d</entry>
324
<entry>
325
debug mode (signal protection disabled for convenience with breakpoints)
326
</entry>
327
</row>
328
329
<row>
330
<entry>-f</entry>
331
<entry>
332
force open the database - use only in emergency
333
</entry>
334
</row>
335
336
<row>
337
<entry>-i</entry>
338
<entry>
339
open database with immutable access (no protection against other
340
access -- for use on read-only media)
341
</entry>
342
</row>
343
344
<row>
345
<entry>-k</entry>
346
<entry>
347
always show keys (normally keys are suppressed if REFN available)
348
</entry>
349
</row>
350
351
<row>
352
<entry>-l</entry>
353
<entry>
354
lock (-ly) or unlock (-ln) a database for use with read only media
355
(access to a locked database is treated as immutable)
356
</entry>
357
</row>
358
359
<row>
360
<entry>-n</entry>
361
<entry>
362
do not use traditional family rules
363
</entry>
364
</row>
365
366
<row>
367
<entry>-o</entry>
368
<entry>
369
Specify program output directory (eg, -o/tmp/mytests)
370
</entry>
371
</row>
372
373
<row>
374
<entry>-r</entry>
375
<entry>
376
open database with read-only access (protect against other
377
writer access)
378
</entry>
379
</row>
380
381
<row>
382
<entry>-t</entry>
383
<entry>
384
trace function calls in report programs (for debugging)
385
</entry>
386
</row>
387
388
<row>
389
<entry>-u</entry>
390
<entry>
391
specify window size (eg, -u120,34 specifies 120 columns by 34 rows)
392
</entry>
393
</row>
394
395
<row>
396
<entry>-w</entry>
397
<entry>
398
open database with writeable access (protect against other
399
writer or reader access)
400
</entry>
401
</row>
402
403
<row>
404
<entry>-x</entry>
405
<entry>
406
execute a single lifelines report program directly
407
</entry>
408
</row>
409
410
<row>
411
<entry>-z</entry>
412
<entry>
413
Use normal ASCII characters for drawing lines in user interface rather
414
than the vt100 special characters.
415
</entry>
416
</row>
417
418
</tbody>
419
</tgroup>
420
</informaltable>
421
422
<para>
423
424
The <option>-r</option> option opens the database with read-only
425
access. When in this mode
426
<application>LifeLines</application> will not let you modify
427
the database; no other operations are affected. The
428
<option>-w</option> option opens the database with writeable
429
access. If the database cannot be opened with the requested
430
mode <application>LifeLines</application> quits
431
immediately. When you open a database with neither the
432
<option>-r</option> or <option>-w</option> options,
433
<application>LifeLines</application> first tries to open the
434
database with writeable access; if not possible
435
<application>LifeLines</application> then tries to open the
436
database with read-only access; and if this is not possible
437
<application>LifeLines</application> quits. A
438
<application>LifeLines</application> database may be open
439
simultaneously by any number of programs with read-only
440
access; however, if a database is open by a program with
441
writeable access, then it cannot be opened by any other other
442
program.
443
444
</para>
445
446
447
448
<para>
449
450
In rare situations the read/write mode mechanism can fail;
451
when this happens a database may appear unopenable. If this
452
happens use the <option>-f</option> option to force open the
453
database; this will open the database and reset the mode
454
mechanism. This is a dangerous feature; you can use it to open
455
the same database with writeable access more than once; the
456
results are unpredictable and generally disastrous.
457
458
</para>
459
460
<para>
461
462
The multiuser protection supplied by this reader/writer access
463
mechanism is provided via a flag setting in the database, so both
464
read-only and writeable access actually alter the database (read-only
465
access only alters the value of this flag). For truly read-only
466
access, e.g., for use with read-only media, the best solution is to
467
lock (-ly) the database before copying it to the read-only media. This
468
annotates the database itself as being for immutable access.
469
Alternatively, to use a database already on read-only media and not
470
so annotated, use the immutable (-i) flag.
471
472
</para>
473
474
<para>
475
476
If you don't give the name of a database on the command line,
477
<application>LifeLines</application> will prompt you for
478
it. If you do not use the <envar>LLDATABASES</envar> shell
479
variable or user options (described later), the name you enter must be the
480
name of a <application>LifeLines</application> database
481
directory expressed using normal <acronym>UNIX</acronym>
482
absolute or relative path naming. If you do use the
483
<envar>LLDATABASES</envar> variable,
484
<application>LifeLines</application> will search for the
485
database in the directories named in the variable; this can be
486
very convenient.
487
488
</para>
489
490
<para>
491
492
If you would like to choose a database from a list of existing ones,
493
enter a single question mark and press return when
494
<application>LifeLines</application> prompts you for the database name.
495
<application>LifeLines</application> will then display a list of all
496
databases that it can find, and you may select one from the list.
497
498
</para>
499
500
501
</sect1>
502
503
504
505
<sect1>
506
507
508
509
<title>
510
511
INTRODUCTION TO <acronym>GEDCOM</acronym>
512
513
</title>
514
515
516
517
<para>
518
519
<application>LifeLines</application> records are stored in
520
<acronym>GEDCOM</acronym> format; you organize, edit and
521
maintain your data in this format. <acronym>GEDCOM</acronym>
522
is a standard that defines a file format for moving
523
genealogical data between computer
524
systems. <application>LifeLines</application> has adopted this
525
format for structuring the records in its databases. This
526
approach provides a structured yet flexible method for storing
527
all the data you wish to record. There are few restrictions on
528
the format, amount or type of information you may store in a
529
<application>LifeLines</application> database.
530
531
</para>
532
533
534
535
<para>
536
537
<acronym>GEDCOM</acronym> is defined at two levels. At the
538
syntactic level <acronym>GEDCOM</acronym> is a simple set of
539
rules for organizing and structuring data into records, with
540
no concern about the types of records, types or formats of
541
information in the records, or the relationships between
542
records. At the semantic level <acronym>GEDCOM</acronym> adds
543
an additional set of rules that specify what record types are
544
allowed, how records must be structured, how data within the
545
records must be identified and formatted, and what specific
546
relationships between the record types are allowed. In
547
principle there can be multiple semantic versions of
548
<acronym>GEDCOM</acronym>, though in practice there is only
549
one, lineage-linked <acronym>GEDCOM</acronym>. Unfortunately
550
this semantic version of <acronym>GEDCOM</acronym> is poorly
551
defined, and every genealogical system has interpreted it in
552
different ways.
553
554
</para>
555
556
557
558
<para>
559
560
<application>LifeLines</application> uses
561
<acronym>GEDCOM</acronym> primarily at the syntactic level,
562
though it does impose a few of the generally accepted
563
lineage-linked semantic restrictions. This means some
564
important things. It means that you can store all your
565
genealogical data in your <application>LifeLines</application>
566
database, and that you have wide freedom in how you choose
567
your own conventions for structuring and formatting your
568
data. But it also means that the way you store data in your
569
databases can be different from the way that someone else
570
stores their data. This can be a problem if you share data
571
with others or share report programs with other
572
<application>LifeLines</application> users. My recommendation
573
is to use <acronym>GEDCOM</acronym> lineage-linking
574
conventions wherever possible.
575
576
</para>
577
578
579
580
<para>
581
582
<application>LifeLines</application> does not use forms or
583
screens to guide you through entering or changing
584
data. Instead you use a screen editor and directly edit the
585
data records. This requires you to understand the
586
<acronym>GEDCOM</acronym> format, and be able to edit data in
587
<acronym>GEDCOM</acronym> format, before you can use
588
<application>LifeLines</application>. The
589
<acronym>GEDCOM</acronym> format is quite simple; this
590
introduction will provide all you need to know about
591
<acronym>GEDCOM</acronym> in order to use
592
<application>LifeLines</application>.
593
594
</para>
595
596
597
598
<para>
599
600
Here is an example <acronym>GEDCOM</acronym> person record:
601
602
<example>
603
604
<title>
605
606
<acronym>GEDCOM</acronym> person record
607
608
</title>
609
610
<programlisting role="gedcom">
611
0 @I25@ INDI
612
1 NAME <userinput>Thomas Trask /Wetmore/ Sr</userinput>
613
1 SEX <userinput>M</userinput>
614
1 BIRT
615
2 DATE <userinput>13 March 1866</userinput>
616
2 PLAC <userinput>St. Mary's Bay, Digby, Nova Scotia</userinput>
617
2 SOUR <userinput>Social Security application</userinput>
618
1 NATU
619
2 NAME <userinput>Thomas T. Wetmore</userinput>
620
2 DATE <userinput>26 October 1888</userinput>
621
2 PLAC <userinput>Norwich, New London, Connecticut</userinput>
622
2 AGE <userinput>22 years</userinput>
623
2 COUR <userinput>New London County Court of Common Pleas</userinput>
624
2 SOUR <userinput>court record from National Archives</userinput>
625
1 OCCU <userinput>Antiques Dealer</userinput>
626
1 DEAT
627
2 NAME <userinput>Thomas Trask Wetmore</userinput>
628
2 DATE <userinput>17 February 1947</userinput>
629
2 PLAC <userinput>New London, New London, Connecticut</userinput>
630
2 AGE <userinput>80 years, 11 months, 4 days</userinput>
631
2 CAUS <userinput>Heart Attack</userinput>
632
2 SOUR <userinput>New London Death Records</userinput>
633
1 FAMC @F11@
634
1 FAMS @F6@
635
1 FAMS @F12@
636
637
</programlisting></example>
638
639
</para>
640
641
642
643
<para>
644
645
A <acronym>GEDCOM</acronym> record is made up of lines. Each
646
line has a level number and a tag, and most lines have a value
647
following the tag. The first line in every record has a
648
cross-reference index between the level number and the tag.
649
650
</para>
651
652
653
654
<para>
655
656
Level numbers allow data to be structured to any degree of
657
detail; lines with higher level numbers expand on lines with
658
lower numbers. Each record begins at level 0, and each deeper
659
level increments the level by
660
one. <application>LifeLines</application> does not restrict
661
the structuring depth. Tags are uppercase (by convention) code
662
words that specify the kind of information on the line or on
663
the higher numbered lines that follow. The information after
664
the tag, if any, is the value of the line.
665
666
</para>
667
668
669
670
<para>
671
672
The first line in a record indicates its type. There are four
673
fixed record types in <application>LifeLines</application>
674
databases: person, family, source and event. The first, 0
675
level line in these records have tags
676
<structname>INDI</structname>, <structname>FAM</structname>,
677
<structname>SOUR</structname> and
678
<structname>EVEN</structname>, respectively. Besides these
679
record types, you may create your own record types by using
680
any other tag on the 0 level line of a record. The lines that
681
begin records are the only level 0 lines used in
682
<application>LifeLines</application>. Each level 0 line has a
683
cross-reference index between the level number and the
684
tag. This index is the record's internal reference key; other
685
records may refer to this record by using this index.
686
Cross-reference indexes are bracketed by @ characters.
687
688
</para>
689
690
691
692
<para>
693
694
The first line in the example record has the
695
<structname>INDI</structname> tag, identifying it as a
696
person. The cross-reference index value, I25, can be used by
697
other records to refer to this record.
698
699
</para>
700
701
702
703
<para>
704
705
The second line in the example has the person's name. Each
706
person record in a <application>LifeLines</application>
707
database must have at least one <structfield>1
708
NAME</structfield> line, and its value must be in
709
<acronym>GEDCOM</acronym> name format. This format allows
710
names to be as long as needed, but the surname, which may be
711
placed anywhere in the name, must be separated from the rest
712
of the name by one or two slashes. For example:
713
714
<example>
715
716
<title>
717
Example of NAME formats
718
719
</title>
720
721
<programlisting>
722
1 NAME <userinput>John/Smith</userinput>
723
1 NAME <userinput>John /Smith/</userinput>
724
1 NAME <userinput>John/Smith/Jr.</userinput>
725
</programlisting>
726
</example>
727
728
</para>
729
730
731
732
<para>
733
734
The second slash is required only if name elements follow the
735
surname. White space is optional before the first slash and
736
after the second. If you don't know a person's surname, or the
737
person doesn't have a surname, you may use / or // or no
738
slashes at all. For example:
739
740
<example>
741
742
<title>
743
Example of searching on NAMEs
744
</title>
745
746
<programlisting>
747
748
1 NAME <userinput>Mary//</userinput>
749
1 NAME <userinput>Mary/</userinput>
750
1 NAME <userinput>Mary</userinput>
751
</programlisting>
752
753
</example>
754
755
are all ways to enter a person named Mary with no known
756
surname. A person may have any number, including zero, given
757
names and/or initials. A <application>LifeLines</application>
758
person record may have any number of <structfield>1
759
NAME</structfield> lines, though the person will be displayed
760
with the first name value only. Persons are indexed under all
761
their names, however, so you will be able to search for
762
persons by any of their names.
763
</para>
764
765
766
767
<para>
768
769
The next line in the example gives the person's
770
sex. <application>LifeLines</application> doesn't require a
771
<structfield>1 SEX</structfield> line, but you should include
772
it. The value of the line should be <userinput>M</userinput>
773
or <userinput>F</userinput> if the sex is known; it can be
774
left blank or set to <userinput>U</userinput> or
775
<userinput>?</userinput>, say, if not known. A person must
776
have a <structfield>1 SEX</structfield> line with a value of
777
either <userinput>M</userinput> or <userinput>F</userinput>
778
before he or she can be made a spouse or parent in a family.
779
780
</para>
781
782
783
784
<para>
785
786
The example record also contains three events: birth,
787
naturalization, and death. An event begins with a level 1 line
788
whose tag indicates the event type. For example,
789
<structfield>BIRT</structfield> is the tag for a birth event.
790
791
</para>
792
793
794
795
<para>
796
797
Events usually have at least a <structfield>2
798
DATE</structfield> and a <structfield>2 PLAC</structfield>
799
line and often a <structfield>2 SOUR</structfield> line. The
800
<structfield>DATE</structfield> and
801
<structfield>PLAC</structfield> lines give the date and place
802
of the event. The value of a
803
<application>LifeLines</application>
804
<structfield>DATE</structfield> line is free format, though
805
<application>LifeLines</application> will try to parse it for
806
specific day, month and year information. The value of a
807
<structfield>PLAC</structfield> line is usually a
808
comma-separated list of geopolitical units, starting with the
809
most specific, ending with the most general. The
810
<structfield>SOUR</structfield> line indicates the source of
811
information about the event. The
812
<structfield>SOUR</structfield> line can be the root of a full
813
description of the source, or the value of the
814
<structfield>SOUR</structfield> line can be a cross-reference
815
key that refers to the source record that describes the
816
source.
817
818
</para>
819
820
821
822
<para>
823
824
The naturalization event (with tag
825
<structfield>NATU</structfield>) shows a few other lines. The
826
<structfield>2 NAME</structfield> line gives the person's name
827
as recorded in the source (only <structfield>1
828
NAME</structfield> lines must follow <acronym>GEDCOM</acronym>
829
format). The <structfield>2 AGE</structfield> line gives the
830
person's age at the time of the event. The <structfield>2
831
COUR</structfield> line indicates the court where
832
naturalization occurred.
833
834
</para>
835
836
837
838
<para>
839
840
The final event is a death event (tag
841
<structfield>DEAT</structfield>). The <structfield>2
842
CAUS</structfield> line gives the cause of death.
843
844
</para>
845
846
847
848
<para>
849
850
At the end of the record are three lines that refer to family
851
records. A <structfield>1 FAMC</structfield> line refers to a
852
family record that the person belongs to as a child; its value
853
is the cross-reference index value of that family. A
854
<structfield>1 FAMS</structfield> line refers to a family
855
record that the person belongs to as a spouse or parent.
856
857
</para>
858
859
860
861
<para>
862
863
When using <application>LifeLines</application> to edit a
864
person, you will not be able to edit the cross reference
865
values on the <structfield>0 INDI</structfield>,
866
<structfield>1 FAMC</structfield> or <structfield>1
867
FAMS</structfield> lines; these are maintained by
868
<application>LifeLines</application>.
869
870
</para>
871
872
873
874
<para>
875
876
Here is an example family record:
877
878
<example>
879
880
<title>
881
Example family record
882
</title>
883
884
<programlisting>
885
886
0 @F6@ FAM
887
1 HUSB @I25@
888
1 WIFE @I26@
889
1 MARR
890
2 DATE <userinput>31 March 1891</userinput>
891
2 PLAC <userinput>New London, New London, Connecticut</userinput>
892
2 SOUR <userinput>New London Vital Records</userinput>
893
1 CHIL @I27@
894
1 CHIL @I17@</programlisting></example>
895
896
</para>
897
898
899
900
<para>
901
902
The <structfield>0 FAM</structfield> line assigns the family
903
the cross-reference index of F6. The record contains
904
<structfield>1 HUSB</structfield> and <structfield>1
905
WIFE</structfield> lines that refer to the two
906
spouses/parents. The record also holds a marriage event (tag
907
<structfield>MARR</structfield>) and two <structfield>1
908
CHIL</structfield> lines that refer to two children in the
909
family. When editing family records, you cannot edit the
910
<structfield>0 FAM</structfield>, <structfield>1
911
HUSB</structfield>, <structfield>1 WIFE</structfield>, or
912
<structfield>1 CHIL</structfield> lines; these are maintained
913
by <application>LifeLines</application>.
914
915
</para>
916
917
<para>
918
919
When you create new records for your database, you are free to
920
invent tags and structure your data in any way you see
921
fit. However, it is good practice to use standard
922
<acronym>GEDCOM</acronym> tags and value formats.
923
<application>LifeLines</application> does enforce a small set
924
of conventions that you must obey. Within person records,
925
<application>LifeLines</application> requires that you use
926
<structfield>1 NAME</structfield> and <structfield>1
927
SEX</structfield> lines with their special meanings and value
928
formats. Though not required,
929
<application>LifeLines</application> assumes that you will use
930
<structfield>1 BIRT</structfield>, <structfield>1
931
DEAT</structfield>, <structfield>1 CHR</structfield>, and
932
<structfield>1 BURI</structfield> lines for birth, death,
933
baptism and burial events, respectively. In family records,
934
<application>LifeLines</application> assumes you will use the
935
<structfield>1 MARR</structfield> event for marriage
936
events. Within person records, you are not allowed to use
937
<structfield>0 INDI</structfield>, <structfield>1
938
FAMC</structfield> or <structfield>1 FAMS</structfield> lines,
939
since these are used to maintain linkage information. Within
940
family records, you are not allowed to use <structfield>0
941
FAM</structfield>, <structfield>1 HUSB</structfield>,
942
<structfield>1 WIFE</structfield> or <structfield>1
943
CHIL</structfield> lines.
944
945
</para>
946
947
948
949
<para>
950
951
The indentation shown in the examples is not part of
952
<acronym>GEDCOM</acronym> format. When
953
<application>LifeLines</application> prepares records for you
954
to edit, however, it always indents the records, making them
955
easier to read and understand. You do not need to follow this
956
indentation scheme when you edit the records. Indentation is
957
removed from the data before it is stored in the database.
958
959
</para>
960
961
962
963
</sect1>
964
965
966
967
<sect1>
968
969
970
971
<title>
972
973
MAIN MENU
974
975
</title>
976
977
978
979
<para>
980
981
After <application>LifeLines</application> opens an existing
982
database, or creates a new one, it presents you with the main
983
menu:
984
985
<screen>
986
Please choose an operation:
987
b Browse the persons in the database
988
s Search database
989
a Add information to the database
990
d Delete information from the database
991
p Pick a report from list and run
992
r Generate report by entering report name
993
t Modify character translation tables
994
u Miscellaneous utilities
995
x Handle source, event and other records
996
q Quit program
997
</screen>
998
999
1000
</para>
1001
1002
<para>
1003
1004
Select an operation by striking the proper selection letter.
1005
1006
</para>
1007
1008
1009
1010
<para>
1011
1012
The browse operation lets you browse the database and perform
1013
many operations on the data. The search operation provides some
1014
simple wildcard search capabilities, which lead into browsing
1015
particular records. The add operation lets you add
1016
new information, and the delete operation removes
1017
information. The report operations read report
1018
programs and generates output reports. The modify character
1019
translation tables operation changes the translation
1020
tables. The miscellaneous utilities operation provides such
1021
things as backup and restore. The handle source, event and
1022
other records operation gives you access to these three record
1023
types. The quit operation closes the database and returns to
1024
<acronym>UNIX</acronym>.
1025
1026
</para>
1027
1028
1029
1030
<para>
1031
1032
The browse operation deserves special mention, because it
1033
provides a rich environment for searching, viewing, adding,
1034
modifying, merging and deleting information in the
1035
database. You will find that you operate from the browsing
1036
modes most of the time. The operations are all described in
1037
later sections.
1038
1039
</para>
1040
1041
1042
1043
</sect1>
1044
1045
1046
1047
<sect1>
1048
1049
1050
1051
<title>
1052
1053
CODESET
1054
1055
</title>
1056
1057
<para>
1058
1059
After you have created a new database, and before you actually
1060
add any data to it, is the time to set the codeset to be used
1061
in the database.
1062
1063
</para>
1064
1065
<para>
1066
1067
The codeset (or character encoding, to use precise Unicode
1068
terminology) is the decision as to how letters will be represented
1069
by the computer. If you have only ever used English letters in
1070
computing, you may not have had to encounter this issue, because as
1071
it happens, the English letters (a-z and A-Z) are stored numerically
1072
in the same fashion in almost all codesets used by computers. However,
1073
in the field of genealogy, you are especially likely to meet letters
1074
outside of the English alphabet (for example, accented vowels).
1075
1076
</para>
1077
1078
<para>
1079
1080
You have fundamentally three choices as to what codeset to use in your
1081
database, listed below from easiest to most powerful.
1082
1083
</para>
1084
1085
<para>
1086
1087
First, you may leave it entirely unspecified. This will give the
1088
traditional lifelines behavior. This is really only suitable if either
1089
(a), you only use English (ASCII) data, or (b), you work in an
1090
environment which entirely uses the same 8-bit codeset (eg, a GNU/Linux box
1091
which is all ISO-8859-15), and you only run lifelines in English.
1092
If you use any non-English data on MS-Windows, this is not likely to
1093
be suitable, because the lifelines screens run in the console, but
1094
you are likely to use MS-Windows applications either for editing or
1095
for viewing output, and the MS-Windows console uses a different
1096
codeset from MS-Windows applications. Also, if you use lifelines in a
1097
different language than English, this may not be suitable, because
1098
the gettext message catalogs (for non-English interface) will not
1099
be converted into your codeset.
1100
1101
</para>
1102
1103
<para>
1104
1105
Second, you may specify a particular 8-bit codeset. Assuming that you
1106
have iconv and gettext installed (or you are using the MS-Windows version,
1107
which comes with these), you may specify any 8-bit codeset supported by
1108
iconv, and iconv supports quite many. A natural choice for Western European
1109
languages would be ISO-8859-1, or (for MS-Windows only) CP-1252. With this
1110
option, gettext language files will be converted to your codeset.
1111
1112
</para>
1113
1114
<para>
1115
1116
Third, you may specify the use of UTF-8. This is a Unicode encoding, and is
1117
by far the most powerful option. In fact, this is the only really convenient
1118
way to be able to store, for example, names in English, names in Russian, and
1119
names in Greek, all in the same database, in their native scripts (alphabets).
1120
In recent versions, lifelines has become more knowledgeable about handling
1121
UTF-8, so that, for example, upper & lower casing only work correctly with
1122
versions from 3.0.28 on.
1123
1124
</para>
1125
1126
<para>
1127
1128
To actually specify a codeset, enter it via the u(tility) o(ptions) page (which is
1129
documented below). From the main menu, in the English version, press u to reach
1130
the utility page, and then o to edit the user options. To set a codeset of, e.g.,
1131
ISO-8859-1, enter this string on its own line, without the surrounding quotes:
1132
"codeset=ISO-8859-1". Or, to specify the use of UTF-8, "codeset=UTF-8".
1133
1134
</para>
1135
1136
<para>
1137
1138
Further information about codeset conversion is found in the later chapter of
1139
that name (for example, information about producing reports which make use of
1140
HTML entity names for non-ASCII characters).
1141
1142
</para>
1143
1144
</sect1>
1145
1146
1147
1148
<sect1>
1149
1150
1151
1152
<title>
1153
1154
ENTERING THE FIRST PERSON
1155
1156
</title>
1157
1158
<para>
1159
1160
Note: Before you add the first person to your database, you
1161
specify internal codeset (review the Codeset chapter for
1162
information).
1163
1164
</para>
1165
1166
<para>
1167
1168
Normally you add persons to the database from the browsing
1169
modes, but when entering the first person there is no one in
1170
the database to browse to. To add the first person to a
1171
<application>LifeLines</application> database, first select
1172
the add operation from the main menu. You will be prompted
1173
with the add menu (described later). Strike p to add a
1174
person. <application>LifeLines</application> creates a
1175
template of a <acronym>GEDCOM</acronym> person record, and
1176
puts you in a screen editor to edit the template. The default
1177
template is:
1178
1179
<example>
1180
<title>
1181
Default person record template
1182
</title>
1183
1184
<programlisting>
1185
1186
0 INDI
1187
1 NAME <replaceable>Fname /Surname/</replaceable>
1188
1 SEX <replaceable>MF</replaceable>
1189
1 BIRT
1190
2 DATE
1191
2 PLAC
1192
2 SOUR
1193
1 DEAT
1194
2 DATE
1195
2 PLAC
1196
2 SOUR</programlisting></example>
1197
1198
</para>
1199
1200
1201
1202
<para>
1203
1204
Edit the template to create the new person's record. Change
1205
the name to the person's name. Assign the person's sex by
1206
deleting either <userinput>M</userinput> or
1207
<userinput>F</userinput>. Fill out the birth and death events
1208
as best you can. If the person is alive, remove the death
1209
event. Remove any <structfield>DATE</structfield> and
1210
<structfield>PLAC</structfield> lines you do not have the
1211
information for.
1212
1213
</para>
1214
1215
1216
1217
<para>
1218
1219
The default template provides lines for one birth and one
1220
death event. You can expand the record with other events (even
1221
more birth or death events) and lines. Indentation makes it
1222
easier to read and edit the record, but isn't necessary. You
1223
may change the default edit template by defining the user
1224
option <option>INDIREC</option> (described later).
1225
1226
</para>
1227
1228
1229
1230
<para>
1231
1232
Here is how I might edit the template when creating a record
1233
about myself:
1234
1235
<example>
1236
1237
<title>
1238
Example editing of template record
1239
</title>
1240
1241
<programlisting>
1242
1243
0 INDI
1244
1 NAME <userinput>Thomas Trask /Wetmore/ IV</userinput>
1245
1 SEX <userinput>M</userinput>
1246
1 BIRT
1247
2 DATE <userinput>18 December 1949</userinput>
1248
2 PLAC <userinput>New London, New London, Connecticut</userinput>
1249
2 SOUR <userinput>Birth Certificate</userinput>
1250
1 OCCU <userinput>Software Engineer</userinput>
1251
1 RESI
1252
2 DATE <userinput>1982 to 1995</userinput>
1253
2 PLAC <userinput>Newburyport, Essex, Massachusetts</userinput>
1254
2 ADDR <userinput>2 Barton Street, Newburyport, MA 01950</userinput>
1255
1256
... lots of other events and facts
1257
</programlisting>
1258
</example>
1259
1260
</para>
1261
1262
1263
1264
<para>
1265
1266
When you edit a person record, don't add or modify
1267
<structfield>INDI</structfield>,
1268
<structfield>FAMC</structfield> or
1269
<structfield>FAMS</structfield>
1270
lines. <application>LifeLines</application> creates and
1271
maintains these lines through specific user commands.
1272
1273
</para>
1274
1275
1276
1277
<para>
1278
1279
When you finish editing and leave the editor, you
1280
automatically return to
1281
<application>LifeLines</application>. If you made an error
1282
(eg, didn't use proper level numbers or didn't follow the
1283
proper name convention), <application>LifeLines</application>
1284
displays an error message, and asks if you want to re-edit the
1285
record. If you don't, <application>LifeLines</application>
1286
doesn't add the person to the database.
1287
1288
</para>
1289
1290
1291
1292
<para>
1293
1294
When the record is in proper format,
1295
<application>LifeLines</application> asks if you are sure you
1296
want to add the person to the database. If you answer yes, the
1297
person is added; if you answer no, the person isn't. In both
1298
cases <application>LifeLines</application> returns to the main
1299
menu.
1300
1301
</para>
1302
1303
1304
1305
</sect1>
1306
1307
1308
1309
<sect1>
1310
1311
1312
1313
<title>
1314
1315
SCREEN EDITORS AND ENVIRONMENT VARIABLES
1316
1317
</title>
1318
1319
1320
1321
<para>
1322
1323
With <application>LifeLines</application> you maintain the
1324
database records using a screen editor. This is different than
1325
other genealogical programs where screens or forms are used to
1326
gather the data.The default screen editor for
1327
<application>LifeLines</application> is
1328
<application>vi</application>. (The <acronym>MS-Windows</acronym>
1329
version defaults instead to notepad.exe.) This can be overridden by the
1330
<envar>ED</envar>, <envar>EDITOR</envar> or
1331
<envar>LLEDITOR</envar> environment variables. For example, if
1332
you prefer the emacs screen editor, and if you use a bourne-compatible
1333
shell, you may add the line:
1334
<userinput><envar>ED</envar>=<replaceable>emacs</replaceable></userinput>
1335
to your login profile file, and
1336
<application>LifeLines</application> will use
1337
<application>emacs</application> for editing.
1338
1339
</para>
1340
1341
1342
1343
<para>
1344
1345
There are four other, <application>LifeLines</application>
1346
specific environment variables. They are
1347
<envar>LLDATABASES</envar>, <envar>LLARCHIVES</envar>,
1348
<envar>LLPROGRAMS</envar> and <envar>LLREPORTS</envar>.
1349
<envar>LLDATABASES</envar> and
1350
<envar>LLPROGRAMS</envar> are <acronym>UNIX</acronym> path
1351
list variables.
1352
1353
</para>
1354
1355
<para>
1356
There is also a configuration file, and
1357
entries in it may be used in lieu of environment variables.
1358
It is ordinarily named .linesrc under <acronym>UNIX</acronym>,
1359
and lines.cfg under <acronym>MS-Windows</acronym>.
1360
A sample configuration file should have been included
1361
in the distribution.
1362
</para>
1363
1364
<para>
1365
See the section on System and User properties
1366
for more details.
1367
</para>
1368
1369
<para>
1370
1371
<envar>LLDATABASES</envar> can be set to a list of directories
1372
that hold <application>LifeLines</application> databases. When
1373
you execute the <application>LifeLines</application> program,
1374
these directories will be searched in turn for the database
1375
mentioned on the command line. For example,
1376
<userinput><envar>LLDATABASES</envar>=<replaceable>.:/home/ttw4/LifeLines/Databases</replaceable></userinput>
1377
indicates that databases should be searched for in the current
1378
directory first, and if not found there, then searched for in:
1379
<filename>/home/ttw4/LifeLines/Databases</filename>
1380
1381
</para>
1382
1383
1384
1385
<para>
1386
1387
Each <application>LifeLines</application> database is
1388
implemented as a directory with specific contents. The
1389
<envar>LLDATABASES</envar> variable should be set to a list of
1390
directories that contain these database directories, not to a
1391
list of database directories themselves.
1392
1393
</para>
1394
1395
1396
1397
<para>
1398
1399
The environment variable <envar>LLPROGRAMS</envar> is used in
1400
the same way, but to specify the search path for
1401
<application>LifeLines</application> report generating and
1402
other programs (described later).
1403
1404
</para>
1405
1406
1407
1408
<para>
1409
1410
<envar>LLARCHIVES</envar> and <envar>LLREPORTS</envar> can
1411
each be set to specify a single
1412
directory. <envar>LLARCHIVES</envar> is used to select a
1413
directory where all database backup files will be stored, and
1414
<envar>LLREPORTS</envar> is used to select a directory where
1415
all generated reports and program outputs will be placed.
1416
1417
</para>
1418
1419
<para>
1420
1421
New databases without explicit paths will be created in the
1422
first directory listed in the LLDATABASES path. (This is a
1423
change; versions from 3.0.6 to 3.0.31 used a now obsolete
1424
variable LLNEWDBDIR).
1425
1426
</para>
1427
1428
<para>
1429
1430
You are not required to use these environment variables; when
1431
a variable is not defined,
1432
<application>LifeLines</application> uses the current
1433
directory as its default value. If you do use the variables,
1434
you can override their use by specifying files and directories
1435
as either absolute or relative paths.
1436
1437
</para>
1438
1439
<para>
1440
1441
You may use the configuration file in
1442
lieu of environment variables. This is especially oriented towards
1443
users on <acronym>MS-Windows</acronym> systems, on which
1444
environment variables are not as common a configuration technique.
1445
1446
</para>
1447
1448
1449
<para>
1450
1451
<application>LifeLines</application> uses the curses library
1452
for terminal independent I/O. This requires you to specify
1453
your terminal type with the <envar>TERM</envar> environment
1454
variable. (This is not relevant in the <acronym>MS-Windows</acronym>
1455
version.)
1456
1457
</para>
1458
1459
1460
1461
</sect1>
1462
1463
1464
1465
<sect1>
1466
1467
1468
1469
<title>
1470
1471
BASICS OF BROWSING
1472
1473
</title>
1474
1475
1476
1477
<para>
1478
1479
You will use the browsing screens of
1480
<application>LifeLines</application> most of the time. When in
1481
these modes you can quickly search for or browse through the
1482
persons and families in the database. When you find a person
1483
or family you are interested in, you can then edit their
1484
records.
1485
1486
</para>
1487
1488
1489
1490
<para>
1491
The browsing screens also allow you to add new persons and
1492
families to the database, add spouses to families, add
1493
children to families, swap the order of spouses and children,
1494
merge persons and merge families, and perform other
1495
operations. The browsing screens also lets you remove spouses
1496
from families and remove children from families.
1497
</para>
1498
1499
<para>
1500
There are six browsing screens. The person and family screens
1501
concentrate on a single person and family, respectively. The
1502
list screen allows you to browse through a list of persons. The
1503
two person browse screen shows two persons at once, and the
1504
two family browse screen shows two families at once. The
1505
auxiliary screen is used browsing any other type of records
1506
(e.g., events, sources, notes).
1507
1508
</para>
1509
1510
<para>
1511
Each browsing screen has multiple
1512
view modes. The view mode affects how the information is displayed
1513
on the screen, but does not affect the menu choices available at
1514
the bottom of the screen. Menu commands are available on each screen
1515
to change amongst the view modes available for that screen.
1516
</para>
1517
1518
<para>
1519
The person screen has the most view modes. It has normal mode,
1520
which shows a summary of the vital records of the person. It (like
1521
all other screens) has GEDCOM mode, which shows the actual GEDCOM
1522
data of the record, and also expanded GEDCOM mode, which shows the
1523
actual GEDCOM data, but augments it with information on each line
1524
that contains a cross-reference (GEDCOM xref). It has two pedigree
1525
or tree modes, one showing an ancestral tree and one showing a
1526
descendant tree. The depth of the pedigree trees shown may be
1527
adjusted via menu commands.
1528
</para>
1529
1530
<para>
1531
The two person browse screen has the same modes as the person
1532
screen.
1533
</para>
1534
1535
<para>
1536
The two family browse screen and tandem family screen alike have
1537
normal mode (showing a summary of vitals), GEDCOM mode, and
1538
expanded GEDCOM mode.
1539
</para>
1540
1541
<para>
1542
The auxiliary screen has only GEDCOM mode and expanded GEDCOM mode.
1543
(The list screen has no view modes at present).
1544
</para>
1545
1546
</sect1>
1547
1548
1549
1550
<sect1>
1551
1552
1553
1554
<title>
1555
1556
IDENTIFYING A PERSON OR LIST OF PERSONS TO BROWSE
1557
1558
</title>
1559
1560
1561
1562
<para>
1563
1564
To enter the browsing modes from the main menu strike
1565
b. <application>LifeLines</application> asks you to identify a
1566
person or list of persons to browse to:
1567
1568
<screen>
1569
Please identify person or persons to browse to.
1570
Enter name, key, refn or list:
1571
</screen>
1572
1573
</para>
1574
1575
<para>
1576
1577
Enter either a name or partial name, or an internal key value,
1578
or a user-defined reference key (described later) or the name
1579
of a previously defined list of persons (described later), and
1580
strike return.
1581
1582
</para>
1583
1584
1585
1586
<para>
1587
1588
<application>LifeLines</application> allows wide flexibility
1589
in how to enter names. You may enter a name in upper or lower
1590
case or any combination. You may leave out all but the first
1591
given name, and, for given names, you may leave out any
1592
letters except the first. You may leave vowels out of the
1593
surname, and after four or five consonants have been typed,
1594
you may leave them out too. You must separate the given names
1595
from the surname by a slash, and if you enter given names
1596
after the surname (as in Chinese names), or any modifiers
1597
(such as Jr, Sr, IV, etc.), they must be separated from the
1598
surname by another slash. Here are a few of the ways I can
1599
enter my name:
1600
1601
<example>
1602
1603
<title>
1604
Example of entering a name
1605
</title>
1606
1607
<literallayout>
1608
Thomas Trask /Wetmore/ IV
1609
thomas/wetmore/iv
1610
t t/wetmr/i
1611
th tr/Wetmore
1612
t/wtmr/iv
1613
</literallayout>
1614
</example>
1615
1616
</para>
1617
1618
1619
1620
<para>
1621
1622
You may browse to the list of all persons with the same
1623
surname by using the * character as the first initial. For
1624
example:
1625
1626
<example>
1627
1628
<title>
1629
Example of using wildcard in browsing
1630
</title>
1631
1632
<literallayout>*/wetmore</literallayout></example>matches all
1633
persons with surname Wetmore. This is the only wildcard
1634
feature supported in browsing. (However, the search operation
1635
provides some simple wildcards for
1636
finding individual name fragments, or searching by user-defined
1637
reference keys. The search operation is accessed via a different
1638
choice off of the main menu.)
1639
1640
</para>
1641
1642
1643
1644
<para>
1645
1646
After you enter a name, <application>LifeLines</application>
1647
searches for all persons who match. There are three
1648
possibilities: no one matches; one person matches; or more
1649
than one person matches. In the first case
1650
<application>LifeLines</application> writes: <screen>There is no
1651
one in the database with that name or key.</screen> and leaves
1652
you in the main menu.
1653
1654
</para>
1655
1656
1657
1658
<para>
1659
1660
If one person matches, <application>LifeLines</application>
1661
enters the person browse mode displaying the matched
1662
person. If more than one person matches,
1663
<application>LifeLines</application> enters the list browsing
1664
mode with the list of matching persons.
1665
1666
</para>
1667
1668
1669
1670
<para>
1671
1672
You may also identify a person by entering his or her
1673
internal, cross-reference key value. The internal key values
1674
of all person records are an I followed by digits. In the
1675
current version, when you enter a key value you must omit the
1676
I. If <application>LifeLines</application> finds a person with
1677
the key value you provide,
1678
<application>LifeLines</application> enters the person
1679
browsing mode displaying that person.
1680
1681
</para>
1682
1683
1684
1685
<para>
1686
1687
The browse command b is also available from most browsing
1688
modes. The command works the same way from those modes as it
1689
does from the main menu.
1690
1691
</para>
1692
1693
1694
1695
</sect1>
1696
1697
1698
1699
<sect1>
1700
1701
1702
1703
<title>
1704
1705
ZIP IDENTIFYING A NEW PERSON
1706
1707
</title>
1708
1709
1710
1711
<para>
1712
1713
Some <application>LifeLines</application> operations need you
1714
to identify a person, not for the purpose of browsing, but for
1715
the purpose of completing an operation you have requested. For
1716
example, when you add a child to a family,
1717
<application>LifeLines</application> may ask you to identify
1718
the child. When this happens a panel pops up that asks you to
1719
identify a person. You respond by typing a name or key exactly
1720
as you would for the b command. If no one matches,
1721
<application>LifeLines</application> returns to the previous
1722
browsing mode. If the name matches persons in the database
1723
<application>LifeLines</application> displays something like:
1724
1725
<screen>
1726
Please choose from among these records.
1727
>Thomas Trask Wetmore, b. 1826, N.B. (42)
1728
Thomas Trask Wetmore IV, b. 1949, Conn. (1)
1729
Thomas Trask Wetmore III, b. 1925, Conn. (6)
1730
Thomas Trask Wetmore Jr, b. 1896, Conn. (11)
1731
Thomas Trask Wetmore Sr, b. 1866, N.S. (23)
1732
Thomas Trask Wetmore V, b. 1982, Mass. (5)
1733
_______________________________________________
1734
Commands: j Move down k Move up i Select q Quit
1735
</screen>
1736
1737
1738
</para>
1739
1740
1741
1742
<para>
1743
1744
Use the j and k commands to move the selection cursor (>) to
1745
the correct person, and then use the i command to select that
1746
person. There may be more persons in the list than you can see
1747
at once. If this is so then you can use the j and k commands
1748
to scroll through the full list. If you don't find the proper
1749
person, use the q command and
1750
<application>LifeLines</application> asks whether you want to
1751
enter another name.
1752
1753
</para>
1754
1755
<para>
1756
1757
With version 3.0.15, lists may also be navigated with the up
1758
and down arrows, PageUp and PageDown keys, Home and End keys, and
1759
the Enter key. Shift-PageUp and Shift-PageDown move more than one
1760
page at a time in a given direction. The keyboard equivalents are
1761
j=UpArrow, k=DownArrow, u=PageUp, d=PageDown, ^=Home, $=End,
1762
U=Shift-PageUp, D=Shift-PageDown, i=Enter.
1763
1764
</para>
1765
1766
1767
<para>
1768
1769
When <application>LifeLines</application> creates a list of
1770
names for you to select from, it tries to add extra
1771
information to the name; this helps determine which name to
1772
choose, and is important in databases where many persons have
1773
the same name. <application>LifeLines</application> also
1774
places the person's key value at the end of each menu line;
1775
this may be helpful in large databases.
1776
1777
</para>
1778
1779
1780
1781
<para>
1782
1783
Some browse screens provide the z command, which allows you to
1784
browse to a new person using the zip style of identification
1785
rather than the b style.
1786
1787
</para>
1788
1789
1790
1791
</sect1>
1792
1793
1794
1795
<sect1>
1796
1797
1798
1799
<title>
1800
1801
BROWSE DISPLAY BASICS
1802
1803
</title>
1804
1805
1806
1807
<para>
1808
1809
The screen display for each browsing screen is made up of
1810
panels. At the bottom of each display is a message panel used
1811
for one line messages. Each display contains one or two data
1812
panels showing information from the database. And each display
1813
has a panel with the operation menu available for that screen.
1814
1815
</para>
1816
1817
1818
1819
</sect1>
1820
1821
1822
1823
<sect1>
1824
1825
1826
1827
<title>
1828
1829
PERSON BROWSE SCREEN
1830
1831
</title>
1832
1833
1834
1835
<para>
1836
1837
After you identify a person to browse to,
1838
<application>LifeLines</application> enters the person browse
1839
screen. The top panel in the display gives basic information
1840
about the person (in the normal, or vitals, mode, which is the
1841
default). The middle panel provides a menu of commands.
1842
For example:
1843
1844
<screen>
1845
person: Thomas Trask WETMORE Sr (25)
1846
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
1847
died: 17 February 1947, New London, New London, Connecticut
1848
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
1849
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
1850
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
1851
child: Portia Louise WETMORE, b. 1892, Conn., d. 1921, Conn. (27)
1852
child: Thomas Trask WETMORE, b. 1896, Conn., d. 1970, Conn. (17)
1853
spouse: Arleen M KEENEY, m. 1914, Conn. (75)
1854
_______________________________________________________________________
1855
Please choose an operation: (pg 1/3)
1856
e Edit the person g Browse to family p Pedigree mode
1857
f Browse to father u Browse to parents n Create new person
1858
m Browse to mother b Browse to persons a Create new family
1859
s Browse to spouse/s h Add as spouse x Swap two families
1860
c Browse to children i Add as child tt Enter tandem mode
1861
o Browse to older sib r Remove as spouse ? Other menu choices
1862
y Browse to younger sib d Remove as child q Return to main menu
1863
_______________________________________________________________________
1864
LifeLines -- Person Browse Screen
1865
</screen>
1866
1867
1868
</para>
1869
1870
1871
1872
<para>
1873
1874
The commands perform a wide variety of functions.
1875
1876
</para>
1877
1878
1879
1880
<para>
1881
1882
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit the person. </action></glossterm><glossdef>
1883
1884
<para>
1885
1886
Edit the person's database
1887
record. <application>LifeLines</application> puts the record
1888
in a file, and then runs a screen editor so you can edit the
1889
record. When you return from the editor,
1890
<application>LifeLines</application> asks you to confirm any
1891
changes; the person is changed only if you answer yes.
1892
1893
</para>
1894
1895
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
1896
1897
<para>
1898
1899
Browse to the person's father. If the father isn't in the
1900
database, <application>LifeLines</application> doesn't change
1901
the display. If there are more than one father,
1902
<application>LifeLines</application> asks you to select one.
1903
1904
</para>
1905
1906
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mother.</action></glossterm><glossdef>
1907
1908
<para>
1909
1910
Browse to the person's mother. If the mother isn't in the
1911
database, <application>LifeLines</application> doesn't change
1912
the display. If there are more than one mother,
1913
<application>LifeLines</application> asks you to select one.
1914
1915
</para>
1916
1917
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse to spouse/s.</action></glossterm><glossdef>
1918
1919
<para>
1920
1921
Browse to the person's spouse. If the person has more than one
1922
spouse, <application>LifeLines</application> asks you to
1923
select one. If the person has no spouse, the display does not
1924
change.
1925
1926
</para>
1927
1928
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
1929
1930
<para>
1931
1932
Browse to one of the person's children. If there is more than
1933
one child, <application>LifeLines</application> asks you to
1934
select one. If the person has no children, the display does
1935
not change.
1936
1937
</para>
1938
1939
</glossdef></glossentry><glossentry><glossterm><keycap>o</keycap> <action>Browse to older sib.</action></glossterm><glossdef>
1940
1941
<para>
1942
1943
Browse to the person's next older sibling. If the person has
1944
no such sibling, the display does not change. Only siblings
1945
from the same family are browsed by this command.
1946
1947
</para>
1948
1949
</glossdef></glossentry><glossentry><glossterm><keycap>y</keycap> <action>Browse to younger sib.</action></glossterm><glossdef>
1950
1951
<para>
1952
1953
Browse to the person's next younger sibling. If the person has
1954
no such sibling, the display does not change. Only siblings
1955
from the same family are browsed by this command.
1956
1957
</para>
1958
1959
</glossdef></glossentry><glossentry><glossterm><keycap>g</keycap> <action>Browse to family.</action></glossterm><glossdef>
1960
1961
<para>
1962
1963
Browse to the family the person is a spouse or parent in, and
1964
switch to the family browse mode. If the person is in more
1965
than one family, <application>LifeLines</application> asks you
1966
to identify which one. If the person is not a spouse or parent
1967
in any family, the display does not change.
1968
1969
</para>
1970
1971
</glossdef></glossentry><glossentry><glossterm><keycap>u</keycap> <action>Browse to parents.</action></glossterm><glossdef>
1972
1973
<para>
1974
1975
Browse to the family the person is a child in, and switch to
1976
the family browse mode. If the person is not a child in a
1977
family, the display does not change. If the person is a child
1978
in more than one family, <application>LifeLines</application>
1979
asks you to identify which one.
1980
1981
</para>
1982
1983
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
1984
1985
<para>
1986
1987
Browse to a new person or list of
1988
persons. <application>LifeLines</application> asks you to
1989
identify a person or persons by name, key or list name, and
1990
depending on how many persons are identified, switches either
1991
to the list browse mode, or remains in the person browse mode.
1992
1993
</para>
1994
1995
</glossdef></glossentry><glossentry><glossterm><keycap>h</keycap> <action>Add as spouse.</action></glossterm><glossdef>
1996
1997
<para>
1998
1999
Add the person as a spouse/parent to an existing
2000
family. <application>LifeLines</application> asks you to
2001
identify the family, and then asks you to confirm the request.
2002
2003
</para>
2004
2005
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Add as child.</action></glossterm><glossdef>
2006
2007
<para>
2008
2009
Add the person as a child to an existing family. The person
2010
may already be a child in another
2011
family. <application>LifeLines</application> asks you to
2012
identify the family, and then asks you to confirm the request.
2013
2014
</para>
2015
2016
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove as spouse.</action></glossterm><glossdef>
2017
2018
<para>
2019
2020
Remove the person as a spouse or parent from an existing
2021
family. If the person is a spouse or parent in more than one
2022
family, <application>LifeLines</application> asks you to
2023
identify the family.
2024
2025
</para>
2026
2027
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Remove as child.</action></glossterm><glossdef>
2028
2029
<para>
2030
2031
Remove the person as a child in an existing family.
2032
2033
</para>
2034
2035
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Create new person.</action></glossterm><glossdef>
2036
2037
<para>
2038
2039
Create and add a new person to the
2040
database. <application>LifeLines</application> creates a
2041
record template and puts you into the screen editor to edit
2042
the record. When you return from the editor,
2043
<application>LifeLines</application> asks you to confirm the
2044
operation. If you do, the new person is added and becomes the
2045
current person. If not, the new person is not added, and
2046
<application>LifeLines</application> returns to the original
2047
display.
2048
2049
</para>
2050
2051
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Create new family.</action></glossterm><glossdef>
2052
2053
<para>
2054
2055
Create and add a new family to the database. The new family
2056
may have the current person as either a spouse/parent or as a
2057
child; <application>LifeLines</application> asks which. If you
2058
choose to create a family with the person as a spouse/parent,
2059
<application>LifeLines</application> asks you to identify the
2060
other spouse if he or she is known. In either case
2061
<application>LifeLines</application> creates a family
2062
template, and places you in the screen editor. When you
2063
return from the editor, <application>LifeLines</application>
2064
asks you to confirm the operation. If you do,
2065
<application>LifeLines</application> adds the family and
2066
shifts into family browse mode. If the command you ran just
2067
before the a command were the n command, and you choose to
2068
create a family with the person as a spouse/parent,
2069
<application>LifeLines</application> guesses that the other
2070
spouse in the family will be the person displayed just before
2071
the new person was
2072
created. <application>LifeLines</application> asks you if this
2073
is the case, and if so, automatically make that person the
2074
other spouse in the new family. If this is not the case,
2075
<application>LifeLines</application> asks you to identify the
2076
other spouse.
2077
2078
</para>
2079
2080
</glossdef></glossentry><glossentry><glossterm><keycap>p</keycap><action>Pedigree mode.</action></glossterm><glossdef>
2081
2082
<para>
2083
2084
Change to pedigree browse mode. The person becomes the root
2085
person in the pedigree display.
2086
2087
</para>
2088
2089
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap two families.</action></glossterm><glossdef>
2090
2091
<para>
2092
2093
Swap (change chronological order) any two families that the
2094
person belongs to as a spouse or
2095
parent. <application>LifeLines</application> asks you to
2096
identify the two families and then swaps them.
2097
2098
</para>
2099
2100
</glossdef></glossentry><glossentry><glossterm><keycap>tt</keycap> <action>Enter tandem mode.</action></glossterm><glossdef>
2101
2102
<para>
2103
2104
Change to the tandem person browse
2105
mode. <application>LifeLines</application> first asks you to
2106
identify the second person.
2107
2108
</para>
2109
2110
</glossdef></glossentry><glossentry><glossterm><keycap>?</keycap> <action>Other menu choices.</action></glossterm><glossdef>
2111
2112
<para>
2113
Go to the next page of menu choices. This will have no effect on the
2114
upper (data) portion of the screen, but it allows you to page through
2115
all available commands for this display screen.
2116
</para>
2117
2118
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2119
2120
<para>
2121
2122
Return to the <application>LifeLines</application> main menu.
2123
2124
</para>
2125
2126
</glossdef></glossentry><glossentry><glossterm><keycap>z</keycap> <action>Zip browse to person.</action></glossterm><glossdef>
2127
2128
<para>
2129
2130
Zip browse to a new person.
2131
<application>LifeLines</application> asks you to
2132
identify a person by name or key value, and if you do so,
2133
browses to that person.
2134
2135
</para>
2136
2137
2138
</glossdef></glossentry></glosslist>
2139
2140
</para>
2141
2142
2143
2144
</sect1>
2145
2146
<sect1>
2147
2148
<title>
2149
2150
LIST BROWSE SCREEN
2151
2152
</title>
2153
2154
2155
2156
<para>
2157
2158
This browse screen handles lists of persons. The top panel shows
2159
information about one person in the list. The left panel
2160
shows a list of up to 12 persons. The person shown in the top
2161
panel is identified by the > character. The right panel is the
2162
menu of available commands.
2163
2164
<screen>
2165
person: Thomas Trask WETMORE Sr (25)
2166
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
2167
died: 17 February 1947, New London, New London, Connecticut
2168
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
2169
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
2170
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
2171
_______________________________________________________________________
2172
Thomas Trask WETMORE (42) Choose an operation:
2173
Thomas Trask WETMORE III (6) j Move down list
2174
Thomas Trask WETMORE IV (1) k Move up list
2175
Thomas Trask WETMORE (11) e Edit this person
2176
>Thomas Trask WETMORE Sr (23) i Browse this person
2177
Thomas Trask WETMORE (5) m Mark this person
2178
r Remove from list
2179
t Enter tandem mode
2180
n Name this list
2181
b Browse new persons
2182
a Add to this list
2183
x Swap mark/current
2184
q Return to main menu
2185
_______________________________________________________________________
2186
LifeLines -- List Browse Screen
2187
</screen>
2188
2189
2190
</para>
2191
2192
2193
2194
<para>
2195
2196
<glosslist><glossentry><glossterm><keycap>j</keycap> <action>Move down list.</action></glossterm><glossdef>
2197
2198
<para>
2199
2200
Move down the list one person. The list panel is only large
2201
enough to show 12 persons. However, the list may contain many
2202
more persons. Use the <keycap>j</keycap> and
2203
<keycap>k</keycap> commands to scroll to these other persons.
2204
2205
</para>
2206
2207
</glossdef></glossentry><glossentry><glossterm><keycap>k</keycap> <action>Move up list.</action></glossterm><glossdef>
2208
2209
<para>
2210
2211
Move up the list one person. The list panel is only large
2212
enough to show 12 persons. However, the list may contain many
2213
more persons. Use the <keycap>j</keycap> and
2214
<keycap>k</keycap> commands to scroll to these other persons.
2215
2216
</para>
2217
2218
<para>
2219
2220
With version 3.0.15, lists may also be navigated with the up
2221
and down arrows, PageUp and PageDown keys, Home and End keys, and
2222
the Enter key. Shift-PageUp and Shift-PageDown move more than one
2223
page at a time in a given direction. The keyboard equivalents are
2224
j=UpArrow, k=DownArrow, u=PageUp, d=PageDown, ^=Home, $=End,
2225
U=Shift-PageUp, D=Shift-PageDown, i=Enter.
2226
2227
</para>
2228
2229
</glossdef></glossentry><glossentry><glossterm><keycap>e</keycap> <action>Edit this person.</action></glossterm><glossdef>
2230
2231
<para>
2232
2233
Edit the displayed person's database
2234
record. <application>LifeLines</application> runs the editor
2235
on the person's record. When you return from the editor,
2236
<application>LifeLines</application> asks you to confirm any
2237
changes, and then leaves you in the list browse screen.
2238
2239
</para>
2240
2241
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Browse this person.</action></glossterm><glossdef>
2242
2243
<para>
2244
2245
Change to the person browse screen with the current person.
2246
2247
</para>
2248
2249
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Mark this person.</action></glossterm><glossdef>
2250
2251
<para>
2252
2253
Mark the current person if he/she is not marked; unmark the
2254
person is he/she is. The marked person is shown with an x by
2255
his/her name. Marked persons are used by the t and x
2256
commands. Only one person may be marked at a time.
2257
2258
</para>
2259
2260
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove from list.</action></glossterm><glossdef>
2261
2262
<para>
2263
2264
Remove the current person from the browse list (not from the database).
2265
2266
</para>
2267
2268
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Enter tandem mode.</action></glossterm><glossdef>
2269
2270
<para>
2271
2272
Change to the tandem person mode with the current person and
2273
the marked person as the two persons. If no person is marked there is no change.
2274
2275
</para>
2276
2277
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Name this list.</action></glossterm><glossdef>
2278
2279
<para>
2280
2281
Lists of persons may be named, allowing you to quickly browse
2282
back to them by giving a list name in response to the b
2283
command from different
2284
modes. <application>LifeLines</application> will prompt you
2285
for the name. List names are most convenient when short.
2286
2287
</para>
2288
2289
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse new persons.</action></glossterm><glossdef>
2290
2291
<para>
2292
2293
Browse to a new person or list of persons. You can identify a
2294
person or list of persons by name, internal or user key or by
2295
list name.
2296
2297
</para>
2298
2299
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add to this list.</action></glossterm><glossdef>
2300
2301
<para>
2302
2303
Add more persons to the current browse
2304
list. <application>LifeLines</application> asks you to
2305
identify a new person or list of persons by name, key or list
2306
name, and they are added to and name-sorted into the current
2307
list.
2308
2309
</para>
2310
2311
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap mark/current.</action></glossterm><glossdef>
2312
2313
<para>
2314
2315
Swap the current person with the marked person in the list.
2316
2317
</para>
2318
2319
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2320
2321
<para>
2322
2323
Return to the <application>LifeLines</application> main menu.
2324
2325
</para>
2326
2327
</glossdef></glossentry></glosslist>
2328
2329
</para>
2330
2331
2332
2333
</sect1>
2334
2335
2336
2337
<sect1>
2338
2339
2340
2341
<title>
2342
2343
FAMILY BROWSE SCREEN
2344
2345
</title>
2346
2347
2348
2349
<para>
2350
2351
This browse screen displays information about a family. The top
2352
panel shows basic information about the family. The bottom
2353
panel shows the menu of available commands.
2354
2355
<screen>
2356
father: Thomas Trask WETMORE IV (1)
2357
born: 18 December 1949, New London, New London, Connecticut
2358
died:
2359
mother: Luann Frances GRENDA (2)
2360
born: 10 July 1949, Pittsburgh, Allegheny, Pennsylvania
2361
died:
2362
married: 1 August 1970, Governors Island, New York, New York
2363
child: Anna Vivian Wetmore, b. 1974, Alaska (3)
2364
child: Marie Margaret WETMORE, b. 1979, Conn. (4)
2365
child: Thomas Trask WETMORE V, b. 1982, Mass. (5)
2366
_______________________________________________________________________
2367
Please choose an operation: (pg 1/4)
2368
e Edit the family %s Add source r Remove spouse from
2369
f Browse to father %e Add event d Remove child from
2370
m Browse to mother %o Add other x Swap two children
2371
c Browse to children s Add spouse to family ? Other menu choices
2372
n Create new person a Add child to family q Return to main menu
2373
_______________________________________________________________________
2374
LifeLines -- Family Browse Screen (* toggles menu)
2375
2376
</screen>
2377
</para>
2378
2379
2380
2381
<para>
2382
2383
<glosslist>
2384
<glossentry><glossterm><keycap>e</keycap> <action>Edit the family.</action></glossterm><glossdef>
2385
2386
<para>
2387
2388
Edit the family's record. <application>LifeLines</application>
2389
writes the record to a file and puts you into an editor to
2390
edit the file. When you return from the editor,
2391
<application>LifeLines</application> asks you to confirm the
2392
update; the family is changed only if you do so.
2393
2394
</para>
2395
2396
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
2397
2398
<para>
2399
2400
Browse to the father/husband of the family, switching to
2401
person browse screen. If the father is not there, there is no change.
2402
2403
</para>
2404
2405
</glossdef>
2406
</glossentry>
2407
2408
<glossentry><glossterm><keycap>m</keycap><action>Browse to mother.</action>
2409
</glossterm>
2410
2411
<glossdef>
2412
2413
<para>
2414
2415
Browse to the mother/wife of the family, switching to person
2416
browse screen. If the mother is not there, there is no change.
2417
2418
</para>
2419
2420
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
2421
2422
<para>
2423
2424
Browse to a child in the family, switching to the person
2425
browse screen. If the family has more than one child,
2426
<application>LifeLines</application> asks you to identify a
2427
specific child.
2428
2429
</para>
2430
2431
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Create new person.</action></glossterm><glossdef>
2432
2433
<para>
2434
2435
Create and add a new person to the
2436
database. <application>LifeLines</application> creates a
2437
record template and puts you into the screen editor to edit
2438
the record. When you return from the editor,
2439
<application>LifeLines</application> asks you to confirm the
2440
operation. If you do, the new person is added to the
2441
database. If not, the new person is not added. In both cases
2442
the display does not change.
2443
2444
</para>
2445
2446
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Add spouse to family.</action></glossterm><glossdef>
2447
2448
<para>
2449
2450
Add a spouse to the
2451
family. <application>LifeLines</application> asks you to
2452
identify the new spouse. If the command you ran just before
2453
the s command were the n command,
2454
<application>LifeLines</application> guesses that the new
2455
spouse will be the person just
2456
created. <application>LifeLines</application> asks if this is
2457
the case, and if so, makes that person the second spouse in
2458
the family. If not, <application>LifeLines</application> asks
2459
you to identify the other spouse.
2460
2461
</para>
2462
2463
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add child to family.</action></glossterm><glossdef>
2464
2465
<para>
2466
2467
Add a child to the
2468
family. <application>LifeLines</application> asks you to
2469
identify the new child. If the command you ran just before the
2470
a command were the n command,
2471
<application>LifeLines</application> guesses that the new
2472
child will be the person just
2473
created. <application>LifeLines</application> asks if this is
2474
the case, and if so, adds that child to the family. If not,
2475
<application>LifeLines</application> asks you to identify the
2476
child. If the family already has children,
2477
<application>LifeLines</application> also asks where to place
2478
the new child in the family.
2479
2480
</para>
2481
2482
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove spouse from.</action></glossterm><glossdef>
2483
2484
<para>
2485
2486
Remove a parent/spouse from the
2487
family. <application>LifeLines</application> asks you to
2488
identify the person, and if you do, removes him or her. The
2489
person is not removed from the database.
2490
2491
</para>
2492
2493
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Remove child from.</action></glossterm><glossdef>
2494
2495
<para>
2496
2497
Remove a child from the
2498
family. <application>LifeLines</application> asks you to
2499
identify the child should, and if you do, removes the child
2500
from the family. The person is not removed from the database.
2501
2502
</para>
2503
2504
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap two children.</action></glossterm><glossdef>
2505
2506
<para>
2507
2508
Swap (change the chronological order) of any two children in
2509
the family. <application>LifeLines</application> asks you to
2510
identify the two children and then swaps them.
2511
2512
</para>
2513
2514
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Enter family tandem.</action></glossterm><glossdef>
2515
2516
<para>
2517
2518
This command takes you to the tandem family browse
2519
screen. <application>LifeLines</application> asks you to
2520
identify a second family, and then takes you to the tandem
2521
family screen, displaying both the two families.
2522
2523
</para>
2524
2525
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
2526
2527
<para>
2528
2529
Browse to a new person or list of persons. You can identify a
2530
person or list by name, by key, or by list name. If you
2531
successfully identify a new person or persons you will switch
2532
into the person or list browse screens.
2533
2534
</para>
2535
2536
</glossdef></glossentry><glossentry><glossterm><keycap>z</keycap> <action>Browse to person.</action></glossterm><glossdef>
2537
2538
<para>
2539
2540
Zip browse to a new person.
2541
<application>LifeLines</application> asks you to identify a
2542
person by name or key value, and if you do, browses to that
2543
person.
2544
2545
</para>
2546
2547
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2548
2549
<para>
2550
2551
Return to the <application>LifeLines</application> main menu.
2552
2553
</para>
2554
2555
</glossdef></glossentry></glosslist>
2556
2557
</para>
2558
2559
2560
2561
</sect1>
2562
2563
2564
2565
<sect1>
2566
2567
2568
2569
<title>
2570
2571
TANDEM PERSON BROWSE MODE
2572
2573
</title>
2574
2575
2576
2577
<para>
2578
2579
The tandem person browse screen displays information about two
2580
persons. Its main use it to support the person merging
2581
operation. The top two panels show two persons in the format
2582
used in the person and list screen displays. The bottom panel
2583
gives the menu of available commands. For example:
2584
2585
2586
<screen>
2587
person: Thomas Trask WETMORE Sr (25)
2588
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
2589
died: 17 February 1947, New London, New London, Connecticut
2590
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
2591
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
2592
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
2593
______________________________________________________________________
2594
person: Thomas Trask WETMORE IV (1)
2595
born: 18 December 1949, New London, New London, Connecticut
2596
died:
2597
father: Thomas Trask WETMORE III, b. 1925, Conn. (6)
2598
mother: Joan Marie HANCOCK, b. 1928, Conn. (7)
2599
spouse: Luann Frances GRENDA, m. 1970, N.Y. (2)
2600
______________________________________________________________________
2601
Please choose an operation:
2602
e Edit top person s Browse top spouse/s a Add family
2603
t Browse to top c Browse top children j Merge bottom to top
2604
f Browse top father b Browse to persons x Switch top/bottom
2605
m Browse top mother d Copy top to bottom q Return to main menu
2606
______________________________________________________________________
2607
LifeLines - Two Person Browse Screen
2608
</screen>
2609
2610
2611
</para>
2612
2613
2614
2615
<para>
2616
2617
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit top person.</action></glossterm><glossdef>
2618
2619
<para>
2620
2621
Edit the top person's
2622
record. <application>LifeLines</application> writes the record
2623
to a file, and puts you in the screen editor to edit the
2624
file. When you return from the editor,
2625
<application>LifeLines</application> asks you to confirm the
2626
update; the person is changed only if you do so.
2627
2628
</para>
2629
2630
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Browse to top.</action></glossterm><glossdef>
2631
2632
<para>
2633
2634
Switch to the person display with the top person as current person.
2635
2636
</para>
2637
2638
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse top father.</action></glossterm><glossdef>
2639
2640
<para>
2641
2642
Replace the top person with his/her father.
2643
2644
</para>
2645
2646
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse top mother.</action></glossterm><glossdef>
2647
2648
<para>
2649
2650
Replace the top person with his/her mother.
2651
2652
</para>
2653
2654
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse top spouse/s.</action></glossterm><glossdef>
2655
2656
<para>
2657
2658
Replace the the top person with his/her spouse. If the person
2659
has more than one spouse, <application>LifeLines</application>
2660
asks you to identify one.
2661
2662
</para>
2663
2664
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse top children.</action></glossterm><glossdef>
2665
2666
<para>
2667
2668
Replace the top person with one of his/her children. If the person has more
2669
than one child, <application>LifeLines</application> asks you to identify the one.
2670
2671
</para>
2672
2673
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
2674
2675
<para>
2676
2677
Browse to a new person or list of persons. <application>LifeLines</application> asks you to identify a new
2678
person or persons by name, key or list name, and then does as described in the section on identifying a
2679
person.
2680
2681
</para>
2682
2683
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Copy top to bottom.</action></glossterm><glossdef>
2684
2685
<para>
2686
2687
Copy the top person into the bottom person. A new person is not created; the same
2688
person is displayed twice.
2689
2690
</para>
2691
2692
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add family.</action></glossterm><glossdef>
2693
2694
<para>
2695
2696
Create a new family record; <application>LifeLines</application> assumes the two displayed persons are to become
2697
the spouses/parents in the new family; they must be of opposite sex.
2698
2699
</para>
2700
2701
</glossdef></glossentry><glossentry><glossterm><keycap>j</keycap> <action>Merge bottom to top.</action></glossterm><glossdef>
2702
2703
<para>
2704
2705
Merge the bottom person into the top person. <application>LifeLines</application> combines the two person
2706
records and places you in the screen editor to edit the combined record. When you are done, if you
2707
confirm the operation, <application>LifeLines</application> removes the bottom person from the database, and the top person is
2708
given the combined record. See the section on merging.
2709
2710
</para>
2711
2712
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Switch top/bottom.</action></glossterm><glossdef>
2713
2714
<para>
2715
2716
Swap the two persons in the display.
2717
2718
</para>
2719
2720
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2721
2722
<para>
2723
2724
Return to the <application>LifeLines</application> main menu.
2725
2726
</para>
2727
2728
</glossdef></glossentry></glosslist>
2729
2730
</para>
2731
2732
2733
2734
</sect1>
2735
2736
2737
2738
<sect1>
2739
2740
2741
2742
<title>
2743
2744
TANDEM FAMILY BROWSE MODE
2745
2746
</title>
2747
2748
2749
2750
<para>
2751
2752
The tandem family browse screen displays information about two families. Its main use it to support the
2753
family merging operation.The top two panels provide information about the two families you are
2754
browsing, and the bottom panel holds the menu of available commands. For example:
2755
<screen>
2756
father: Thomas Trask WETMORE IV (1)
2757
born: 18 December 1949, New London, New London, Connecticut
2758
mother: Luann Frances GRENDA (2)
2759
born: 10 July 1949, Pittsburgh, Allegheny, Pennsylvania
2760
married: 1 August 1970, Governors Island, New York, New York
2761
child: Anna Vivian WETMORE, b. 1974, Alaska (3)
2762
__________________________________________________________________
2763
father: Thomas Trask WETMORE III (6)
2764
born: 26 October 1925, New London, New London, Connecticut
2765
wife: Joan Marie Hancock (7)
2766
born: 6 June 1928, New London, New London, Connecticut
2767
married: 5 February 1949, New London, New London, Connecticut
2768
child: Thomas Trask WETMORE IV, b. 1949, Conn. (1)
2769
__________________________________________________________________
2770
Please choose an operation: (pg 1/3)
2771
e Edit top person m Browse to mothers )b Scroll bottom down
2772
t Browse to top (t Scroll top up (( Scroll both up
2773
b Browse to bottom )t Scroll top down ? Other menu choices
2774
f Browse to fathers (b Scroll bottom up q Return to main menu
2775
__________________________________________________________________
2776
LifeLines -- Two Family Browse Screen (* toggles menu)
2777
</screen>
2778
2779
2780
</para>
2781
2782
2783
2784
<para>
2785
2786
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit top family.</action></glossterm><glossdef>
2787
2788
<para>
2789
2790
This command lets you edit the top family's record. <application>LifeLines</application> writes the record into
2791
a file, and then puts you into an editor to edit that information. When you return from the editor,
2792
<application>LifeLines</application> asks you whether you are sure you want to update the family in the database. The family
2793
is changed only if you answer yes.
2794
2795
</para>
2796
2797
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Browse to top.</action></glossterm><glossdef>
2798
2799
<para>
2800
2801
Change to the family browse screen with the top family the current family.
2802
2803
</para>
2804
2805
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to bottom.</action></glossterm><glossdef>
2806
2807
<para>
2808
2809
Change to the single family browse screen with the bottom family the current
2810
family.
2811
2812
</para>
2813
2814
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to fathers.</action></glossterm><glossdef>
2815
2816
<para>
2817
2818
Change to the tandem person screen with the fathers of the two
2819
families as the two persons.
2820
2821
</para>
2822
2823
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mothers.</action></glossterm><glossdef>
2824
2825
<para>
2826
2827
Change to the tandem person screen with the mothers of the two
2828
families as the two persons.
2829
2830
</para>
2831
2832
</glossdef></glossentry><glossentry><glossterm><keycap>(t</keycap> <action>Scroll top up.</action></glossterm><glossdef>
2833
2834
<para>
2835
2836
TODO
2837
2838
</para>
2839
2840
</glossdef></glossentry><glossentry><glossterm><keycap>)t</keycap> <action>Scroll top down.</action></glossterm><glossdef>
2841
2842
<para>
2843
2844
TODO
2845
2846
</para>
2847
2848
</glossdef></glossentry><glossentry><glossterm><keycap>(b</keycap> <action>Scroll bottom up.</action></glossterm><glossdef>
2849
2850
<para>
2851
2852
TODO
2853
2854
</para>
2855
2856
</glossdef></glossentry><glossentry><glossterm><keycap>)b</keycap> <action>Scroll bottom down.</action></glossterm><glossdef>
2857
2858
<para>
2859
2860
TODO
2861
2862
</para>
2863
2864
</glossdef></glossentry><glossentry><glossterm><keycap>((</keycap> <action>Scroll both up.</action></glossterm><glossdef>
2865
2866
<para>
2867
2868
TODO
2869
2870
</para>
2871
2872
</glossdef></glossentry><glossentry><glossterm><keycap>))</keycap> <action>Scroll both down.</action></glossterm><glossdef>
2873
2874
<para>
2875
2876
TODO
2877
2878
</para>
2879
2880
</glossdef></glossentry><glossentry><glossterm><keycap>#</keycap> <action>Toggle childnos.</action></glossterm><glossdef>
2881
2882
<para>
2883
2884
TODO
2885
2886
</para>
2887
2888
</glossdef></glossentry><glossentry><glossterm><keycap>(1-9)</keycap> <action>Browse to child.</action></glossterm><glossdef>
2889
2890
<para>
2891
2892
TODO
2893
2894
</para>
2895
2896
</glossdef></glossentry><glossentry><glossterm><keycap>j</keycap> <action>Merge bottom to top.</action></glossterm><glossdef>
2897
2898
<para>
2899
2900
Merge the bottom family into the top family. <application>LifeLines</application> combines the two
2901
family records and places you in the screen editor to edit the combined record. When you are done, if
2902
you confirm the operation, <application>LifeLines</application> deletes the bottom family from the database, and the top
2903
family is given the combined record. See the section on merging.
2904
2905
</para>
2906
2907
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Switch top/bottom.</action></glossterm><glossdef>
2908
2909
<para>
2910
2911
Swap the two families in the display.
2912
2913
</para>
2914
2915
<para>
2916
[There are some more miscellaneous commands available on the menus.]
2917
</para>
2918
2919
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2920
2921
<para>
2922
2923
Return to the <application>LifeLines</application> main menu.
2924
2925
</para>
2926
2927
</glossdef></glossentry></glosslist>
2928
2929
</para>
2930
2931
2932
2933
</sect1>
2934
2935
2936
2937
<sect1>
2938
2939
2940
2941
<title>
2942
2943
PEDIGREE BROWSE MODE
2944
2945
</title>
2946
2947
2948
2949
<para>
2950
2951
The pedigree browse screen displays a four-generation pedigree for the current person. The top panel
2952
holds the pedigree, and the bottom panel holds the menu of available commands. For example:
2953
<screen>
2954
John WETMORE [1755-1848] (32)
2955
Daniel Van Cott WETMORE [1791-1881] (41)
2956
Anna VAN COTT [1757-1802] (33)
2957
Daniel Lorenzo WETMORE [1821-1903] (48)
2958
Thomas TRASK [-1836] (81)
2959
Hannah TRASK [1797-1829] (46)
2960
Susannah PORTER [1754-] (82)
2961
Thomas Trask WETMORE Sr [1866-1947] (25)
2962
Samuel DOTY [1759-] (501)
2963
Samuel DOTY [1787-] (74)
2964
Hephzibah PORTER [1764-1853] (502)
2965
Mary Ann DOTY [1827-1897] (59)
2966
Nathan SAVERY [1748-1826] (510)
2967
Lydia SAVERY [1806-] (75)
2968
Deidamia SABEAN [1765-1845] (511)
2969
__________________________________________________________________
2970
Please choose an operation:
2971
e Edit the person m Browse to mother g Browse to family
2972
i Browse to person s Browse to spouse/s b Browse to persons
2973
f Browse to father c Browse to children q Return to main menu
2974
__________________________________________________________________
2975
LifeLines - Pedigree Browse Mode</screen>
2976
2977
</para>
2978
2979
2980
2981
<para>
2982
2983
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit the person.</action></glossterm><glossdef>
2984
2985
<para>
2986
2987
Edit the current person.
2988
2989
</para>
2990
2991
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Browse to person.</action></glossterm><glossdef>
2992
2993
<para>
2994
2995
Change to the person display mode with the current person.
2996
2997
</para>
2998
2999
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
3000
3001
<para>
3002
3003
Browse to the father of the current person, shifting the pedigree one
3004
generation back. If the father is not in the database, there is no change.
3005
3006
</para>
3007
3008
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mother.</action></glossterm><glossdef>
3009
3010
<para>
3011
3012
Browse to the mother of the current person, shifting the pedigree one
3013
generation back. If the mother is not in the database, there is no change.
3014
3015
</para>
3016
3017
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse to spouse/s.</action></glossterm><glossdef>
3018
3019
<para>
3020
3021
Browse to a spouse of the current person, shifting the display to the pedigree of
3022
that person. If the current person has more than one spouse, <application>LifeLines</application> asks you to identify the spouse;
3023
if the person has no spouse there is no change.
3024
3025
</para>
3026
3027
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
3028
3029
<para>
3030
3031
Browse to a child of the current person, shifting the pedigree one generation
3032
forward. If the current person has more than one child, <application>LifeLines</application> asks you to identify the child; if
3033
the person has no children there is no change.
3034
3035
</para>
3036
3037
</glossdef></glossentry><glossentry><glossterm><keycap>g</keycap> <action>Browse to family.</action></glossterm><glossdef>
3038
3039
<para>
3040
3041
Change to the family display; the family will be the one that the current person
3042
belongs to as spouse or parent. If there are more than one, <application>LifeLines</application> asks you to identify the proper
3043
one.
3044
3045
</para>
3046
3047
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
3048
3049
<para>
3050
3051
Browse to another person or list of persons; if you identify a single person the
3052
display remains in the pedigree display; if you identify more than one person the display changes to
3053
the list browse mode.
3054
3055
</para>
3056
3057
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
3058
3059
<para>
3060
3061
Leave the pedigree browsing mode and return to the main menu.
3062
3063
</para>
3064
3065
</glossdef></glossentry></glosslist>
3066
3067
</para>
3068
3069
3070
3071
</sect1>
3072
3073
3074
3075
<sect1>
3076
3077
3078
3079
<title>
3080
3081
ADD OPERATION
3082
3083
</title>
3084
3085
3086
3087
<para>
3088
3089
If you choose the add operation from the main menu, <application>LifeLines</application> displays the add menu:
3090
<screen>
3091
What do you want to add?
3092
p Person - add new person to the database
3093
f Family - create family record from one or two spouses
3094
c Child - add a child to an existing family
3095
s Spouse - add a spouse to an existing family
3096
q Quit - return to the previous menu
3097
</screen>
3098
3099
3100
</para>
3101
3102
3103
3104
<para>
3105
3106
These operations work in a straightforward way. <application>LifeLines</application> asks you the necessary questions, and lets
3107
you cancel at any time. The operations provided by this menu are also available from the browsing
3108
modes, and are often easier to perform there.
3109
3110
</para>
3111
3112
3113
3114
3115
</sect1>
3116
3117
3118
3119
<sect1>
3120
3121
3122
3123
<title>
3124
3125
DELETE OPERATION
3126
3127
</title>
3128
3129
3130
3131
<para>
3132
3133
If you choose the delete operation at the main menu, <application>LifeLines</application> displays the delete menu:
3134
<screen>
3135
What do you want to delete?
3136
c Child - remove a child from his/her family
3137
s Spouse - remove a spouse from a family
3138
p Person - remove a person completely
3139
q Quit - return to the previous menu
3140
</screen>
3141
3142
3143
</para>
3144
3145
3146
3147
<para>
3148
3149
These operations also work in a straightforward way. <application>LifeLines</application> asks you the necessary questions and
3150
lets you cancel at any time.
3151
3152
3153
</para>
3154
3155
3156
3157
<para>
3158
3159
You may also remove a child from his/her family, or remove a spouse/parent from his/her family,
3160
from the person browsing mode. In both cases, only a relationship is removed, not a person. On the other
3161
hand, the delete menu must be used if you want to completely remove a person from the database; this
3162
cannot be done from the browsing mode.
3163
3164
3165
</para>
3166
3167
3168
3169
<para>
3170
3171
There is no special operation for removing a family record. <application>LifeLines</application> silently removes any family
3172
record that has no parent or child associated with it.
3173
3174
</para>
3175
3176
3177
3178
</sect1>
3179
3180
3181
3182
<sect1>
3183
3184
3185
3186
<title>
3187
3188
CODESET CONVERSION
3189
3190
</title>
3191
3192
3193
3194
<para>
3195
3196
(This section was previously entitled CHARACTER TRANSLATION.)
3197
3198
</para>
3199
3200
<para>
3201
3202
The intention is that you need only specify the internal codeset for
3203
each database you create (and this step may be automated via the NewDbProps
3204
property), and all else works pretty well without tuning. That is,
3205
lifelines tries to guess the correct codeset for your environment (including
3206
guessing the console and windows codesets when operating under MS-Windows,
3207
which it should do fairly well).
3208
3209
</para>
3210
3211
<para>
3212
3213
However, you may encounter situations where you wish to alter the codeset
3214
behavior, or the codeset conversion is not operating correctly (in which case
3215
we hope you will report the problem to the mailing list and/or sourceforge
3216
bugs list).
3217
3218
</para>
3219
3220
<para>
3221
3222
There are two ways to amend codeset conversion. The first method is by changing
3223
configuration variables. For example, if you wish to generate an HTML report
3224
of all your data, which includes names in Russian (in Cyrillic letters), for your
3225
cousin, and you know that your cousin's computer has no font for Cyrillic letters,
3226
you might wish to temporarily adjust your report output codeset so that you will
3227
get interpolated ASCII letters for the Russian letters. You could do this by
3228
temporarily altering the configuration variable ReportCodeSetOut to be "ASCII"
3229
(actually, if any of your data has characters in it that are reserved in HTML,
3230
such as the less than sign, or the ampersand, you would probaby want "ASCII//HTML").
3231
3232
</para>
3233
3234
<para>
3235
3236
The second way to change codeset conversion, and the only way in lifelines 3.0.6,
3237
is to edit the embedded character translation tables, in which you actually specify
3238
the letters you want converted, letter by letter, and how you want them converted.
3239
This method, unlike the first, even works in databases with no specified internal
3240
codeset.
3241
</para>
3242
3243
<para>
3244
3245
If you choose the modify character translation tables operation from the main menu, <application>LifeLines</application> displays
3246
the character translation menu:
3247
<screen>
3248
Which character mapping do you want to edit?
3249
e Editor to Internal mapping
3250
m Internal to Editor mapping
3251
i GEDCOM to Internal mapping
3252
x Internal to GEDCOM mapping
3253
d Internal to Display mapping
3254
r Internal to Report mapping
3255
q Return to main menu
3256
</screen>
3257
3258
3259
</para>
3260
3261
3262
3263
<para>
3264
3265
<application>LifeLines</application> has little built-in knowledge of
3266
character codes. If you use 7-bit <acronym>ASCII</acronym> characters you
3267
will not encounter problems. However, many European and other languages
3268
require additional characters, and
3269
there are many 8-bit and other schemes for encoding those characters.
3270
<application>LifeLines</application> knows about none of
3271
them. However, <application>LifeLines</application> provides a number of
3272
character translation features you can use to manage
3273
character translation.
3274
3275
</para>
3276
3277
3278
3279
<para>
3280
3281
<application>LifeLines</application> provides facilities for mapping between characters whenever a data record changes form.
3282
<application>LifeLines</application> supports four forms:
3283
</para>
3284
<glosslist>
3285
<glossentry><glossterm>internal</glossterm><glossdef>
3286
3287
<para>
3288
3289
for records in the database
3290
3291
</para>
3292
</glossdef></glossentry>
3293
3294
<glossentry><glossterm>editor</glossterm><glossdef>
3295
3296
<para>
3297
for records being edited
3298
</para>
3299
</glossdef></glossentry>
3300
3301
<glossentry><glossterm>display</glossterm><glossdef>
3302
3303
<para>
3304
for records being displayed
3305
</para>
3306
</glossdef></glossentry>
3307
3308
<glossentry><glossterm>report</glossterm><glossdef>
3309
3310
<para>
3311
for records written to output file
3312
</para>
3313
</glossdef></glossentry>
3314
</glosslist>
3315
3316
3317
<para>
3318
3319
When converting text from one form to another <application>LifeLines</application> normally does not convert characters codes.
3320
You may, however, override this default behavior by creating translation tables that <application>LifeLines</application> will
3321
use when converting between forms. There are six translation tables you may define. The following
3322
table shows the six tables and describes when they are applied:
3323
</para>
3324
3325
<glosslist>
3326
<glossentry><glossterm>internal to editor</glossterm><glossdef>
3327
3328
<para>
3329
when converting from internal, database form to editor form
3330
</para>
3331
</glossdef></glossentry>
3332
3333
<glossentry><glossterm>editor to internal</glossterm><glossdef>
3334
3335
<para>
3336
when converting from editor form back to internal, database form
3337
</para>
3338
</glossdef></glossentry>
3339
3340
<glossentry><glossterm><acronym>GEDCOM</acronym> to internal</glossterm><glossdef>
3341
3342
<para>
3343
when reading <acronym>GEDCOM</acronym> input records and writing them to
3344
database
3345
</para>
3346
</glossdef></glossentry>
3347
3348
<glossentry><glossterm>internal to <acronym>GEDCOM</acronym></glossterm><glossdef>
3349
3350
<para>
3351
when writing internal database records to external <acronym>GEDCOM</acronym> file
3352
</para>
3353
3354
</glossdef></glossentry>
3355
<glossentry><glossterm>internal to display</glossterm><glossdef>
3356
3357
<para>
3358
when displaying a record in a browsing mode display screen
3359
</para>
3360
</glossdef></glossentry>
3361
3362
<glossentry><glossterm>internal to report</glossterm><glossdef>
3363
3364
<para>
3365
when writing internal database records to external report file
3366
</para>
3367
</glossdef></glossentry>
3368
</glosslist>
3369
3370
<para>
3371
3372
After you select a translation table you are placed in the editor to edit the table. Translation tables are
3373
made up of lines that look like:
3374
<synopsis><replaceable>pattern</replaceable> <replaceable>pattern</replaceable></synopsis>
3375
where a tab separates the patterns. Each pattern is an arbitrary sequence of verbatim <acronym>ASCII</acronym> characters
3376
and escape sequences. Translation occurs by finding all occurrences that match left patterns and
3377
replacing them with the corresponding right patterns.
3378
3379
</para>
3380
3381
3382
3383
<para>
3384
There are five escape mechanisms used in patterns:
3385
</para>
3386
3387
<glosslist>
3388
<glossentry><glossterm>#nnn</glossterm><glossdef>
3389
3390
<para>
3391
nnn is a decimal character value
3392
</para>
3393
</glossdef></glossentry>
3394
3395
<glossentry><glossterm>$hh</glossterm><glossdef>
3396
3397
<para>
3398
hh is a hexadecimal character value
3399
</para>
3400
</glossdef></glossentry>
3401
3402
<glossentry><glossterm>\ #</glossterm><glossdef>
3403
<!-- note above has extra space between \ and # - without this
3404
conversion to pdf gets confused openjade does some tex processing...
3405
-->
3406
3407
<para>
3408
represents the # character
3409
</para>
3410
</glossdef></glossentry>
3411
3412
<glossentry><glossterm>\$</glossterm><glossdef>
3413
3414
<para>
3415
represents the $ character
3416
</para>
3417
</glossdef></glossentry>
3418
3419
<glossentry><glossterm>\\</glossterm><glossdef>
3420
<para>
3421
represents the \ character
3422
</para>
3423
</glossdef></glossentry>
3424
</glosslist>
3425
3426
<para>
3427
3428
The character translation feature is not fully tested, and not all translations are currently
3429
implemented.
3430
3431
</para>
3432
3433
3434
3435
</sect1>
3436
3437
3438
3439
<sect1>
3440
3441
<title>
3442
3443
MISCELLANEOUS UTILITIES
3444
3445
</title>
3446
3447
3448
3449
<para>
3450
3451
If you choose the miscellaneous utilities operation,
3452
<application>LifeLines</application> displays the utilities menu:
3453
<screen>
3454
What utility do you want to perform?
3455
s Save the database in a GEDCOM file
3456
r Read in data from a GEDCOM file
3457
k Find a person's key value
3458
i Identify a person from key value
3459
d Show database statistics
3460
m Show memory statistics
3461
e Edit the place abbreviation file
3462
o Edit the user options file
3463
q Return to the main menu
3464
</screen>
3465
3466
3467
</para>
3468
3469
3470
<glosslist>
3471
<glossentry><glossterm><keycap>s</keycap> <action>Save the database in a GEDCOM file.</action></glossterm><glossdef>
3472
<para>
3473
3474
This command saves the complete <application>LifeLines</application> database in a
3475
<acronym>GEDCOM</acronym> file. All person, family, event, source and user-defined records are stored. This command
3476
may be used to periodically back up your database. When you use this command, <application>LifeLines</application> asks you
3477
for the name of the file. If you have defined the <envar>LLARCHIVE</envar> shell variable, <application>LifeLines</application> will store
3478
the file in the directory named in the variable.
3479
3480
</para>
3481
3482
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Read in data from a GEDCOM file.</action></glossterm><glossdef>
3483
3484
<para>
3485
3486
This command allows you restore a complete database from a
3487
<acronym>GEDCOM</acronym> file. When you select this command, <application>LifeLines</application> asks you for the name of the <acronym>GEDCOM</acronym> file.
3488
This command can also be used to import data from a <acronym>GEDCOM</acronym> file to an existing database. When
3489
<application>LifeLines</application> performs this command, it first reads the entire <acronym>GEDCOM</acronym> file and checks it for validity.
3490
If there are problems in the file, <application>LifeLines</application> describes them, writing them to the file err.log, and does
3491
not add any records to the database. If there are no problems, <application>LifeLines</application> adds all the records found in
3492
the file to the database (only header and trailer records are not stored in the database).
3493
3494
</para>
3495
</glossdef></glossentry>
3496
3497
<glossentry><glossterm><keycap>k</keycap> <action>Find a person's key value.</action></glossterm><glossdef>
3498
3499
<para>
3500
3501
This command finds the internal key value of a person.
3502
3503
</para>
3504
3505
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Identify a person from key value.</action></glossterm><glossdef>
3506
3507
<para>
3508
3509
This command identifies the person that has a particular internal
3510
key value.
3511
3512
</para>
3513
</glossdef></glossentry>
3514
3515
<glossentry><glossterm><keycap>d</keycap> <action>Show database statistics.</action></glossterm><glossdef>
3516
3517
<para>
3518
3519
This command summarizes the contents of the current database. It
3520
displays the number of person, family, source, event and other records in the database.
3521
3522
</para>
3523
</glossdef></glossentry>
3524
3525
<glossentry><glossterm><keycap>m</keycap> <action>Show memory statistics.</action></glossterm><glossdef>
3526
3527
<para>
3528
3529
This command is used by the author for debugging.
3530
3531
</para>
3532
</glossdef></glossentry>
3533
3534
<glossentry><glossterm><keycap>e</keycap> <action>Edit the place abbreviation file.</action></glossterm><glossdef>
3535
3536
<para>
3537
3538
This command allows you to edit the place abbreviations
3539
file. This file defines the abbreviations that are used by
3540
<application>LifeLines</application> when it creates lists of
3541
persons for you to select from. Each line in the file has the
3542
format:<synopsis><replaceable>word</replaceable>:<replaceable>
3543
abbr </replaceable></synopsis>where word is a word to be
3544
abbreviated, and abbr is its abbreviation. The word and its
3545
abbreviation are separated by a colon. For example:
3546
3547
<example>
3548
3549
<title>
3550
Example of using abbreviations
3551
</title>
3552
3553
<literallayout>Connecticut:Conn.
3554
Massachusetts:Mass.
3555
Nova Scotia:N.S.</literallayout></example>
3556
3557
</para>
3558
3559
3560
3561
<para>
3562
3563
When <application>LifeLines</application> constructs lists of persons for you to select from, it looks up the last component of
3564
certain <structfield>PLAC</structfield> lines in this file, and if it finds that component, replaces it with its abbreviation.
3565
3566
</para>
3567
</glossdef></glossentry>
3568
3569
<glossentry><glossterm><keycap>o</keycap>
3570
<action>Edit the user options file.</action>
3571
</glossterm><glossdef>
3572
3573
<para>
3574
3575
This command allows you to edit the user options file. The user options file
3576
is a record kept in the database that holds user selectable options. Each
3577
option has a name and a string value. Each line in the options file has the
3578
format:<synopsis><replaceable>option</replaceable>=<replaceable>value</replaceable></synopsis>
3579
where option is the name of an option and value is the option's string value.
3580
If the value is more than one line long, then the last character in each
3581
non-final line must be a backslash. The escapes \n and \t are also recognized
3582
in version 3.0.7 and better (to represent a carriage return and a tab, respectively).
3583
These (\n and \t) are primarily for use in custom record templates.
3584
In version 3.0.14 there are 39 options. Note that all of these may also be specified in
3585
the configuration file, to apply to all databases, but if specified in
3586
both places, the entry in the database (user options table) governs.
3587
For more information, see the sample configuration file; each option is preceded
3588
by a brief explanation.
3589
3590
</para>
3591
3592
<para>
3593
The list of options can be found in the section 'System and User Properties'
3594
below.
3595
</para>
3596
</glossdef></glossentry>
3597
</glosslist>
3598
3599
<para>
3600
3601
For example if you would like to replace the default person
3602
record template with the following:
3603
3604
<example>
3605
3606
<title>
3607
Example of replacing the default person record template
3608
</title>
3609
3610
<programlisting>
3611
3612
0 INDI
3613
1 NAME //
3614
1 SEX</programlisting></example>
3615
you would edit the user option file to contain:<example>
3616
3617
<title>
3618
Example of replaced default person record template
3619
</title>
3620
3621
<literallayout>INDIREC=0 INDI\
3622
1 NAME //\
3623
1 SEX</literallayout>
3624
</example>
3625
3626
or, using the \n escape so as to keep the entry on one line:<example>
3627
3628
<title>
3629
Example of replaced single line default person record template
3630
</title>
3631
3632
<literallayout>INDIREC=0 INDI\n1 NAME //\n1 SEX</literallayout>
3633
</example>
3634
3635
</para>
3636
3637
<glosslist>
3638
<glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
3639
3640
<para>
3641
This command returns you to the main menu.
3642
</para>
3643
3644
</glossdef></glossentry>
3645
</glosslist>
3646
3647
3648
</sect1>
3649
3650
<sect1>
3651
3652
<title>
3653
IMPORT ERRORS
3654
</title>
3655
3656
<para>
3657
Errors generated during a GEDCOM import are logged to a file, by default named errs.log.
3658
</para>
3659
<glosslist><glossentry><glossterm>Bad NAME syntax.</glossterm><glossdef>
3660
3661
<para>
3662
3663
A level 1 NAME record must have a value, and the value must not be a pointer, may
3664
have no more than two slashes.
3665
</para>
3666
3667
</glossdef></glossentry><glossentry><glossterm>Family %s has an incorrect key.</glossterm><glossdef>
3668
3669
<para>
3670
3671
Each FAM record must have an XREF value beginning with the letter F.
3672
(The XREF is the letters between "0" and "FAM".)
3673
3674
</para>
3675
3676
</glossdef></glossentry><glossentry><glossterm>Person defined here has no name.</glossterm><glossdef>
3677
3678
<para>
3679
3680
Each INDI record must have at least one level 1 NAME record, if the
3681
configuration option RequireNames is non-zero.
3682
3683
</para>
3684
3685
</glossdef></glossentry><glossentry><glossterm>Person %s has an incorrect key: skipped.</glossterm><glossdef>
3686
3687
<para>
3688
3689
Each INDI record must have an XREF value beginning with the letter I.
3690
(The XREF is the letters between "0" and "INDI".)
3691
3692
</para>
3693
3694
</glossdef></glossentry><glossentry><glossterm>Person %s is multiply defined: skipped.</glossterm><glossdef>
3695
3696
<para>
3697
3698
No XREF value of an INDI may be reused.
3699
(The XREF is the letters between "0" and "INDI".)
3700
3701
</para>
3702
3703
</glossdef></glossentry><glossentry><glossterm>The family defined here has no key.</glossterm><glossdef>
3704
3705
<para>
3706
3707
Each FAM record must have an XREF value.
3708
(The XREF is the letters between "0" and "FAM".)
3709
3710
</para>
3711
3712
</glossdef></glossentry><glossentry><glossterm>The person defined here has no key: skipped.</glossterm><glossdef>
3713
3714
<para>
3715
3716
Each INDI record must have an XREF value.
3717
(The XREF is the letters between "0" and "INDI".)
3718
3719
</para>
3720
3721
</glossdef></glossentry><glossentry><glossterm>This line has a level number that is too large.</glossterm><glossdef>
3722
3723
<para>
3724
3725
A child level must be one higher than its parent level.
3726
3727
</para>
3728
3729
</glossdef></glossentry></glosslist>
3730
3731
</sect1>
3732
3733
<sect1>
3734
3735
3736
3737
<title>
3738
3739
HANDLING SOURCE, EVENT AND USER-DEFINED RECORDS
3740
3741
</title>
3742
3743
3744
3745
<para>
3746
3747
<application>LifeLines</application> supports source, event
3748
and other, user-defined record types. You can access these
3749
features in two ways: either through the x operation from the
3750
main menu, or via commands in the individual and family browse
3751
screens. The first approach might be most convenient when you
3752
are solely working with these record types. The second makes
3753
it easier to work with source, event and user-defined records
3754
in parallel with your person and family records; this can be
3755
useful for instance when you want to create references from
3756
your person and family record to your source, event and user
3757
defined records as you create them, and to view and edit
3758
records that you have referenced from within a person or
3759
family record.
3760
3761
</para>
3762
3763
<para>
3764
3765
Using the first of these two possibilities
3766
<application>LifeLines</application> displays the following
3767
menu:
3768
3769
<screen>
3770
What activity do you want to perform?
3771
3772
s Browse source records
3773
e Browse event records
3774
x Browse other records
3775
1 Add a source record to the database
3776
2 Edit source record from the database
3777
3 Add an event record to the database
3778
4 Edit event record from the database
3779
5 Add an other record to the database
3780
6 Edit other record from the database
3781
q Return to main menu
3782
</screen>
3783
3784
Using the second variant (from the person and family browse
3785
screens), the following six commands are available. The first
3786
three are described alongside with their counterparts in the x
3787
menu (they do mostly, but not entirely, the same things); the
3788
last three are described separately:
3789
3790
<screen>
3791
%s Add source
3792
%e Add event
3793
%o Add other
3794
</screen>
3795
3796
<screen>
3797
$s List sources
3798
$n List notes
3799
$$ List references
3800
</screen>
3801
3802
</para>
3803
3804
3805
3806
<para>
3807
3808
The handling of source, event and user-defined records in
3809
<application>LifeLines</application> is still in
3810
development. For example, sources cannot yet be searched by
3811
REFN or be deleted.
3812
3813
</para>
3814
3815
<glosslist><glossentry><glossterm><keycap>s</keycap>
3816
<action>Browse source records.</action></glossterm><glossdef>
3817
3818
<para>
3819
This will bring up a list of all source records by number, showing
3820
REFN, title, and author for each. A record may be selected
3821
from this list to edit.
3822
</para>
3823
3824
</glossdef></glossentry><glossentry><glossterm><keycap>e</keycap>
3825
<action>Browse event records.</action></glossterm><glossdef>
3826
3827
<para>
3828
This will bring up a list of all event records by number. As of
3829
yet this does not display any information about each event.
3830
(Suggestions as to how to summarize events are welcome).
3831
A record may be selected from this list to edit.
3832
</para>
3833
3834
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap>
3835
<action>Browse other records.</action></glossterm><glossdef>
3836
3837
<para>
3838
This will bring up a list of all other records by number,
3839
showing the 0 level line as summary. A record may be selected
3840
from this list to edit.
3841
</para>
3842
3843
</glossdef></glossentry><glossentry><glossterm><keycap>1</keycap>
3844
<action>Add a source record to the
3845
database.</action></glossterm><glossdef>
3846
3847
<para>
3848
3849
This operation (or alternatively <keycap>%s</keycap> from the
3850
person, family or auxiliary browse screens) is used to add a
3851
new source record to the database.
3852
<application>LifeLines</application> creates a template source
3853
and puts you in the screen editor to edit the template. The
3854
default template is:
3855
3856
<programlisting>
3857
3858
0 SOUR
3859
1 REFN
3860
1 TITL <replaceable>Title</replaceable>
3861
1 AUTH <replaceable>Author</replaceable>
3862
3863
</programlisting>
3864
3865
</para>
3866
3867
3868
3869
<para>
3870
3871
Do not change the <structfield>0 SOUR</structfield>
3872
line. Otherwise you may edit this record any way you like. The
3873
<structfield>1 REFN</structfield> line is a special line you
3874
can use to give the source a symbolic name that can be used in
3875
other records to refer to the source record. See the section
3876
on using <structfield>REFN</structfield> values. Because many
3877
sources have a title and an author, the default template has
3878
these lines. You may adjust the source template via the
3879
SOURREC user option (either at the database level, via the
3880
user options, or globally, via the configuration file). Here
3881
is how I recorded one of the sources in my database:
3882
3883
<example>
3884
3885
<title>
3886
Example of a source record
3887
</title>
3888
3889
<programlisting>
3890
3891
0 SOUR
3892
1 REFN <userinput>jcw</userinput>
3893
1 TITL <userinput>The Wetmore Family of America, and its Collateral Branches: with</userinput>
3894
2 CONT <userinput>Genealogical, Biographical, and Historical Notices</userinput>
3895
1 AUTH <userinput>James Carnahan Wetmore</userinput>
3896
1 PUBL
3897
2 DATE <userinput>1861</userinput>
3898
2 PLAC <userinput>Albany, New York</userinput>
3899
2 INST <userinput>Munsell and Rowland</userinput>
3900
2 ADDR <userinput>78 State Street</userinput></programlisting></example>
3901
3902
</para>
3903
3904
<para>
3905
3906
The add source command in the x menu is equivalent to the
3907
<keycap>%s</keycap> command available in the person or family
3908
browse screen, in terms of entering the source record; after
3909
saving the source record though, there is one significant
3910
difference, in that that you then are presented with the
3911
following prompt (also, the key value of the new record is
3912
displayed in the status bar at this point):
3913
</para>
3914
3915
<screen>
3916
Please choose from the following options:
3917
1: Insert xref automatically at bottom of current record.
3918
2: Edit current record now to add xref manually.
3919
3: Browse new record (without adding xref).
3920
4: Return to current record (without adding xref).
3921
3922
Commands: j Move down k Move up i Select q Quit
3923
</screen>
3924
3925
<para>
3926
3927
The four options perform the following actions:
3928
3929
</para>
3930
3931
<para>
3932
3933
1: LifeLines adds a reference to the new source record at the
3934
bottom of the person or family record that was visible in the
3935
display screen when you prompted LifeLines to create the new
3936
source record.
3937
3938
</para>
3939
3940
<para>
3941
3942
2: LifeLines will open the person or family record that was
3943
visible in the display screen when you prompted LifeLines to
3944
create the new source record, so that you can manually enter a
3945
reference to the newly created source record (perhaps as a
3946
source reference to an event that you are planning to add).
3947
3948
</para>
3949
3950
<para>
3951
3952
3: LifeLines lets you browse (and optionally reopen for
3953
editing) your newly added source record.
3954
3955
</para>
3956
3957
<para>
3958
3959
4: You are returned to the person or family record that was
3960
visible in the display screen when you prompted LifeLines to
3961
create the new source record. No reference is added to the new
3962
record.
3963
3964
</para>
3965
3966
</glossdef></glossentry><glossentry><glossterm><keycap>2</keycap> <action>Edit source record from the database.</action></glossterm>
3967
<glossdef>
3968
3969
<para>
3970
3971
Use this operation to edit an existing source record already in
3972
the database. When you select this operation
3973
<application>LifeLines</application> asks you to identify a source:
3974
<screen>
3975
Which source record do you want to edit?
3976
enter key or refn:
3977
</screen>
3978
3979
3980
</para>
3981
3982
3983
3984
<para>
3985
3986
Identify a source by entering its key value, with or without the leading S, or by entering its <structfield>REFN</structfield>
3987
value. <application>LifeLines</application> retrieves the record and puts you in the editor with the record.
3988
3989
</para>
3990
3991
</glossdef></glossentry><glossentry><glossterm><keycap>3</keycap> <action>Add an event record to the database.</action></glossterm><glossdef>
3992
3993
<para>
3994
3995
This operation (or alternatively <keycap>%e</keycap> from the person,
3996
family or auxiliary browse screens) adds a new event record to the
3997
database. <application>LifeLines</application> creates a template
3998
event and puts you in the screen editor to edit the template. The
3999
default template is:<programlisting>
4000
4001
0 EVEN
4002
1 REFN
4003
1 DATE
4004
1 PLAC
4005
1 INDI
4006
2 NAME
4007
2 ROLE
4008
1 SOUR</programlisting>
4009
4010
</para>
4011
4012
<para>
4013
4014
You may adjust the event template via the EVENREC user option (either
4015
at the database level, via the user options, or globally, via the
4016
configuration file).
4017
4018
</para>
4019
4020
<para>
4021
4022
Do not change the <structfield>0 EVEN</structfield>
4023
line. Otherwise you may edit this record any way you like. The
4024
<structfield>1 REFN</structfield> line allows you to give this
4025
event a symbolic name you can use when you want to refer to
4026
this event from other records. See the section on using
4027
<structfield>REFN</structfield> values. The default template
4028
suggests that an event has a date, a place, and refers to
4029
persons in roles with respect to the event. There is far less
4030
experience with event-based <acronym>GEDCOM</acronym> than
4031
there is with simple person and family
4032
<acronym>GEDCOM</acronym>. You may even be wondering why you
4033
would need event records when you can simply tuck events away
4034
in person and family records. This is a topic that may get
4035
covered in an appendix.
4036
4037
</para>
4038
4039
<para>
4040
4041
The add event command in the x menu is equivalent to the
4042
<keycap>%e</keycap> command available in the person or family
4043
browse screen, in terms of entering the event record; after
4044
saving the event record though, there is one significant
4045
difference, in that that you then are presented with the
4046
following prompt (also, the key value of the new record is
4047
displayed in the status bar at this point):
4048
</para>
4049
4050
<screen>
4051
Please choose from the following options:
4052
1: Insert xref automatically at bottom of current record.
4053
2: Edit current record now to add xref manually.
4054
3: Browse new record (without adding xref).
4055
4: Return to current record (without adding xref).
4056
4057
Commands: j Move down k Move up i Select q Quit
4058
</screen>
4059
4060
<para>
4061
4062
The four options perform the following actions:
4063
4064
</para>
4065
4066
<para>
4067
4068
1: LifeLines adds a reference to the new event record at the
4069
bottom of the person or family record that was visible in the
4070
display screen when you prompted LifeLines to create the new
4071
event record.
4072
4073
</para>
4074
4075
<para>
4076
4077
2: LifeLines will open the person or family record that was
4078
visible in the display screen when you prompted LifeLines to
4079
create the new event record, so that you can manually enter a
4080
reference to the newly created event record.
4081
4082
</para>
4083
4084
<para>
4085
4086
3: LifeLines lets you browse (and optionally reopen for
4087
editing) your newly added event record.
4088
4089
</para>
4090
4091
<para>
4092
4093
4: You are returned to the person or family record that was
4094
visible in the display screen when you prompted LifeLines to
4095
create the new event record. No reference is added to the new
4096
record.
4097
4098
</para>
4099
4100
</glossdef></glossentry><glossentry><glossterm><keycap>4</keycap> <action>Edit event record from the database.</action></glossterm><glossdef>
4101
4102
<para>
4103
4104
Use this operation to edit an existing event record from the
4105
database . When you select this operation
4106
<application>LifeLines</application> asks you to identify an
4107
event:
4108
4109
<screen>
4110
Which event record do you want to edit?
4111
enter key or refn:
4112
</screen>
4113
4114
4115
</para>
4116
4117
4118
4119
<para>
4120
4121
You identify a event by entering its key value, with or
4122
without the leading E, or by entering its
4123
<structfield>REFN</structfield>
4124
value. <application>LifeLines</application> retrieves the
4125
record and places you in the screen editor with the record.
4126
4127
</para>
4128
4129
</glossdef></glossentry><glossentry><glossterm><keycap>5</keycap> <action>Add an other record to the database.</action></glossterm><glossdef>
4130
4131
<para>
4132
4133
This operation (or alternatively <keycap>%o</keycap> from the
4134
person, family or auxiliary browse screens) adds a new
4135
user-defined record to the database.
4136
<application>LifeLines</application> creates a template and
4137
puts you in the screen editor to edit the template. The
4138
default template is
4139
4140
<programlisting>
4141
0 XXXX
4142
1 REFN
4143
</programlisting>
4144
</para>
4145
4146
4147
4148
<para>
4149
4150
Replace <replaceable>XXXX</replaceable> with the tag string
4151
you select for the type of the new record. You are free to
4152
choose any tag value except <structfield>INDI</structfield>,
4153
<structfield>FAM</structfield>,
4154
<structfield>SOUR</structfield> and
4155
<structfield>EVEN</structfield>. For example, if you keep
4156
record information about the ships that your North American
4157
immigrant ancestors arrived on, you would keep records about
4158
those ships in your database; the tag
4159
<structfield>SHIP</structfield> suggests itself for such
4160
records. The <structfield>1 REFN</structfield> line allows you
4161
to give this record a symbolic name you can use when you want
4162
to refer to it from other records. See the section on using
4163
<structfield>REFN</structfield> values. You may adjust the
4164
other template via the OTHR user option (either at the database
4165
level, via the user options, or globally, via the configuration
4166
file).
4167
4168
</para>
4169
4170
<para>
4171
4172
The add other record command in the x menu is equivalent to the
4173
<keycap>%o</keycap> command available in the person or family
4174
browse screen, in terms of entering the other record; after
4175
saving the record though, there is one significant difference,
4176
in that that you then are presented with the following prompt
4177
(also, the key value of the new record is displayed in the
4178
status bar at this point):
4179
</para>
4180
4181
<screen>
4182
Please choose from the following options:
4183
1: Insert xref automatically at bottom of current record.
4184
2: Edit current record now to add xref manually.
4185
3: Browse new record (without adding xref).
4186
4: Return to current record (without adding xref).
4187
4188
Commands: j Move down k Move up i Select q Quit
4189
</screen>
4190
4191
<para>
4192
4193
The four options perform the following actions:
4194
4195
</para>
4196
4197
<para>
4198
4199
1: LifeLines adds a reference to the new other record at the
4200
bottom of the person or family record that was visible in the
4201
display screen when you prompted LifeLines to create the new
4202
other record.
4203
4204
</para>
4205
4206
<para>
4207
4208
2: LifeLines will open the person or family record that was
4209
visible in the display screen when you prompted LifeLines to
4210
create the new other record, so that you can manually enter a
4211
reference to the newly created other record (perhaps as a
4212
note reference to an event that you are planning to add).
4213
4214
</para>
4215
4216
<para>
4217
4218
3: LifeLines lets you browse (and optionally reopen for
4219
editing) your newly added other record.
4220
4221
</para>
4222
4223
<para>
4224
4225
4: You are returned to the person or family record that was
4226
visible in the display screen when you prompted LifeLines to
4227
create the new other record. No reference is added to the new
4228
record.
4229
4230
</para>
4231
4232
</glossdef></glossentry><glossentry><glossterm><keycap>6</keycap> <action>Edit other record from the database.</action></glossterm><glossdef>
4233
4234
<para>
4235
4236
Use this operation to edit an existing user-defined record
4237
from the database. When you select this operation
4238
<application>LifeLines</application> asks you to identify the
4239
record:
4240
4241
<screen>
4242
What record do you want to edit?
4243
enter key or refn:
4244
</screen>
4245
4246
4247
</para>
4248
4249
<para>
4250
4251
You identify a record by entering its key value, with or
4252
without the leading X, or by entering its
4253
<structfield>REFN</structfield>
4254
value. <application>LifeLines</application> retrieves the
4255
record and places you in the screen editor with the record.
4256
4257
</para>
4258
4259
</glossdef></glossentry><glossentry><glossterm><keycap>$s</keycap>
4260
<action>List sources</action></glossterm><glossdef>
4261
4262
<para>
4263
4264
This command is available in the person and family browse
4265
screens. It will bring up a list of all source records that
4266
are referenced within the currently displayed person or family
4267
record, by the order they appear in the person/family record,
4268
showing REFN, title, and author for each. A record may be
4269
selected from this list to view in the auxiliary browse screen
4270
(and optionally be edited from there).
4271
4272
</para>
4273
4274
4275
</glossdef></glossentry><glossentry><glossterm><keycap>$n</keycap>
4276
<action>List notes</action></glossterm><glossdef>
4277
4278
<para>
4279
4280
This command is available in the person and family browse
4281
screens. It will bring up a list of all note records that are
4282
referenced within the currently displayed person or family
4283
record, by the order they appear in the person/family record,
4284
showing REFN, title, and author for each. A record may be
4285
selected from this list to view in the auxiliary browse screen
4286
(and optionally be edited from there).
4287
4288
</para>
4289
4290
</glossdef></glossentry><glossentry><glossterm><keycap>$$</keycap>
4291
<action>List all references</action></glossterm><glossdef>
4292
4293
<para>
4294
4295
This command is available in the person and family browse
4296
screens. It will bring up a list of all records that are
4297
referenced within the currently displayed person or family
4298
record, by the order they appear in the person/family record,
4299
showing REFN, title, and author for each. A record may be
4300
selected from this list to view in the auxiliary browse screen
4301
(and optionally be edited from there).
4302
4303
</para>
4304
4305
</glossdef></glossentry></glosslist>
4306
4307
</sect1>
4308
4309
4310
4311
<sect1>
4312
4313
<title>
4314
FAMILY STRUCTURE AND MERGING PERSONS AND FAMILIES
4315
</title>
4316
4317
<para>
4318
4319
<application>LifeLines</application> 3.0.2 has relaxed most of
4320
restrictions on family structure that were imposed by earlier
4321
versions. For example, a family record may have more than one
4322
parent/spouse of the same sex; a person may be a child in more
4323
than family. This is a controversial issue. Some users insist
4324
that family relationships should imply biological relatedness,
4325
and that all other relationships should be handled by
4326
different means. Others insist that non-traditional families
4327
(any number of parents/spouses of any sex) should be allowed,
4328
and that children can be members of more than one family (eg,
4329
natural family and adoptive
4330
family). <application>LifeLines</application> no longer takes
4331
a position on this matter; you are free to set up families any
4332
way you like; the operations that add spouses and children to
4333
families no longer check for non-traditional arrangements. It
4334
is possible that a future release will include a user option
4335
to either disallow or to ask for confirmation about
4336
non-traditional relationships.
4337
4338
</para>
4339
4340
4341
4342
<para>
4343
4344
<application>LifeLines</application> provides features for
4345
merging persons together and for merging families
4346
together. The person merging feature is accessed from the
4347
tandem person browse mode, and the family merging feature is
4348
accessed from the tandem family browse mode. You browse to the
4349
two persons or families you want to merge and then use the j
4350
command. Merging is necessary when you discover that two or
4351
more person records, or two or more family records, represent
4352
the same person or family, respectively.
4353
4354
</para>
4355
4356
4357
4358
<para>
4359
4360
Versions of <application>LifeLines</application> prior to
4361
3.0.2 required that persons and families meet certain criteria
4362
before they could be merged. The criteria ensured that the
4363
merged persons and families would still meet traditional
4364
family structuring rules. With the relaxation of the
4365
structuring rules, restrictions on merging have also been
4366
removed. It is now possible to create non-traditional
4367
relationships by merging traditional persons and/or
4368
families. For example, if you merge two persons that happen to
4369
be children in two different families, the merged person will
4370
be a child in both families. If you want to maintain only
4371
traditional relationships in your database you may have to
4372
makes further to changes to relationships after you complete a
4373
merge operation.
4374
4375
</para>
4376
4377
4378
4379
</sect1>
4380
4381
4382
4383
<sect1>
4384
4385
4386
4387
<title>
4388
4389
LINKING RECORDS TOGETHER AND USING THE REFN FEATURE
4390
4391
</title>
4392
4393
4394
4395
<para>
4396
4397
Records in a <application>LifeLines</application> database may
4398
refer to other records via cross-reference links. The
4399
lineage-linked references are maintained directly by
4400
<application>LifeLines</application> through operations found
4401
in the browsing mode menus. These references are the links
4402
from a person to families (<structfield>1 FAMC</structfield>
4403
and <structfield>1 FAMS</structfield>), and the links from a
4404
family to persons (<structfield>1 HUSB</structfield>,
4405
<structfield>1 WIFE</structfield> and <structfield>1
4406
CHIL</structfield>). Because
4407
<application>LifeLines</application> maintains these links you
4408
are not allowed to change these lines when you are editing
4409
records. There are a couple of seeming exceptions to this
4410
rule. For example, you may change the order of <structfield>1
4411
CHIL</structfield> lines in a family record in order to change
4412
the order of children in a family, and you may change the
4413
order of <structfield>1 FAMS</structfield> lines in a person
4414
record to change the order of families the person was a spouse
4415
or parent in. These operations are allowed because they don't
4416
affect which person records refer to which family records and
4417
vice versa.
4418
4419
</para>
4420
4421
4422
4423
<para>
4424
4425
Besides the lineage-links that are maintained by
4426
<application>LifeLines</application>, you may place your own
4427
links in records. Probably the most common example of this is
4428
referring events within a person record to the record of the
4429
information source for the event. For example:
4430
4431
4432
<example>
4433
4434
<title>
4435
Example of referring events from a person record
4436
</title>
4437
4438
<programlisting>
4439
4440
0 @I23@ INDI
4441
1 NAME <userinput>Thomas/Whitmore/</userinput>
4442
1 BIRT
4443
2 DATE <userinput>about 1615</userinput>
4444
2 PLAC <userinput>England</userinput>
4445
2 SOUR @S3@
4446
...
4447
0 @S3@ SOUR
4448
1 REFN <userinput>cat</userinput>
4449
1 TITL <userinput>New England Marriages Prior to 1700</userinput>
4450
1 AUTH <userinput>Clarence Almon Torrey</userinput>
4451
...</programlisting></example>
4452
4453
</para>
4454
4455
4456
4457
<para>
4458
4459
The <structfield>2 SOUR</structfield> <replaceable>@S3@</replaceable> line in the person record refers to the source record. <application>LifeLines</application> allows any specific
4460
structure within a record (in this case a birth event) to refer to another record. It is not possible to refer
4461
to a specific location within another record, though this may be supported eventually.
4462
4463
4464
</para>
4465
4466
4467
4468
<para>
4469
4470
This example implies that when linking one record to another you must know the key of the target
4471
record (S3 in the example). This is not desirable because internal record keys may change when the
4472
records are exported from one database or imported to another.
4473
4474
</para>
4475
4476
4477
4478
<para>
4479
4480
Because internal key values are not permanent,
4481
<application>LifeLines</application> allows you to assign a
4482
permanent user-defined key to any record in the database using
4483
the <structfield>1 REFN</structfield> line. The value of this
4484
line is a string that you choose as your permanent key value
4485
for the record. When adding a link to a record that has a user
4486
<structfield>REFN</structfield> key value, you may use that
4487
value instead of the internal key value. For example, when
4488
adding the person in the previous example you could edit the
4489
new record as follows:
4490
4491
<example>
4492
4493
<title>
4494
Example of adding a new person
4495
</title>
4496
4497
<programlisting>
4498
4499
0 INDI
4500
1 NAME <userinput>Thomas/Whitmore/</userinput>
4501
1 BIRT
4502
2 DATE <userinput>about 1615</userinput>
4503
2 PLAC <userinput>England</userinput>
4504
2 SOUR <userinput><cat></userinput></programlisting></example>
4505
4506
</para>
4507
4508
4509
4510
<para>
4511
4512
Instead of using the actual key value of the source, S3, the
4513
<structfield>REFN</structfield> value cat was used. The
4514
<structfield>REFN</structfield> value must be enclosed by
4515
angle brackets when used this
4516
way. <application>LifeLines</application> automatically
4517
replaces the <structfield>REFN</structfield> link with the
4518
proper internal key value when the record is stored in the
4519
database.
4520
4521
4522
</para>
4523
4524
4525
4526
<para>
4527
4528
The <structfield>REFN</structfield> value may also be used
4529
when searching for person, source, event and user-defined
4530
records. You should not add more than one
4531
<structfield>REFN</structfield> line to a record, and every
4532
<structfield>REFN</structfield> value should be unique.
4533
4534
</para>
4535
4536
</sect1>
4537
4538
4539
<sect1>
4540
4541
4542
4543
<title>
4544
4545
System and User Properties
4546
4547
</title>
4548
4549
<para>
4550
There are a number of properties that can be specified to customize
4551
the behavior of <application>LifeLines</application>. These properties can
4552
be specified in <application>LifeLines</application>
4553
customization files, in each <application>LifeLines</application> database
4554
or in some cases by environment variables.
4555
</para>
4556
<para>
4557
<application>LifeLines</application> configuration files are look for
4558
first in the directory specified by the HOME environment variable, assuming
4559
that it is set, and then in the current directory. The name of the
4560
configuration file is .linesrc on <acronym>UNIX</acronym> or linux systems
4561
and lines.cfg on windows systems.
4562
4563
</para>
4564
<para>
4565
A configuration file can also be specified using the -C option to
4566
<application>LifeLines</application>
4567
or by defining the environment variable "LLCONFIGFILE" with a value containing
4568
the full pathname of the configuration file. If either of these
4569
mechanisms is used, <application>LifeLines</application> does not look for a
4570
configuration file anywhere else.
4571
If a -C option is provided, the LLCONFIGFILE environment variable, if defined,
4572
is ignored. If neither the -C option nor the environment variable
4573
LLCONFIGFILE is set, the above mentioned configuration file names are used.
4574
A configuration file is looked for in your home directory and is read in,
4575
if it exists, and then if a configuration file exists in the current
4576
directory it is read. The values in this second file are used to replace
4577
or supplement values found in the first file.
4578
</para>
4579
4580
<para>
4581
When <application>LifeLines</application> searches for a property it looks for it as follows:
4582
</para>
4583
<glosslist>
4584
4585
<glossentry><glossterm>cmdline table</glossterm><glossdef>
4586
4587
<para>
4588
First, <application>LifeLines</application> looks in the cmdline table. This table contains the
4589
values that have been specified using the -I option to
4590
<application>LifeLines</application>.
4591
</para>
4592
</glossdef></glossentry>
4593
4594
<glossentry><glossterm>database table</glossterm><glossdef>
4595
4596
<para> Next, <application>LifeLines</application> looks in the database table. This table contains the
4597
values which have been stored in the current database.
4598
</para>
4599
</glossdef></glossentry>
4600
4601
<glossentry><glossterm>global table</glossterm><glossdef>
4602
4603
<para>
4604
Next, <application>LifeLines</application> looks in the global table. This table contains the
4605
values found when reading in the configuration files.
4606
</para>
4607
</glossdef></glossentry>
4608
4609
<glossentry><glossterm>environment table</glossterm><glossdef>
4610
4611
<para>
4612
Finally, <application>LifeLines</application> looks in the environment table. This table contains the
4613
values found in the environment variables, LLPROGRAMS, LLREPORTS,
4614
LLARCHIVES, LLDATABASES, LLNEWDBDIR, and LLEDITOR.
4615
</para>
4616
</glossdef></glossentry>
4617
</glosslist>
4618
4619
4620
<para>
4621
Properties are named group.subgroup.property or group.property, or even
4622
just property.
4623
The following keys are available at the moment:
4624
</para>
4625
4626
<glosslist>
4627
<glossentry><glossterm>LLPROGRAMS</glossterm><glossdef>
4628
4629
<para>
4630
<envar>LLPROGRAMS</envar> is the search path for
4631
<application>LifeLines</application> report generating and
4632
other programs.
4633
</para>
4634
</glossdef></glossentry>
4635
4636
<glossentry><glossterm>LLREPORTS</glossterm><glossdef>
4637
4638
<para>
4639
<envar>LLREPORTS</envar> is used to select a directory where
4640
all generated reports and program outputs will be placed.
4641
</para>
4642
</glossdef></glossentry>
4643
4644
<glossentry><glossterm>LLARCHIVES</glossterm><glossdef>
4645
4646
<para>
4647
<envar>LLARCHIVES</envar> is used to select a
4648
directory where all database backup files will be stored
4649
</para>
4650
</glossdef></glossentry>
4651
4652
<glossentry><glossterm>LLDATABASES</glossterm><glossdef>
4653
4654
<para>
4655
<envar>LLDATABASES</envar> is a list of
4656
directories that contain database directories used to locate
4657
database directories themselves
4658
</para>
4659
</glossdef></glossentry>
4660
4661
<glossentry><glossterm>LLNEWDBDIR</glossterm><glossdef>
4662
4663
<para>
4664
<envar>LLNEWDBDIR</envar> a single directory where new databases
4665
specified without paths will be created.
4666
This is a convenience for users
4667
who generally put all their databases under a single common
4668
directory.
4669
</para>
4670
</glossdef></glossentry>
4671
4672
<glossentry><glossterm>LLEDITOR</glossterm><glossdef>
4673
4674
<para>
4675
Overrides the default screen editor
4676
</para>
4677
</glossdef></glossentry>
4678
</glosslist>
4679
4680
<para>
4681
Codeset Information:
4682
</para>
4683
<para>
4684
For the following parameters related to codeset, the values are a
4685
String denoting code set in use in data. Special handling is provided
4686
for UTF-8, which may be entered as "UTF-8", "utf-8", or "65001". (The
4687
official, and preferred, name is UTF-8.
4688
</para>
4689
<glosslist>
4690
<glossentry><glossterm>GedcomCodeSet</glossterm><glossdef>
4691
4692
<para>
4693
Specifies the default Codeset to use when processing Gedcom files.
4694
There are actually 3 properties.
4695
<glossterm>GedcomCodeSetOut</glossterm> and <glossterm>GedcomCodeSetIn</glossterm>
4696
can be used to specify the codeset for output or input. If either of these is
4697
not specified <glossterm>GedcomCodeSet</glossterm> is used. Most Gedcom files should
4698
contain a codeset property, so this is not usually relevant when reading a Gedcom
4699
file, unless the input Gedcom file lacks a codeset property. This is used, however,
4700
when writing out a Gedcom file.
4701
NB: This is ignored if the database has no internal codeset specified.
4702
</para>
4703
</glossdef></glossentry>
4704
4705
<glossentry><glossterm>EditorCodeSet</glossterm><glossdef>
4706
4707
<para>
4708
Specifies the codeset to use for editing. There are actually 3 properties.
4709
<glossterm>EditorCodeSetOut</glossterm> and <glossterm>EditorCodeSetIn</glossterm>
4710
can be used to specify the codeset for output or input. If either of these is
4711
not specified <glossterm>EditorCodeSet</glossterm> is used. This property allows
4712
lifelines to convert from its internal codeset to the one you use in your editor, so
4713
this is important when your editor does not use the same codeset as your database.
4714
NB: This is ignored if the database has no internal codeset specified.
4715
</para>
4716
</glossdef></glossentry>
4717
4718
<glossentry><glossterm>ReportCodeSet</glossterm><glossdef>
4719
4720
<para>
4721
Specifies the codeset to use for reports. There are actually 3 properties.
4722
<glossterm>ReportCodeSetOut</glossterm> and <glossterm>ReportCodeSetIn</glossterm>
4723
can be used to specify the codeset for output or input. If either of these is
4724
not specified <glossterm>ReportCodeSet</glossterm> is used. Recently created
4725
reports may actually specify their codeset, in which case this is not used, but
4726
for reports which do not include a specification of codeset, the
4727
<glossterm>ReportCodeSetIn</glossterm> (or <glossterm>ReportCodeSet</glossterm>)
4728
specifies how the report will be understood. In any case, the output of a
4729
report program will be written in the codeset given by
4730
<glossterm>ReportCodeSetOut</glossterm> (or <glossterm>ReportCodeSet</glossterm>).
4731
NB: This is ignored if the database has no internal codeset specified.
4732
</para>
4733
</glossdef></glossentry>
4734
4735
<glossentry><glossterm>LongDisplayDate</glossterm><glossdef>
4736
4737
<para>
4738
Six comma separated numbers. Specifing the format for
4739
days, months, years, date format, era format, and complex format.
4740
If string does not contain 6 comma separated numbers all formats are
4741
set to 0, except date format is set to 14.
4742
These formats are used by <application>LifeLines</application> to display dates in long format.
4743
</para>
4744
</glossdef></glossentry>
4745
4746
<glossentry><glossterm>LongDisplayDatePic</glossterm><glossdef>
4747
4748
<para>
4749
a custom ymd date picture. A string in which %y, %m and %d will be
4750
converted to the corresponding year, month and day.
4751
This picture is used by <application>LifeLines</application> to display dates in long format.
4752
</para>
4753
</glossdef></glossentry>
4754
4755
<glossentry><glossterm>ShortDisplayDate</glossterm><glossdef>
4756
4757
<para>
4758
Six comma separated numbers. Specifing the format for
4759
days, months, years, date format, era format, and complex format.
4760
If string does not contain 6 comma separated numbers all formats are
4761
set to 0, except date format is set to 14.
4762
These formats are used by <application>LifeLines</application> to display dates in short format.
4763
</para>
4764
</glossdef></glossentry>
4765
4766
<glossentry><glossterm>ShortDisplayDatePic</glossterm><glossdef>
4767
4768
<para>
4769
a custom ymd date picture. A string in which %y, %m and %d will be
4770
converted to the corresponding year, month and day.
4771
This picture is used by <application>LifeLines</application> to display dates in short format.
4772
</para>
4773
</glossdef></glossentry>
4774
4775
<glossentry><glossterm>LocaleDir</glossterm><glossdef>
4776
4777
<para>
4778
run-time specification of locale directory
4779
</para>
4780
</glossdef></glossentry>
4781
4782
<glossentry><glossterm>NewDbProps</glossterm><glossdef>
4783
4784
<para>
4785
if specified, properties to add to a newly created database.
4786
The string is of the form "option1=value1\noption2=value2".
4787
</para>
4788
</glossdef></glossentry>
4789
4790
<glossentry><glossterm>IllegalChar</glossterm><glossdef>
4791
4792
<para>
4793
Apparently not used at this time.
4794
</para>
4795
</glossdef></glossentry>
4796
4797
<glossentry><glossterm> DenySystemCalls</glossterm><glossdef>
4798
4799
<para>
4800
If set to a non-zero value will disable use of the <function>system</function>
4801
function.
4802
</para>
4803
</glossdef></glossentry>
4804
4805
<glossentry><glossterm>UiLocaleCollate</glossterm><glossdef>
4806
4807
<para>
4808
ui collating sequence
4809
</para>
4810
</glossdef></glossentry>
4811
4812
<glossentry><glossterm>UiLocaleMessages</glossterm><glossdef>
4813
<para>
4814
ui messages locale
4815
</para>
4816
</glossdef></glossentry>
4817
4818
<glossentry><glossterm>RptLocaleCollate</glossterm><glossdef>
4819
4820
<para>
4821
Report Collating Sequence
4822
</para>
4823
</glossdef></glossentry>
4824
4825
<glossentry><glossterm>RptLocaleMessages</glossterm><glossdef>
4826
4827
<para>
4828
Report Messages Locale
4829
</para>
4830
</glossdef></glossentry>
4831
4832
<glossentry><glossterm>ShortOmitString</glossterm><glossdef>
4833
4834
<para>
4835
If defined this string replaces characters at the end of an event being
4836
printed.
4837
</para>
4838
</glossdef></glossentry>
4839
4840
<glossentry><glossterm>DisplayKeyTags</glossterm><glossdef>
4841
4842
<para>
4843
If set to 1 an i or f is prepended to individual and family keys when shown
4844
on-screen.
4845
</para>
4846
</glossdef></glossentry>
4847
4848
<glossentry><glossterm>AnnotatePointers</glossterm><glossdef>
4849
4850
<para>
4851
If set to 1 a descriptive comment is added to pointers when editing family or
4852
individual records to help identify who is being refered to. These tags
4853
are removed when the edit is finished and not stored in the database.
4854
</para>
4855
4856
</glossdef></glossentry>
4857
4858
<glossentry><glossterm>TTPATH</glossterm><glossdef>
4859
4860
<para>
4861
4862
list of directories to search for translation table files (*.tt)
4863
</para>
4864
</glossdef></glossentry>
4865
4866
<glossentry><glossterm>TTDIR</glossterm><glossdef>
4867
4868
<para>
4869
Dir to look for Codeset information in ???
4870
</para>
4871
</glossdef></glossentry>
4872
4873
<glossentry><glossterm>InputPath</glossterm><glossdef>
4874
4875
<para>
4876
path to look for in when reading in gedcom files
4877
</para>
4878
</glossdef></glossentry>
4879
4880
<glossentry><glossterm>INDIREC</glossterm><glossdef>
4881
4882
<para>
4883
The default template to use whenever creating a new individual.
4884
If not specified, the concatenation of the following is used:
4885
<programlisting>
4886
"0 INDI\n1 NAME Fname/Surname\n1 SEX MF\n"
4887
"1 BIRT\n 2 DATE\n 2 PLAC\n"
4888
"1 DEAT\n 2 DATE\n 2 PLAC\n1 SOUR\n"
4889
</programlisting>
4890
</para>
4891
</glossdef></glossentry>
4892
4893
<glossentry><glossterm>FAMRECBODY</glossterm><glossdef>
4894
4895
<para>
4896
The default template to use whenever creating a new family.
4897
If not specified, the following is used:
4898
<programlisting>
4899
"1 MARR\n 2 DATE\n 2 PLAC\n 2 SOUR\n"
4900
</programlisting>
4901
Note: Unlike the others, this should not
4902
include the 0 level FAM tag.)
4903
</para>
4904
</glossdef></glossentry>
4905
4906
<glossentry><glossterm>SOURREC</glossterm><glossdef>
4907
4908
<para>
4909
The default template to use whenever creating a new source.
4910
If not specified, the following is used in english:
4911
<programlisting>
4912
"0 SOUR\n1 REFN\n1 TITL Title\n1 AUTH Author"
4913
</programlisting>
4914
</para>
4915
</glossdef></glossentry>
4916
4917
<glossentry><glossterm>EVENREC</glossterm><glossdef>
4918
4919
<para>
4920
The default template to use whenever creating a new event.
4921
If not specified, the following is used in english:
4922
<programlisting>
4923
"0 EVEN\n1 REFN\n1 DATE\n1 PLAC\n1 INDI\n 2 NAME\n 2 ROLE\n1 SOUR"
4924
</programlisting>
4925
</para>
4926
</glossdef></glossentry>
4927
4928
<glossentry><glossterm>OTHR</glossterm><glossdef>
4929
4930
<para>
4931
The default template to use whenever creating a new other record.
4932
If not specified, the following is used in english:
4933
<programlisting>
4934
"0 XXXX\n1 REFN"
4935
</programlisting>
4936
</para>
4937
</glossdef></glossentry>
4938
4939
<glossentry><glossterm>HDR_SUBM</glossterm><glossdef>
4940
4941
<para>
4942
string to use when writing gedcom files for the SUBM.
4943
Default is
4944
<programlisting>
4945
"1 SUBM".
4946
</programlisting>
4947
</para>
4948
</glossdef></glossentry>
4949
4950
<glossentry><glossterm>HDR_GEDC</glossterm><glossdef>
4951
4952
<para>
4953
String containing the GEDC block for the header record when exporting GEDCOM.
4954
The default is
4955
<programlisting>
4956
"1 GEDC\n2 VERS 5.5\n2 FORM LINEAGE-LINKED".
4957
</programlisting>
4958
</para>
4959
</glossdef></glossentry>
4960
4961
<glossentry><glossterm>HDR_CHAR</glossterm><glossdef>
4962
4963
<para>
4964
String containing the CHAR block for the header record when exporting GEDCOM.
4965
The default is
4966
<programlisting>
4967
"1 CHAR ASCII".
4968
</programlisting>
4969
</para>
4970
</glossdef></glossentry>
4971
4972
<glossentry><glossterm>ReportLog</glossterm><glossdef>
4973
4974
<para>
4975
name of file to print report program errors to, if not specified
4976
use stdout curses window.
4977
</para>
4978
</glossdef></glossentry>
4979
4980
<glossentry><glossterm>CrashLog_llexec</glossterm><glossdef>
4981
4982
<para>
4983
file to write crash log into for llexec.
4984
</para>
4985
</glossdef></glossentry>
4986
4987
<glossentry><glossterm>CrashLog_llines</glossterm><glossdef>
4988
4989
<para>
4990
file to write crash log into for llines.
4991
</para>
4992
</glossdef></glossentry>
4993
<glossentry><glossterm>LLTTEXPORT</glossterm><glossdef>
4994
4995
<para>
4996
directory to write translation tables to. Default is the current
4997
directory.
4998
</para>
4999
</glossdef></glossentry>
5000
5001
<glossentry><glossterm>ImportLog</glossterm><glossdef>
5002
5003
<para>
5004
where to log errors found while importing a gedcom file.
5005
default is errs.log.
5006
</para>
5007
</glossdef></glossentry>
5008
5009
<glossentry><glossterm>gettext.path</glossterm><glossdef>
5010
5011
<para>
5012
for windows, if specified path to (re)load gettext dll
5013
</para>
5014
</glossdef></glossentry>
5015
5016
<glossentry><glossterm>iconv.path</glossterm><glossdef>
5017
5018
<para>
5019
for Windows, path to link dynamically to gettext and iconv
5020
</para>
5021
</glossdef></glossentry>
5022
5023
<glossentry><glossterm>user.fullname</glossterm><glossdef>
5024
5025
<para>
5026
The full name of the current user. If not found as a property it is fetched
5027
from the system when possible.
5028
</para>
5029
</glossdef></glossentry>
5030
5031
<glossentry><glossterm>user.email</glossterm><glossdef>
5032
5033
<para>
5034
The email address of the current user. If not found as a property it is
5035
fetched from the system when possible.
5036
</para>
5037
</glossdef></glossentry>
5038
5039
<glossentry><glossterm>user.address</glossterm><glossdef>
5040
5041
<para>
5042
Postal address of the current user.
5043
</para>
5044
</glossdef></glossentry>
5045
5046
<glossentry><glossterm>user.url</glossterm><glossdef>
5047
5048
<para>
5049
URL to the users home page.
5050
</para>
5051
</glossdef></glossentry>
5052
</glosslist>
5053
5054
</sect1>
5055
5056
</chapter>
5057
</book>
5058
1
<?xml version='1.0' encoding='iso-8859-1'?>
2
3
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
4
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
5
[<!ENTITY llversion '3.0.50'>]>
6
7
<book id="docbook">
8
9
<bookinfo>
10
11
12
<!--
13
14
this is lifelines.xml
15
16
To use this file with SGML software, replace the text above
17
this comments section with the following:
18
19
_________________________________________________________
20
21
<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
22
<!entity llversion "3.0.50">
23
]>
24
25
<book id="docbook">
26
<?dbhtml filename="ll-doc.htm">
27
<bookinfo>
28
_________________________________________________________
29
30
31
Rafal Prinke <rafalp@amu.edu.pl> 1-Apr-200
32
- Converted original LifeLines Reference Guide to DocBook SGML.
33
34
35
Marc Nozell <marc@nozell.com> 26-Jul-2001
36
- Changed <simpara> to <para>. Newer docbook likes it better.
37
38
Marc Nozell <marc@nozell.com> 21-Sep-2000
39
- updated license info
40
- point to lifelines.sourceforge.net
41
- change references from lines302 to llines
42
- make most lines less than 80 characters wide
43
44
Rafal Prinke <rafalp@amu.edu.pl> 30-Dec-2001
45
- Converted to XML.
46
- closed all <para> elements
47
- defined and corrected llversion entity
48
- closed empty tag <void />
49
- converted all tags to lower case
50
- replaced ampersands with entities
51
- added space at end of line
52
- parsed against DocBook 4.1.2 DTD
53
54
-->
55
<!-- ================================================= -->
56
57
<title>
58
59
<application>LifeLines</application> Documentation
60
</title>
61
62
<authorgroup>
63
<author>
64
<firstname>Thomas T. </firstname>
65
<surname>Wetmore </surname>
66
<lineage>IV</lineage>
67
</author>
68
</authorgroup>
69
70
<subtitle><application>LifeLines</application> Version &llversion;</subtitle>
71
</bookinfo>
72
73
<chapter>
74
75
<title>
76
77
Users' Manual
78
79
</title>
80
81
<sect1>
82
83
84
<title>
85
86
INTRODUCTION
87
88
</title>
89
90
91
92
<para>
93
94
<application>LifeLines</application> is a genealogy program
95
that runs on <acronym>UNIX</acronym> systems. It maintains
96
genealogical records (persons, families, sources, events and
97
others) in a database, and generates reports from those
98
records. There are no practical limits on the number of
99
records that can be stored in a
100
<application>LifeLines</application> database, nor on the
101
amounts or kinds of data that can be kept in the
102
records. <application>LifeLines</application> does not contain
103
built-in reports. Instead it provides a programming subsystem
104
that you use to program your own reports and charts. The
105
programming subsystem also lets you query your databases and
106
process your data in any
107
way. <application>LifeLines</application> uses the terminal
108
independent features of <acronym>UNIX</acronym> to provide a
109
screen and menu based user interface.
110
111
</para>
112
113
114
115
<para>
116
117
<application>LifeLines</application> is a non-commercial,
118
experimental system that is use at your own risk software. I
119
developed <application>LifeLines</application> for personal
120
use and shared it with friends. Enough of a demand arose
121
through word of mouth and internet, that I have made the
122
<application>LifeLines</application> source code and other
123
information freely available under an MIT-style license
124
reproduced below:
125
126
</para>
127
128
<para>
129
<quote>
130
Copyright (c) 1991-1999 Thomas T. Wetmore IV
131
132
Permission is hereby granted, free of charge, to any person obtaining
133
a copy of this software and associated documentation files (the
134
"Software"), to deal in the Software without restriction, including
135
without limitation the rights to use, copy, modify, merge, publish,
136
distribute, sublicense, and/or sell copies of the Software, and to
137
permit persons to whom the Software is furnished to do so, subject to
138
the following conditions:
139
140
The above copyright notice and this permission notice shall be
141
included in all copies or substantial portions of the Software.
142
143
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
144
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
145
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
146
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
147
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
148
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
149
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
150
151
</quote>
152
153
</para>
154
155
<para>
156
157
The source code, documentation and a collection of report
158
scripts are located at <ulink url="http://lifelines.sourceforge.net/">
159
http://lifelines.sourceforge.net/</ulink>. You can also find
160
binary kits for some platforms. If you are a developer and
161
wish to contribute enhancements, please sign up on sourceforge
162
and contact <ulink url="mailto:marc@nozell.com"> Marc
163
Nozell</ulink> who is currently managing the project.
164
</para>
165
166
<note>
167
<para>
168
Prior to 1999, Lifelines was available on the ftp sites,
169
<ulink url="ftp://ftp.cac.psu.edu">ftp.cac.psu.edu</ulink> and
170
<ulink url="ftp://hoth.stsci.edu">hoth.stsci.edu</ulink>.
171
Please use sourceforge instead.
172
</para>
173
</note>
174
175
</sect1>
176
177
178
179
<sect1>
180
181
<title>
182
INSTALLATION
183
</title>
184
185
<para>
186
You may be installing <application>LifeLines</application>
187
from a source distribution package or as an executable program
188
already prepared for your <acronym>UNIX</acronym>
189
(or <acronym>MS-Windows</acronym>) system. The
190
source distribution comes with the readme, build script and
191
make files necessary to build
192
<application>LifeLines</application>. Follow the instructions
193
in the readme file. A number of executables are built
194
which can be put it in a
195
directory in your execution path. If you get the program in
196
executable form, follow whatever instructions came with it.
197
</para>
198
<glosslist>
199
200
<glossentry><glossterm><command>btedit</command></glossterm><glossdef>
201
<para>
202
a low-level editor for advanced debugging of broken <application>LifeLines</application> databases.
203
</para>
204
</glossdef></glossentry>
205
206
<glossentry><glossterm><command>dbverify</command></glossterm><glossdef>
207
<para>
208
a utility program to verify <application>LifeLines</application> databases.
209
</para>
210
</glossdef></glossentry>
211
212
<glossentry><glossterm><command>llexec</command></glossterm><glossdef>
213
<para>
214
a stripped down version of the
215
<application>LifeLines</application> program, without the user interface
216
for non-interactive processing of report programs
217
</para>
218
</glossdef></glossentry>
219
220
<glossentry><glossterm><command>llines</command></glossterm><glossdef>
221
<para>
222
the <application>LifeLines</application> program with full user interface
223
</para>
224
</glossdef></glossentry>
225
226
227
</glosslist>
228
229
<para>
230
The source distribution package also contains documentation
231
and some <application>LifeLines</application> programs.
232
Included with these in the reports directory is a brief overview
233
of the reports in the file index.html.
234
</para>
235
236
237
</sect1>
238
239
240
241
<sect1>
242
243
244
245
<title>
246
247
STARTING <application>LIFELINES</application> AND CREATING DATABASES
248
249
</title>
250
251
252
253
<para>
254
255
You normally start <application>LifeLines</application> with
256
the command: <userinput><command>lines</command> <replaceable class="parameter">database</replaceable></userinput> where
257
database is the name of a <application>LifeLines</application>
258
database. If <application>LifeLines</application> finds the
259
database, <application>LifeLines</application> opens the
260
database and takes you to the program's main menu. If the
261
database doesn't exist, <application>LifeLines</application>
262
asks whether it should create it, and if you answer yes, does
263
so. You may create any number of databases, but only one can
264
be accessed by <application>LifeLines</application> at a
265
time. If you built the <application>LifeLines</application>
266
executable from the source package, the executable may be
267
named <command>llines</command> rather than
268
<command>lines</command>. You may either change its name or
269
invoke <application>LifeLines</application> by using the
270
command <command>llines</command> instead.
271
272
</para>
273
274
275
276
<para>
277
278
The full command line interface to
279
<application>LifeLines</application> is:
280
281
<synopsis>
282
<command>lines</command> <option>[-acdfiklnortuwxzCFI]</option><replaceable class="parameter">[database]</replaceable>
283
</synopsis>
284
285
</para>
286
287
288
289
<para>
290
291
The following options are supported:
292
293
</para>
294
295
<informaltable pgwide='0' frame='none'>
296
<tgroup cols='2'>
297
<colspec colwidth='0.5in'></colspec>
298
<tbody>
299
300
<row>
301
<entry>-C</entry>
302
<entry>Specify configuration file location (e.g.
303
-C/home/bill/lifelines/.linesrc2 ) see the section on System and User Properties below</entry>
304
</row>
305
306
<row>
307
<entry>-F</entry>
308
<entry>Finnish option (only available if so compiled)
309
</entry>
310
</row>
311
312
<row>
313
<entry>-I</entry>
314
<entry>
315
Specify a user property (e.g. -ILLEDITOR=gvim)
316
</entry>
317
</row>
318
319
<row>
320
<entry>-a</entry>
321
<entry>log dynamic memory operation (for debugging)</entry>
322
</row>
323
324
<row>
325
<entry>-c</entry>
326
<entry>supply cache values (eg, -ci400,4000f400,4000 sets direct indi & fam
327
caches to 400, and indirect indi & fam caches to 4000)
328
</entry>
329
</row>
330
331
<row>
332
<entry>-d</entry>
333
<entry>
334
debug mode (signal protection disabled for convenience with breakpoints)
335
</entry>
336
</row>
337
338
<row>
339
<entry>-f</entry>
340
<entry>
341
force open the database - use only in emergency
342
</entry>
343
</row>
344
345
<row>
346
<entry>-i</entry>
347
<entry>
348
open database with immutable access (no protection against other
349
access -- for use on read-only media)
350
</entry>
351
</row>
352
353
<row>
354
<entry>-k</entry>
355
<entry>
356
always show keys (normally keys are suppressed if REFN available)
357
</entry>
358
</row>
359
360
<row>
361
<entry>-l</entry>
362
<entry>
363
lock (-ly) or unlock (-ln) a database for use with read only media
364
(access to a locked database is treated as immutable)
365
</entry>
366
</row>
367
368
<row>
369
<entry>-n</entry>
370
<entry>
371
do not use traditional family rules
372
</entry>
373
</row>
374
375
<row>
376
<entry>-o</entry>
377
<entry>
378
Specify program output filename (eg, -o/tmp/mytests)
379
</entry>
380
</row>
381
382
<row>
383
<entry>-r</entry>
384
<entry>
385
open database with read-only access (protect against other
386
writer access)
387
</entry>
388
</row>
389
390
<row>
391
<entry>-t</entry>
392
<entry>
393
trace function calls in report programs (for debugging)
394
</entry>
395
</row>
396
397
<row>
398
<entry>-u</entry>
399
<entry>
400
specify window size (eg, -u120,34 specifies 120 columns by 34 rows)
401
</entry>
402
</row>
403
404
<row>
405
<entry>-w</entry>
406
<entry>
407
open database with writeable access (protect against other
408
writer or reader access)
409
</entry>
410
</row>
411
412
<row>
413
<entry>-x</entry>
414
<entry>
415
execute a single lifelines report program directly
416
</entry>
417
</row>
418
419
<row>
420
<entry>-z</entry>
421
<entry>
422
Use normal ASCII characters for drawing lines in user interface rather
423
than the vt100 special characters.
424
</entry>
425
</row>
426
427
</tbody>
428
</tgroup>
429
</informaltable>
430
431
<para>
432
the <option>-o</option> option specifies the initial filename to use for
433
output when running reports. It only applies to reports run with the
434
<option>-x</option> option. This option has no effect on interactively run
435
programs.
436
</para>
437
438
<para>
439
440
The <option>-r</option> option opens the database with read-only
441
access. When in this mode
442
<application>LifeLines</application> will not let you modify
443
the database; no other operations are affected. The
444
<option>-w</option> option opens the database with writeable
445
access. If the database cannot be opened with the requested
446
mode <application>LifeLines</application> quits
447
immediately. When you open a database with neither the
448
<option>-r</option> or <option>-w</option> options,
449
<application>LifeLines</application> first tries to open the
450
database with writeable access; if not possible
451
<application>LifeLines</application> then tries to open the
452
database with read-only access; and if this is not possible
453
<application>LifeLines</application> quits. A
454
<application>LifeLines</application> database may be open
455
simultaneously by any number of programs with read-only
456
access; however, if a database is open by a program with
457
writeable access, then it cannot be opened by any other other
458
program.
459
460
</para>
461
462
463
464
<para>
465
466
In rare situations the read/write mode mechanism can fail;
467
when this happens a database may appear unopenable. If this
468
happens use the <option>-f</option> option to force open the
469
database; this will open the database and reset the mode
470
mechanism. This is a dangerous feature; you can use it to open
471
the same database with writeable access more than once; the
472
results are unpredictable and generally disastrous.
473
474
</para>
475
476
<para>
477
478
The multiuser protection supplied by this reader/writer access
479
mechanism is provided via a flag setting in the database, so both
480
read-only and writeable access actually alter the database (read-only
481
access only alters the value of this flag). For truly read-only
482
access, e.g., for use with read-only media, the best solution is to
483
lock (-ly) the database before copying it to the read-only media. This
484
annotates the database itself as being for immutable access.
485
Alternatively, to use a database already on read-only media and not
486
so annotated, use the immutable (-i) flag.
487
488
</para>
489
490
<para>
491
By default lifelines supports a traditional family concept, that is, each
492
family has at most one father and one mother. The -n flag relaxes this
493
restriction. However, not all the code in lifelines supports these
494
relaxations. For example, the default family browse screen will only display
495
two parents, however by switching to one of the gedcom modes of displaying the
496
family you can see all the data.
497
</para>
498
499
<para>
500
501
If you don't give the name of a database on the command line,
502
<application>LifeLines</application> will prompt you for
503
it. If the name you supply is an absolute pathname or a
504
relative pathname it is used as the path to the database.
505
If you provided a simple filename and you use the
506
<envar>LLDATABASES</envar> variable or user options (described later),
507
<application>LifeLines</application> will search for the
508
database in the directories named in the variable; this can be
509
very convenient.
510
If <envar>LLDATABASES</envar> is not set
511
the filename you enter is looked for in the current working directory.
512
513
</para>
514
515
<para>
516
517
If you would like to choose a database from a list of existing ones,
518
enter a single question mark and press return when
519
<application>LifeLines</application> prompts you for the database name.
520
<application>LifeLines</application> will then display a list of all
521
databases that it can find, and you may select one from the list.
522
523
</para>
524
525
526
</sect1>
527
528
529
530
<sect1>
531
532
533
534
<title>
535
536
INTRODUCTION TO <acronym>GEDCOM</acronym>
537
538
</title>
539
540
541
542
<para>
543
544
<application>LifeLines</application> records are stored in
545
<acronym>GEDCOM</acronym> format; you organize, edit and
546
maintain your data in this format. <acronym>GEDCOM</acronym>
547
is a standard that defines a file format for moving
548
genealogical data between computer
549
systems. <application>LifeLines</application> has adopted this
550
format for structuring the records in its databases. This
551
approach provides a structured yet flexible method for storing
552
all the data you wish to record. There are few restrictions on
553
the format, amount or type of information you may store in a
554
<application>LifeLines</application> database.
555
556
</para>
557
558
559
560
<para>
561
562
<acronym>GEDCOM</acronym> is defined at two levels. At the
563
syntactic level <acronym>GEDCOM</acronym> is a simple set of
564
rules for organizing and structuring data into records, with
565
no concern about the types of records, types or formats of
566
information in the records, or the relationships between
567
records. At the semantic level <acronym>GEDCOM</acronym> adds
568
an additional set of rules that specify what record types are
569
allowed, how records must be structured, how data within the
570
records must be identified and formatted, and what specific
571
relationships between the record types are allowed. In
572
principle there can be multiple semantic versions of
573
<acronym>GEDCOM</acronym>, though in practice there is only
574
one, lineage-linked <acronym>GEDCOM</acronym>. Unfortunately
575
this semantic version of <acronym>GEDCOM</acronym> is poorly
576
defined, and every genealogical system has interpreted it in
577
different ways.
578
579
</para>
580
581
582
583
<para>
584
585
<application>LifeLines</application> uses
586
<acronym>GEDCOM</acronym> primarily at the syntactic level,
587
though it does impose a few of the generally accepted
588
lineage-linked semantic restrictions. This means some
589
important things. It means that you can store all your
590
genealogical data in your <application>LifeLines</application>
591
database, and that you have wide freedom in how you choose
592
your own conventions for structuring and formatting your
593
data. But it also means that the way you store data in your
594
databases can be different from the way that someone else
595
stores their data. This can be a problem if you share data
596
with others or share report programs with other
597
<application>LifeLines</application> users. My recommendation
598
is to use <acronym>GEDCOM</acronym> lineage-linking
599
conventions wherever possible.
600
601
</para>
602
603
604
605
<para>
606
607
<application>LifeLines</application> does not use forms or
608
screens to guide you through entering or changing
609
data. Instead you use a screen editor and directly edit the
610
data records. This requires you to understand the
611
<acronym>GEDCOM</acronym> format, and be able to edit data in
612
<acronym>GEDCOM</acronym> format, before you can use
613
<application>LifeLines</application>. The
614
<acronym>GEDCOM</acronym> format is quite simple; this
615
introduction will provide all you need to know about
616
<acronym>GEDCOM</acronym> in order to use
617
<application>LifeLines</application>.
618
619
</para>
620
621
622
623
<para>
624
625
Here is an example <acronym>GEDCOM</acronym> person record:
626
627
<example>
628
629
<title>
630
631
<acronym>GEDCOM</acronym> person record
632
633
</title>
634
635
<programlisting role="gedcom">
636
0 @I25@ INDI
637
1 NAME <userinput>Thomas Trask /Wetmore/ Sr</userinput>
638
1 SEX <userinput>M</userinput>
639
1 BIRT
640
2 DATE <userinput>13 March 1866</userinput>
641
2 PLAC <userinput>St. Mary's Bay, Digby, Nova Scotia</userinput>
642
2 SOUR <userinput>Social Security application</userinput>
643
1 NATU
644
2 NAME <userinput>Thomas T. Wetmore</userinput>
645
2 DATE <userinput>26 October 1888</userinput>
646
2 PLAC <userinput>Norwich, New London, Connecticut</userinput>
647
2 AGE <userinput>22 years</userinput>
648
2 COUR <userinput>New London County Court of Common Pleas</userinput>
649
2 SOUR <userinput>court record from National Archives</userinput>
650
1 OCCU <userinput>Antiques Dealer</userinput>
651
1 DEAT
652
2 NAME <userinput>Thomas Trask Wetmore</userinput>
653
2 DATE <userinput>17 February 1947</userinput>
654
2 PLAC <userinput>New London, New London, Connecticut</userinput>
655
2 AGE <userinput>80 years, 11 months, 4 days</userinput>
656
2 CAUS <userinput>Heart Attack</userinput>
657
2 SOUR <userinput>New London Death Records</userinput>
658
1 FAMC @F11@
659
1 FAMS @F6@
660
1 FAMS @F12@
661
662
</programlisting></example>
663
664
</para>
665
666
667
668
<para>
669
670
A <acronym>GEDCOM</acronym> record is made up of lines. Each
671
line has a level number and a tag, and most lines have a value
672
following the tag. The first line in every record has a
673
cross-reference index between the level number and the tag.
674
675
</para>
676
677
678
679
<para>
680
681
Level numbers allow data to be structured to any degree of
682
detail; lines with higher level numbers expand on lines with
683
lower numbers. Each record begins at level 0, and each deeper
684
level increments the level by
685
one. <application>LifeLines</application> does not restrict
686
the structuring depth. Tags are uppercase (by convention) code
687
words that specify the kind of information on the line or on
688
the higher numbered lines that follow. The information after
689
the tag, if any, is the value of the line.
690
691
</para>
692
693
694
695
<para>
696
697
The first line in a record indicates its type. There are four
698
fixed record types in <application>LifeLines</application>
699
databases: person, family, source and event. The first, 0
700
level line in these records have tags
701
<structname>INDI</structname>, <structname>FAM</structname>,
702
<structname>SOUR</structname> and
703
<structname>EVEN</structname>, respectively. Besides these
704
record types, you may create your own record types by using
705
any other tag on the 0 level line of a record. The lines that
706
begin records are the only level 0 lines used in
707
<application>LifeLines</application>. Each level 0 line has a
708
cross-reference index between the level number and the
709
tag. This index is the record's internal reference key; other
710
records may refer to this record by using this index.
711
Cross-reference indexes are bracketed by @ characters.
712
713
</para>
714
715
716
717
<para>
718
719
The first line in the example record has the
720
<structname>INDI</structname> tag, identifying it as a
721
person. The cross-reference index value, I25, can be used by
722
other records to refer to this record.
723
724
</para>
725
726
727
728
<para>
729
730
The second line in the example has the person's name. Each
731
person record in a <application>LifeLines</application>
732
database must have at least one <structfield>1
733
NAME</structfield> line, and its value must be in
734
<acronym>GEDCOM</acronym> name format. This format allows
735
names to be as long as needed, but the surname, which may be
736
placed anywhere in the name, must be separated from the rest
737
of the name by one or two slashes. For example:
738
739
<example>
740
741
<title>
742
Example of NAME formats
743
744
</title>
745
746
<programlisting>
747
1 NAME <userinput>John/Smith</userinput>
748
1 NAME <userinput>John /Smith/</userinput>
749
1 NAME <userinput>John/Smith/Jr.</userinput>
750
</programlisting>
751
</example>
752
753
</para>
754
755
756
757
<para>
758
759
The second slash is required only if name elements follow the
760
surname. White space is optional before the first slash and
761
after the second. If you don't know a person's surname, or the
762
person doesn't have a surname, you may use / or // or no
763
slashes at all. For example:
764
765
<example>
766
767
<title>
768
Example of searching on NAMEs
769
</title>
770
771
<programlisting>
772
773
1 NAME <userinput>Mary//</userinput>
774
1 NAME <userinput>Mary/</userinput>
775
1 NAME <userinput>Mary</userinput>
776
</programlisting>
777
778
</example>
779
780
are all ways to enter a person named Mary with no known
781
surname. A person may have any number, including zero, given
782
names and/or initials. A <application>LifeLines</application>
783
person record may have any number of <structfield>1
784
NAME</structfield> lines, though the person will be displayed
785
with the first name value only. Persons are indexed under all
786
their names, however, so you will be able to search for
787
persons by any of their names.
788
</para>
789
790
791
792
<para>
793
794
The next line in the example gives the person's
795
sex. <application>LifeLines</application> doesn't require a
796
<structfield>1 SEX</structfield> line, but you should include
797
it. The value of the line should be <userinput>M</userinput>
798
or <userinput>F</userinput> if the sex is known; it can be
799
left blank or set to <userinput>U</userinput> or
800
<userinput>?</userinput>, say, if not known. A person must
801
have a <structfield>1 SEX</structfield> line with a value of
802
either <userinput>M</userinput> or <userinput>F</userinput>
803
before he or she can be made a spouse or parent in a family.
804
805
</para>
806
807
808
809
<para>
810
811
The example record also contains three events: birth,
812
naturalization, and death. An event begins with a level 1 line
813
whose tag indicates the event type. For example,
814
<structfield>BIRT</structfield> is the tag for a birth event.
815
816
</para>
817
818
819
820
<para>
821
822
Events usually have at least a <structfield>2
823
DATE</structfield> and a <structfield>2 PLAC</structfield>
824
line and often a <structfield>2 SOUR</structfield> line. The
825
<structfield>DATE</structfield> and
826
<structfield>PLAC</structfield> lines give the date and place
827
of the event. The value of a
828
<application>LifeLines</application>
829
<structfield>DATE</structfield> line is free format, though
830
<application>LifeLines</application> will try to parse it for
831
specific day, month and year information. The value of a
832
<structfield>PLAC</structfield> line is usually a
833
comma-separated list of geopolitical units, starting with the
834
most specific, ending with the most general. The
835
<structfield>SOUR</structfield> line indicates the source of
836
information about the event. The
837
<structfield>SOUR</structfield> line can be the root of a full
838
description of the source, or the value of the
839
<structfield>SOUR</structfield> line can be a cross-reference
840
key that refers to the source record that describes the
841
source.
842
843
</para>
844
845
846
847
<para>
848
849
The naturalization event (with tag
850
<structfield>NATU</structfield>) shows a few other lines. The
851
<structfield>2 NAME</structfield> line gives the person's name
852
as recorded in the source (only <structfield>1
853
NAME</structfield> lines must follow <acronym>GEDCOM</acronym>
854
format). The <structfield>2 AGE</structfield> line gives the
855
person's age at the time of the event. The <structfield>2
856
COUR</structfield> line indicates the court where
857
naturalization occurred.
858
859
</para>
860
861
862
863
<para>
864
865
The final event is a death event (tag
866
<structfield>DEAT</structfield>). The <structfield>2
867
CAUS</structfield> line gives the cause of death.
868
869
</para>
870
871
872
873
<para>
874
875
At the end of the record are three lines that refer to family
876
records. A <structfield>1 FAMC</structfield> line refers to a
877
family record that the person belongs to as a child; its value
878
is the cross-reference index value of that family. A
879
<structfield>1 FAMS</structfield> line refers to a family
880
record that the person belongs to as a spouse or parent.
881
882
</para>
883
884
885
886
<para>
887
888
When using <application>LifeLines</application> to edit a
889
person, you will not be able to edit the cross reference
890
values on the <structfield>0 INDI</structfield>,
891
<structfield>1 FAMC</structfield> or <structfield>1
892
FAMS</structfield> lines; these are maintained by
893
<application>LifeLines</application>.
894
895
</para>
896
897
898
899
<para>
900
901
Here is an example family record:
902
903
<example>
904
905
<title>
906
Example family record
907
</title>
908
909
<programlisting>
910
911
0 @F6@ FAM
912
1 HUSB @I25@
913
1 WIFE @I26@
914
1 MARR
915
2 DATE <userinput>31 March 1891</userinput>
916
2 PLAC <userinput>New London, New London, Connecticut</userinput>
917
2 SOUR <userinput>New London Vital Records</userinput>
918
1 CHIL @I27@
919
1 CHIL @I17@</programlisting></example>
920
921
</para>
922
923
924
925
<para>
926
927
The <structfield>0 FAM</structfield> line assigns the family
928
the cross-reference index of F6. The record contains
929
<structfield>1 HUSB</structfield> and <structfield>1
930
WIFE</structfield> lines that refer to the two
931
spouses/parents. The record also holds a marriage event (tag
932
<structfield>MARR</structfield>) and two <structfield>1
933
CHIL</structfield> lines that refer to two children in the
934
family. When editing family records, you cannot edit the
935
<structfield>0 FAM</structfield>, <structfield>1
936
HUSB</structfield>, <structfield>1 WIFE</structfield>, or
937
<structfield>1 CHIL</structfield> lines; these are maintained
938
by <application>LifeLines</application>.
939
940
</para>
941
942
<para>
943
944
When you create new records for your database, you are free to
945
invent tags and structure your data in any way you see
946
fit. However, it is good practice to use standard
947
<acronym>GEDCOM</acronym> tags and value formats.
948
<application>LifeLines</application> does enforce a small set
949
of conventions that you must obey. Within person records,
950
<application>LifeLines</application> requires that you use
951
<structfield>1 NAME</structfield> and <structfield>1
952
SEX</structfield> lines with their special meanings and value
953
formats. Though not required,
954
<application>LifeLines</application> assumes that you will use
955
<structfield>1 BIRT</structfield>, <structfield>1
956
DEAT</structfield>, <structfield>1 CHR</structfield>, and
957
<structfield>1 BURI</structfield> lines for birth, death,
958
baptism and burial events, respectively. In family records,
959
<application>LifeLines</application> assumes you will use the
960
<structfield>1 MARR</structfield> event for marriage
961
events. Within person records, you are not allowed to use
962
<structfield>0 INDI</structfield>, <structfield>1
963
FAMC</structfield> or <structfield>1 FAMS</structfield> lines,
964
since these are used to maintain linkage information. Within
965
family records, you are not allowed to use <structfield>0
966
FAM</structfield>, <structfield>1 HUSB</structfield>,
967
<structfield>1 WIFE</structfield> or <structfield>1
968
CHIL</structfield> lines.
969
970
</para>
971
972
973
974
<para>
975
976
The indentation shown in the examples is not part of
977
<acronym>GEDCOM</acronym> format. When
978
<application>LifeLines</application> prepares records for you
979
to edit, however, it always indents the records, making them
980
easier to read and understand. You do not need to follow this
981
indentation scheme when you edit the records. Indentation is
982
removed from the data before it is stored in the database.
983
984
</para>
985
986
987
988
</sect1>
989
990
991
992
<sect1>
993
994
995
996
<title>
997
998
MAIN MENU
999
1000
</title>
1001
1002
1003
1004
<para>
1005
1006
After <application>LifeLines</application> opens an existing
1007
database, or creates a new one, it presents you with the main
1008
menu:
1009
1010
<screen>
1011
Please choose an operation:
1012
b Browse the persons in the database
1013
s Search database
1014
a Add information to the database
1015
d Delete information from the database
1016
p Pick a report from list and run
1017
r Generate report by entering report name
1018
t Modify character translation tables
1019
u Miscellaneous utilities
1020
x Handle source, event and other records
1021
Q Quit current database
1022
q Quit program
1023
</screen>
1024
1025
1026
</para>
1027
1028
<para>
1029
1030
Select an operation by striking the proper selection letter.
1031
1032
</para>
1033
1034
1035
1036
<para>
1037
1038
The browse operation lets you browse the database and perform
1039
many operations on the data. The search operation provides some
1040
simple wildcard search capabilities, which lead into browsing
1041
particular records. The add operation lets you add
1042
new information, and the delete operation removes
1043
information. The report operations read report
1044
programs and generates output reports. The modify character
1045
translation tables operation changes the translation
1046
tables. The miscellaneous utilities operation provides such
1047
things as backup and restore. The handle source, event and
1048
other records operation gives you access to these three record
1049
types. The quit operation closes the database and returns to
1050
<acronym>UNIX</acronym>.
1051
1052
</para>
1053
1054
1055
1056
<para>
1057
1058
The browse operation deserves special mention, because it
1059
provides a rich environment for searching, viewing, adding,
1060
modifying, merging and deleting information in the
1061
database. You will find that you operate from the browsing
1062
modes most of the time. The operations are all described in
1063
later sections.
1064
1065
</para>
1066
1067
1068
1069
</sect1>
1070
1071
1072
1073
<sect1>
1074
1075
1076
1077
<title>
1078
1079
CODESET
1080
1081
</title>
1082
1083
<para>
1084
1085
After you have created a new database, and before you actually
1086
add any data to it, is the time to set the codeset to be used
1087
in the database.
1088
1089
</para>
1090
1091
<para>
1092
1093
The codeset (or character encoding, to use precise Unicode
1094
terminology) is the decision as to how letters will be represented
1095
by the computer. If you have only ever used English letters in
1096
computing, you may not have had to encounter this issue, because as
1097
it happens, the English letters (a-z and A-Z) are stored numerically
1098
in the same fashion in almost all codesets used by computers. However,
1099
in the field of genealogy, you are especially likely to meet letters
1100
outside of the English alphabet (for example, accented vowels).
1101
1102
</para>
1103
1104
<para>
1105
1106
You have fundamentally three choices as to what codeset to use in your
1107
database, listed below from easiest to most powerful.
1108
1109
</para>
1110
1111
<para>
1112
1113
First, you may leave it entirely unspecified. This will give the
1114
traditional lifelines behavior. This is really only suitable if either
1115
(a), you only use English (ASCII) data, or (b), you work in an
1116
environment which entirely uses the same 8-bit codeset (eg, a GNU/Linux box
1117
which is all ISO-8859-15), and you only run lifelines in English.
1118
If you use any non-English data on MS-Windows, this is not likely to
1119
be suitable, because the lifelines screens run in the console, but
1120
you are likely to use MS-Windows applications either for editing or
1121
for viewing output, and the MS-Windows console uses a different
1122
codeset from MS-Windows applications. Also, if you use lifelines in a
1123
different language than English, this may not be suitable, because
1124
the gettext message catalogs (for non-English interface) will not
1125
be converted into your codeset.
1126
1127
</para>
1128
1129
<para>
1130
1131
Second, you may specify a particular 8-bit codeset. Assuming that you
1132
have iconv and gettext installed (or you are using the MS-Windows version,
1133
which comes with these), you may specify any 8-bit codeset supported by
1134
iconv, and iconv supports quite many. A natural choice for Western European
1135
languages would be ISO-8859-1, or (for MS-Windows only) CP-1252. With this
1136
option, gettext language files will be converted to your codeset.
1137
1138
</para>
1139
1140
<para>
1141
1142
Third, you may specify the use of UTF-8. This is a Unicode encoding, and
1143
is by far the most powerful option. In fact, this is the only really
1144
convenient way to be able to store, for example, names in English, names
1145
in Russian, and names in Greek, all in the same database, in their native
1146
scripts (alphabets). In recent versions, lifelines has become more
1147
knowledgeable about handling UTF-8, so that, for example, upper &
1148
lower casing only work correctly with versions from 3.0.28 on.
1149
1150
</para>
1151
1152
<para>
1153
1154
To actually specify a codeset, enter it via the u(tility) o(ptions) page
1155
(which is documented below). From the main menu, in the English version,
1156
press u to reach the utility page, and then o to edit the user options. To
1157
set a codeset of, e.g., ISO-8859-1, enter this string on its own line,
1158
without the surrounding quotes: "codeset=ISO-8859-1". Or, to specify the
1159
use of UTF-8, "codeset=UTF-8".
1160
1161
</para>
1162
1163
<para>
1164
1165
Further information about codeset conversion is found in the later chapter
1166
of that name (for example, information about producing reports which make
1167
use of HTML entity names for non-ASCII characters).
1168
1169
</para>
1170
1171
</sect1>
1172
1173
1174
1175
<sect1>
1176
1177
1178
1179
<title>
1180
1181
ENTERING THE FIRST PERSON
1182
1183
</title>
1184
1185
<para>
1186
1187
Note: Before you add the first person to your database, you
1188
specify internal codeset (review the Codeset chapter for
1189
information).
1190
1191
</para>
1192
1193
<para>
1194
1195
Normally you add persons to the database from the browsing
1196
modes, but when entering the first person there is no one in
1197
the database to browse to. To add the first person to a
1198
<application>LifeLines</application> database, first select
1199
the add operation from the main menu. You will be prompted
1200
with the add menu (described later). Strike p to add a
1201
person. <application>LifeLines</application> creates a
1202
template of a <acronym>GEDCOM</acronym> person record, and
1203
puts you in a screen editor to edit the template. The default
1204
template is:
1205
1206
<example>
1207
<title>
1208
Default person record template
1209
</title>
1210
1211
<programlisting>
1212
1213
0 INDI
1214
1 NAME <replaceable>Fname /Surname/</replaceable>
1215
1 SEX <replaceable>MF</replaceable>
1216
1 BIRT
1217
2 DATE
1218
2 PLAC
1219
2 SOUR
1220
1 DEAT
1221
2 DATE
1222
2 PLAC
1223
2 SOUR</programlisting></example>
1224
1225
</para>
1226
1227
1228
1229
<para>
1230
1231
Edit the template to create the new person's record. Change
1232
the name to the person's name. Assign the person's sex by
1233
deleting either <userinput>M</userinput> or
1234
<userinput>F</userinput>. Fill out the birth and death events
1235
as best you can. If the person is alive, remove the death
1236
event. Remove any <structfield>DATE</structfield> and
1237
<structfield>PLAC</structfield> lines you do not have the
1238
information for.
1239
1240
</para>
1241
1242
1243
1244
<para>
1245
1246
The default template provides lines for one birth and one
1247
death event. You can expand the record with other events (even
1248
more birth or death events) and lines. Indentation makes it
1249
easier to read and edit the record, but isn't necessary. You
1250
may change the default edit template by defining the user
1251
option <option>INDIREC</option> (described later).
1252
1253
</para>
1254
1255
1256
1257
<para>
1258
1259
Here is how I might edit the template when creating a record
1260
about myself:
1261
1262
<example>
1263
1264
<title>
1265
Example editing of template record
1266
</title>
1267
1268
<programlisting>
1269
1270
0 INDI
1271
1 NAME <userinput>Thomas Trask /Wetmore/ IV</userinput>
1272
1 SEX <userinput>M</userinput>
1273
1 BIRT
1274
2 DATE <userinput>18 December 1949</userinput>
1275
2 PLAC <userinput>New London, New London, Connecticut</userinput>
1276
2 SOUR <userinput>Birth Certificate</userinput>
1277
1 OCCU <userinput>Software Engineer</userinput>
1278
1 RESI
1279
2 DATE <userinput>1982 to 1995</userinput>
1280
2 PLAC <userinput>Newburyport, Essex, Massachusetts</userinput>
1281
2 ADDR <userinput>2 Barton Street, Newburyport, MA 01950</userinput>
1282
1283
... lots of other events and facts
1284
</programlisting>
1285
</example>
1286
1287
</para>
1288
1289
1290
1291
<para>
1292
1293
When you edit a person record, don't add or modify
1294
<structfield>INDI</structfield>,
1295
<structfield>FAMC</structfield> or
1296
<structfield>FAMS</structfield>
1297
lines. <application>LifeLines</application> creates and
1298
maintains these lines through specific user commands.
1299
1300
</para>
1301
1302
1303
1304
<para>
1305
1306
When you finish editing and leave the editor, you
1307
automatically return to
1308
<application>LifeLines</application>. If you made an error
1309
(eg, didn't use proper level numbers or didn't follow the
1310
proper name convention), <application>LifeLines</application>
1311
displays an error message, and asks if you want to re-edit the
1312
record. If you don't, <application>LifeLines</application>
1313
doesn't add the person to the database.
1314
1315
</para>
1316
1317
1318
1319
<para>
1320
1321
When the record is in proper format,
1322
<application>LifeLines</application> asks if you are sure you
1323
want to add the person to the database. If you answer yes, the
1324
person is added; if you answer no, the person isn't. In both
1325
cases <application>LifeLines</application> returns to the main
1326
menu.
1327
1328
</para>
1329
1330
1331
1332
</sect1>
1333
1334
1335
1336
<sect1>
1337
1338
1339
1340
<title>
1341
1342
SCREEN EDITORS AND ENVIRONMENT VARIABLES
1343
1344
</title>
1345
1346
1347
1348
<para>
1349
1350
With <application>LifeLines</application> you maintain the
1351
database records using a screen editor. This is different than
1352
other genealogical programs where screens or forms are used to
1353
gather the data.The default screen editor for
1354
<application>LifeLines</application> is
1355
<application>vi</application>. (The <acronym>MS-Windows</acronym>
1356
version defaults instead to notepad.exe.) This can be overridden by the
1357
<envar>ED</envar>, <envar>EDITOR</envar> or
1358
<envar>LLEDITOR</envar> environment variables. For example, if
1359
you prefer the emacs screen editor, and if you use a bourne-compatible
1360
shell, you may add the line:
1361
<userinput><envar>ED</envar>=<replaceable>emacs</replaceable></userinput>
1362
to your login profile file, and
1363
<application>LifeLines</application> will use
1364
<application>emacs</application> for editing.
1365
1366
</para>
1367
1368
1369
1370
<para>
1371
1372
There are four other, <application>LifeLines</application>
1373
specific environment variables. They are
1374
<envar>LLDATABASES</envar>, <envar>LLARCHIVES</envar>,
1375
<envar>LLPROGRAMS</envar> and <envar>LLREPORTS</envar>.
1376
<envar>LLDATABASES</envar> and
1377
<envar>LLPROGRAMS</envar> are <acronym>UNIX</acronym> path
1378
list variables.
1379
1380
</para>
1381
1382
<para>
1383
There is also a configuration file, and
1384
entries in it may be used in lieu of environment variables.
1385
It is ordinarily named .linesrc under <acronym>UNIX</acronym>,
1386
and lines.cfg under <acronym>MS-Windows</acronym>.
1387
A sample configuration file should have been included
1388
in the distribution.
1389
</para>
1390
1391
<para>
1392
See the section on System and User properties
1393
for more details.
1394
</para>
1395
1396
<para>
1397
1398
<envar>LLDATABASES</envar> can be set to a list of directories
1399
that hold <application>LifeLines</application> databases. When
1400
you execute the <application>LifeLines</application> program,
1401
these directories will be searched in turn for the database
1402
mentioned on the command line. For example,
1403
<userinput><envar>LLDATABASES</envar>=<replaceable>.:/home/ttw4/LifeLines/Databases</replaceable></userinput>
1404
indicates that databases should be searched for in the current
1405
directory first, and if not found there, then searched for in:
1406
<filename>/home/ttw4/LifeLines/Databases</filename>
1407
1408
</para>
1409
1410
1411
1412
<para>
1413
1414
Each <application>LifeLines</application> database is
1415
implemented as a directory with specific contents. The
1416
<envar>LLDATABASES</envar> variable should be set to a list of
1417
directories that contain these database directories, not to a
1418
list of database directories themselves.
1419
1420
</para>
1421
1422
1423
1424
<para>
1425
1426
The environment variable <envar>LLPROGRAMS</envar> is used in
1427
the same way, but to specify the search path for
1428
<application>LifeLines</application> report generating and
1429
other programs (described later).
1430
1431
</para>
1432
1433
1434
1435
<para>
1436
1437
<envar>LLARCHIVES</envar> and <envar>LLREPORTS</envar> can
1438
each be set to specify a single
1439
directory. <envar>LLARCHIVES</envar> is used to select a
1440
directory where all database backup files will be stored, and
1441
<envar>LLREPORTS</envar> is used to select a directory where
1442
all generated reports and program outputs will be placed.
1443
1444
</para>
1445
1446
<para>
1447
1448
New databases without explicit paths will be created in the
1449
first directory listed in the LLDATABASES path. (This is a
1450
change; versions from 3.0.6 to 3.0.31 used a now obsolete
1451
variable LLNEWDBDIR).
1452
1453
</para>
1454
1455
<para>
1456
1457
You are not required to use these environment variables; when
1458
a variable is not defined,
1459
<application>LifeLines</application> uses the current
1460
directory as its default value. If you do use the variables,
1461
you can override their use by specifying files and directories
1462
as either absolute or relative paths.
1463
1464
</para>
1465
1466
<para>
1467
1468
You may use the configuration file in
1469
lieu of environment variables. This is especially oriented towards
1470
users on <acronym>MS-Windows</acronym> systems, on which
1471
environment variables are not as common a configuration technique.
1472
1473
</para>
1474
1475
1476
<para>
1477
1478
<application>LifeLines</application> uses the curses library
1479
for terminal independent I/O. This requires you to specify
1480
your terminal type with the <envar>TERM</envar> environment
1481
variable. (This is not relevant in the <acronym>MS-Windows</acronym>
1482
version.)
1483
1484
</para>
1485
1486
1487
1488
</sect1>
1489
1490
1491
1492
<sect1>
1493
1494
1495
1496
<title>
1497
1498
BASICS OF BROWSING
1499
1500
</title>
1501
1502
1503
1504
<para>
1505
1506
You will use the browsing screens of
1507
<application>LifeLines</application> most of the time. When in
1508
these modes you can quickly search for or browse through the
1509
persons and families in the database. When you find a person
1510
or family you are interested in, you can then edit their
1511
records.
1512
1513
</para>
1514
1515
1516
1517
<para>
1518
The browsing screens also allow you to add new persons and
1519
families to the database, add spouses to families, add
1520
children to families, swap the order of spouses and children,
1521
merge persons and merge families, and perform other
1522
operations. The browsing screens also lets you remove spouses
1523
from families and remove children from families.
1524
</para>
1525
1526
<para>
1527
There are six browsing screens. The person and family screens
1528
concentrate on a single person and family, respectively. The
1529
list screen allows you to browse through a list of persons. The
1530
two person browse screen shows two persons at once, and the
1531
two family browse screen shows two families at once. The
1532
auxiliary screen is used browsing any other type of records
1533
(e.g., events, sources, notes).
1534
1535
</para>
1536
1537
<para>
1538
Each browsing screen has multiple
1539
view modes. The view mode affects how the information is displayed
1540
on the screen, but does not affect the menu choices available at
1541
the bottom of the screen. Menu commands are available on each screen
1542
to change amongst the view modes available for that screen.
1543
</para>
1544
1545
<para>
1546
The person screen has the most view modes. It has normal mode,
1547
which shows a summary of the vital records of the person. It (like
1548
all other screens) has GEDCOM mode, which shows the actual GEDCOM
1549
data of the record, and also expanded GEDCOM mode, which shows the
1550
actual GEDCOM data, but augments it with information on each line
1551
that contains a cross-reference (GEDCOM xref). It has two pedigree
1552
or tree modes, one showing an ancestral tree and one showing a
1553
descendant tree. The depth of the pedigree trees shown may be
1554
adjusted via menu commands.
1555
</para>
1556
1557
<para>
1558
The two person browse screen has the same modes as the person
1559
screen.
1560
</para>
1561
1562
<para>
1563
The two family browse screen and tandem family screen alike have
1564
normal mode (showing a summary of vitals), GEDCOM mode, and
1565
expanded GEDCOM mode.
1566
</para>
1567
1568
<para>
1569
The auxiliary screen has only GEDCOM mode and expanded GEDCOM mode.
1570
(The list screen has no view modes at present).
1571
</para>
1572
1573
</sect1>
1574
1575
1576
1577
<sect1>
1578
1579
1580
1581
<title>
1582
1583
IDENTIFYING A PERSON OR LIST OF PERSONS TO BROWSE
1584
1585
</title>
1586
1587
1588
1589
<para>
1590
1591
To enter the browsing modes from the main menu strike
1592
b. <application>LifeLines</application> asks you to identify a
1593
person or list of persons to browse to:
1594
1595
<screen>
1596
Please identify person or persons to browse to.
1597
Enter name, key, refn or list:
1598
</screen>
1599
1600
</para>
1601
1602
<para>
1603
1604
Enter either a name or partial name, or an internal key value,
1605
or a user-defined reference key (described later) or the name
1606
of a previously defined list of persons (described later), and
1607
strike return.
1608
1609
</para>
1610
1611
1612
1613
<para>
1614
1615
<application>LifeLines</application> allows wide flexibility
1616
in how to enter names. You may enter a name in upper or lower
1617
case or any combination. You may leave out all but the first
1618
given name, and, for given names, you may leave out any
1619
letters except the first. You may leave vowels out of the
1620
surname, and after four or five consonants have been typed,
1621
you may leave them out too. You must separate the given names
1622
from the surname by a slash, and if you enter given names
1623
after the surname (as in Chinese names), or any modifiers
1624
(such as Jr, Sr, IV, etc.), they must be separated from the
1625
surname by another slash. Here are a few of the ways I can
1626
enter my name:
1627
1628
<example>
1629
1630
<title>
1631
Example of entering a name
1632
</title>
1633
1634
<literallayout>
1635
Thomas Trask /Wetmore/ IV
1636
thomas/wetmore/iv
1637
t t/wetmr/i
1638
th tr/Wetmore
1639
t/wtmr/iv
1640
</literallayout>
1641
</example>
1642
1643
</para>
1644
1645
1646
1647
<para>
1648
1649
You may browse to the list of all persons with the same
1650
surname by using the * character as the first initial. For
1651
example:
1652
1653
<example>
1654
1655
<title>
1656
Example of using wildcard in browsing
1657
</title>
1658
1659
<literallayout>*/wetmore</literallayout></example>matches all
1660
persons with surname Wetmore. This is the only wildcard
1661
feature supported in browsing. (However, the search operation
1662
provides some simple wildcards for
1663
finding individual name fragments, or searching by user-defined
1664
reference keys. The search operation is accessed via a different
1665
choice off of the main menu.)
1666
1667
</para>
1668
1669
1670
1671
<para>
1672
1673
After you enter a name, <application>LifeLines</application>
1674
searches for all persons who match. There are three
1675
possibilities: no one matches; one person matches; or more
1676
than one person matches. In the first case
1677
<application>LifeLines</application> writes:
1678
<screen>There is no one in the database with that name or key.</screen>
1679
and leaves you in the main menu.
1680
1681
</para>
1682
1683
1684
1685
<para>
1686
1687
If one person matches, <application>LifeLines</application>
1688
enters the person browse mode displaying the matched
1689
person. If more than one person matches,
1690
<application>LifeLines</application> enters the list browsing
1691
mode with the list of matching persons.
1692
1693
</para>
1694
1695
1696
1697
<para>
1698
1699
You may also identify a person by entering his or her
1700
internal, cross-reference key value. The internal key values
1701
of all person records are an I followed by digits.
1702
When you enter a key value you may omit the I.
1703
If <application>LifeLines</application> finds a person with
1704
the key value you provide,
1705
<application>LifeLines</application> enters the person
1706
browsing mode displaying that person. You can also browse to
1707
a Family, Source, or Note by entering it's key, but you must
1708
include the letter identifing the key type, thus F11, S1, or N3
1709
would browse to the family, source or note corresponding to the key
1710
if it exists.
1711
1712
</para>
1713
1714
<para>
1715
1716
The browse command b is also available from most browsing
1717
modes. The command works the same way from those modes as it
1718
does from the main menu.
1719
1720
</para>
1721
1722
1723
1724
</sect1>
1725
1726
1727
1728
<sect1>
1729
1730
1731
1732
<title>
1733
1734
ZIP IDENTIFYING A NEW PERSON
1735
1736
</title>
1737
1738
1739
1740
<para>
1741
1742
Some <application>LifeLines</application> operations need you
1743
to identify a person, not for the purpose of browsing, but for
1744
the purpose of completing an operation you have requested. For
1745
example, when you add a child to a family,
1746
<application>LifeLines</application> may ask you to identify
1747
the child. When this happens a panel pops up that asks you to
1748
identify a person. You respond by typing a name or key exactly
1749
as you would for the b command. If no one matches,
1750
<application>LifeLines</application> returns to the previous
1751
browsing mode. If the name matches persons in the database
1752
<application>LifeLines</application> displays something like:
1753
1754
<screen>
1755
Please choose from among these records.
1756
>Thomas Trask Wetmore, b. 1826, N.B. (42)
1757
Thomas Trask Wetmore IV, b. 1949, Conn. (1)
1758
Thomas Trask Wetmore III, b. 1925, Conn. (6)
1759
Thomas Trask Wetmore Jr, b. 1896, Conn. (11)
1760
Thomas Trask Wetmore Sr, b. 1866, N.S. (23)
1761
Thomas Trask Wetmore V, b. 1982, Mass. (5)
1762
_______________________________________________
1763
Commands: j Move down k Move up i Select q Quit
1764
</screen>
1765
1766
1767
</para>
1768
1769
1770
1771
<para>
1772
1773
Use the j and k commands to move the selection cursor (>) to
1774
the correct person, and then use the i command to select that
1775
person. There may be more persons in the list than you can see
1776
at once. If this is so then you can use the j and k commands
1777
to scroll through the full list. If you don't find the proper
1778
person, use the q command and
1779
<application>LifeLines</application> asks whether you want to
1780
enter another name.
1781
1782
</para>
1783
1784
<para>
1785
1786
With version 3.0.15, lists may also be navigated with the up
1787
and down arrows, PageUp and PageDown keys, Home and End keys, and
1788
the Enter key. Shift-PageUp and Shift-PageDown move more than one
1789
page at a time in a given direction. The keyboard equivalents are
1790
j=UpArrow, k=DownArrow, u=PageUp, d=PageDown, ^=Home, $=End,
1791
U=Shift-PageUp, D=Shift-PageDown, i=Enter.
1792
1793
</para>
1794
1795
1796
<para>
1797
1798
When <application>LifeLines</application> creates a list of
1799
names for you to select from, it tries to add extra
1800
information to the name; this helps determine which name to
1801
choose, and is important in databases where many persons have
1802
the same name. <application>LifeLines</application> also
1803
places the person's key value at the end of each menu line;
1804
this may be helpful in large databases.
1805
1806
</para>
1807
1808
1809
1810
<para>
1811
1812
Some browse screens provide the z command, which allows you to
1813
browse to a new person using the zip style of identification
1814
rather than the b style.
1815
1816
</para>
1817
1818
1819
1820
</sect1>
1821
1822
1823
1824
<sect1>
1825
1826
1827
1828
<title>
1829
1830
BROWSE DISPLAY BASICS
1831
1832
</title>
1833
1834
1835
1836
<para>
1837
1838
The screen display for each browsing screen is made up of
1839
panels. At the bottom of each display is a message panel used
1840
for one line messages. Each display contains one or two data
1841
panels showing information from the database. And each display
1842
has a panel with the operation menu available for that screen.
1843
1844
</para>
1845
1846
1847
1848
</sect1>
1849
1850
1851
1852
<sect1>
1853
1854
1855
1856
<title>
1857
1858
PERSON BROWSE SCREEN
1859
1860
</title>
1861
1862
1863
1864
<para>
1865
1866
After you identify a person to browse to,
1867
<application>LifeLines</application> enters the person browse
1868
screen. The top panel in the display gives basic information
1869
about the person (in the normal, or vitals, mode, which is the
1870
default). The middle panel provides a menu of commands.
1871
For example:
1872
1873
<screen>
1874
person: Thomas Trask WETMORE Sr (25)
1875
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
1876
died: 17 February 1947, New London, New London, Connecticut
1877
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
1878
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
1879
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
1880
child: Portia Louise WETMORE, b. 1892, Conn., d. 1921, Conn. (27)
1881
child: Thomas Trask WETMORE, b. 1896, Conn., d. 1970, Conn. (17)
1882
spouse: Arleen M KEENEY, m. 1914, Conn. (75)
1883
_______________________________________________________________________
1884
Please choose an operation: (pg 1/3)
1885
e Edit the person g Browse to family p Pedigree mode
1886
f Browse to father u Browse to parents n Create new person
1887
m Browse to mother b Browse to persons a Create new family
1888
s Browse to spouse/s h Add as spouse x Swap two families
1889
c Browse to children i Add as child tt Enter tandem mode
1890
o Browse to older sib r Remove as spouse ? Other menu choices
1891
y Browse to younger sib d Remove as child q Return to main menu
1892
_______________________________________________________________________
1893
LifeLines -- Person Browse Screen
1894
</screen>
1895
1896
1897
</para>
1898
1899
1900
1901
<para>
1902
1903
The commands perform a wide variety of functions.
1904
1905
</para>
1906
1907
1908
1909
<para>
1910
1911
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit the person. </action></glossterm><glossdef>
1912
1913
<para>
1914
1915
Edit the person's database
1916
record. <application>LifeLines</application> puts the record
1917
in a file, and then runs a screen editor so you can edit the
1918
record. When you return from the editor,
1919
<application>LifeLines</application> asks you to confirm any
1920
changes; the person is changed only if you answer yes.
1921
1922
</para>
1923
1924
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
1925
1926
<para>
1927
1928
Browse to the person's father. If the father isn't in the
1929
database, <application>LifeLines</application> doesn't change
1930
the display. If there are more than one father,
1931
<application>LifeLines</application> asks you to select one.
1932
1933
</para>
1934
1935
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mother.</action></glossterm><glossdef>
1936
1937
<para>
1938
1939
Browse to the person's mother. If the mother isn't in the
1940
database, <application>LifeLines</application> doesn't change
1941
the display. If there are more than one mother,
1942
<application>LifeLines</application> asks you to select one.
1943
1944
</para>
1945
1946
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse to spouse/s.</action></glossterm><glossdef>
1947
1948
<para>
1949
1950
Browse to the person's spouse. If the person has more than one
1951
spouse, <application>LifeLines</application> asks you to
1952
select one. If the person has no spouse, the display does not
1953
change.
1954
1955
</para>
1956
1957
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
1958
1959
<para>
1960
1961
Browse to one of the person's children. If there is more than
1962
one child, <application>LifeLines</application> asks you to
1963
select one. If the person has no children, the display does
1964
not change.
1965
1966
</para>
1967
1968
</glossdef></glossentry><glossentry><glossterm><keycap>o</keycap> <action>Browse to older sib.</action></glossterm><glossdef>
1969
1970
<para>
1971
1972
Browse to the person's next older sibling. If the person has
1973
no such sibling, the display does not change. Only siblings
1974
from the same family are browsed by this command.
1975
1976
</para>
1977
1978
</glossdef></glossentry><glossentry><glossterm><keycap>y</keycap> <action>Browse to younger sib.</action></glossterm><glossdef>
1979
1980
<para>
1981
1982
Browse to the person's next younger sibling. If the person has
1983
no such sibling, the display does not change. Only siblings
1984
from the same family are browsed by this command.
1985
1986
</para>
1987
1988
</glossdef></glossentry><glossentry><glossterm><keycap>g</keycap> <action>Browse to family.</action></glossterm><glossdef>
1989
1990
<para>
1991
1992
Browse to the family the person is a spouse or parent in, and
1993
switch to the family browse mode. If the person is in more
1994
than one family, <application>LifeLines</application> asks you
1995
to identify which one. If the person is not a spouse or parent
1996
in any family, the display does not change.
1997
1998
</para>
1999
2000
</glossdef></glossentry><glossentry><glossterm><keycap>u</keycap> <action>Browse to parents.</action></glossterm><glossdef>
2001
2002
<para>
2003
2004
Browse to the family the person is a child in, and switch to
2005
the family browse mode. If the person is not a child in a
2006
family, the display does not change. If the person is a child
2007
in more than one family, <application>LifeLines</application>
2008
asks you to identify which one.
2009
2010
</para>
2011
2012
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
2013
2014
<para>
2015
2016
Browse to a new person or list of
2017
persons. <application>LifeLines</application> asks you to
2018
identify a person or persons by name, key or list name, and
2019
depending on how many persons are identified, switches either
2020
to the list browse mode, or remains in the person browse mode.
2021
2022
</para>
2023
2024
</glossdef></glossentry><glossentry><glossterm><keycap>h</keycap> <action>Add as spouse.</action></glossterm><glossdef>
2025
2026
<para>
2027
2028
Add the person as a spouse/parent to an existing
2029
family. <application>LifeLines</application> asks you to
2030
identify the family, and then asks you to confirm the request.
2031
2032
</para>
2033
2034
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Add as child.</action></glossterm><glossdef>
2035
2036
<para>
2037
2038
Add the person as a child to an existing family. The person
2039
may already be a child in another
2040
family. <application>LifeLines</application> asks you to
2041
identify the family, and then asks you to confirm the request.
2042
2043
</para>
2044
2045
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove as spouse.</action></glossterm><glossdef>
2046
2047
<para>
2048
2049
Remove the person as a spouse or parent from an existing
2050
family. If the person is a spouse or parent in more than one
2051
family, <application>LifeLines</application> asks you to
2052
identify the family.
2053
2054
</para>
2055
2056
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Remove as child.</action></glossterm><glossdef>
2057
2058
<para>
2059
2060
Remove the person as a child in an existing family.
2061
2062
</para>
2063
2064
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Create new person.</action></glossterm><glossdef>
2065
2066
<para>
2067
2068
Create and add a new person to the
2069
database. <application>LifeLines</application> creates a
2070
record template and puts you into the screen editor to edit
2071
the record. When you return from the editor,
2072
<application>LifeLines</application> asks you to confirm the
2073
operation. If you do, the new person is added and becomes the
2074
current person. If not, the new person is not added, and
2075
<application>LifeLines</application> returns to the original
2076
display.
2077
2078
</para>
2079
2080
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Create new family.</action></glossterm><glossdef>
2081
2082
<para>
2083
2084
Create and add a new family to the database. The new family
2085
may have the current person as either a spouse/parent or as a
2086
child; <application>LifeLines</application> asks which. If you
2087
choose to create a family with the person as a spouse/parent,
2088
<application>LifeLines</application> asks you to identify the
2089
other spouse if he or she is known. In either case
2090
<application>LifeLines</application> creates a family
2091
template, and places you in the screen editor. When you
2092
return from the editor, <application>LifeLines</application>
2093
asks you to confirm the operation. If you do,
2094
<application>LifeLines</application> adds the family and
2095
shifts into family browse mode. If the command you ran just
2096
before the a command were the n command, and you choose to
2097
create a family with the person as a spouse/parent,
2098
<application>LifeLines</application> guesses that the other
2099
spouse in the family will be the person displayed just before
2100
the new person was
2101
created. <application>LifeLines</application> asks you if this
2102
is the case, and if so, automatically make that person the
2103
other spouse in the new family. If this is not the case,
2104
<application>LifeLines</application> asks you to identify the
2105
other spouse.
2106
2107
</para>
2108
2109
</glossdef></glossentry><glossentry><glossterm><keycap>p</keycap> <action>Pedigree mode.</action></glossterm><glossdef>
2110
2111
<para>
2112
2113
Change to pedigree browse mode. The person becomes the root
2114
person in the pedigree display.
2115
2116
</para>
2117
2118
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap two families.</action></glossterm><glossdef>
2119
2120
<para>
2121
2122
Swap (change chronological order) any two families that the
2123
person belongs to as a spouse or
2124
parent. <application>LifeLines</application> asks you to
2125
identify the two families and then swaps them.
2126
2127
</para>
2128
2129
</glossdef></glossentry><glossentry><glossterm><keycap>tt</keycap> <action>Enter tandem mode.</action></glossterm><glossdef>
2130
2131
<para>
2132
2133
Change to the tandem person browse
2134
mode. <application>LifeLines</application> first asks you to
2135
identify the second person.
2136
2137
</para>
2138
2139
</glossdef></glossentry><glossentry><glossterm><keycap>?</keycap> <action>Other menu choices.</action></glossterm><glossdef>
2140
2141
<para>
2142
Go to the next page of menu choices. This will have no effect on the
2143
upper (data) portion of the screen, but it allows you to page through
2144
all available commands for this display screen.
2145
</para>
2146
2147
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2148
2149
<para>
2150
2151
Return to the <application>LifeLines</application> main menu.
2152
2153
</para>
2154
2155
</glossdef></glossentry><glossentry><glossterm><keycap>z</keycap> <action>Zip browse to person.</action></glossterm><glossdef>
2156
2157
<para>
2158
2159
Zip browse to a new person.
2160
<application>LifeLines</application> asks you to
2161
identify a person by name or key value, and if you do so,
2162
browses to that person.
2163
2164
</para>
2165
2166
2167
</glossdef></glossentry></glosslist>
2168
2169
</para>
2170
2171
2172
2173
</sect1>
2174
2175
<sect1>
2176
2177
<title>
2178
2179
LIST BROWSE SCREEN
2180
2181
</title>
2182
2183
2184
2185
<para>
2186
2187
This browse screen handles lists of persons. The top panel shows
2188
information about one person in the list. The left panel
2189
shows a list of up to 12 persons. The person shown in the top
2190
panel is identified by the > character. The right panel is the
2191
menu of available commands.
2192
2193
<screen>
2194
person: Thomas Trask WETMORE Sr (25)
2195
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
2196
died: 17 February 1947, New London, New London, Connecticut
2197
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
2198
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
2199
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
2200
_______________________________________________________________________
2201
Thomas Trask WETMORE (42) Choose an operation:
2202
Thomas Trask WETMORE III (6) j Move down list
2203
Thomas Trask WETMORE IV (1) k Move up list
2204
Thomas Trask WETMORE (11) e Edit this person
2205
>Thomas Trask WETMORE Sr (23) i Browse this person
2206
Thomas Trask WETMORE (5) m Mark this person
2207
r Remove from list
2208
t Enter tandem mode
2209
n Name this list
2210
b Browse new persons
2211
a Add to this list
2212
x Swap mark/current
2213
q Return to main menu
2214
_______________________________________________________________________
2215
LifeLines -- List Browse Screen
2216
</screen>
2217
2218
2219
</para>
2220
2221
2222
2223
<para>
2224
2225
<glosslist><glossentry><glossterm><keycap>j</keycap> <action>Move down list.</action></glossterm><glossdef>
2226
2227
<para>
2228
2229
Move down the list one person. The list panel is only large
2230
enough to show 12 persons. However, the list may contain many
2231
more persons. Use the <keycap>j</keycap> and
2232
<keycap>k</keycap> commands to scroll to these other persons.
2233
2234
</para>
2235
2236
</glossdef></glossentry><glossentry><glossterm><keycap>k</keycap> <action>Move up list.</action></glossterm><glossdef>
2237
2238
<para>
2239
2240
Move up the list one person. The list panel is only large
2241
enough to show 12 persons. However, the list may contain many
2242
more persons. Use the <keycap>j</keycap> and
2243
<keycap>k</keycap> commands to scroll to these other persons.
2244
2245
</para>
2246
2247
<para>
2248
2249
With version 3.0.15, lists may also be navigated with the up
2250
and down arrows, PageUp and PageDown keys, Home and End keys, and
2251
the Enter key. Shift-PageUp and Shift-PageDown move more than one
2252
page at a time in a given direction. The keyboard equivalents are
2253
j=UpArrow, k=DownArrow, u=PageUp, d=PageDown, ^=Home, $=End,
2254
U=Shift-PageUp, D=Shift-PageDown, i=Enter.
2255
2256
</para>
2257
2258
</glossdef></glossentry><glossentry><glossterm><keycap>e</keycap> <action>Edit this person.</action></glossterm><glossdef>
2259
2260
<para>
2261
2262
Edit the displayed person's database
2263
record. <application>LifeLines</application> runs the editor
2264
on the person's record. When you return from the editor,
2265
<application>LifeLines</application> asks you to confirm any
2266
changes, and then leaves you in the list browse screen.
2267
2268
</para>
2269
2270
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Browse this person.</action></glossterm><glossdef>
2271
2272
<para>
2273
2274
Change to the person browse screen with the current person.
2275
2276
</para>
2277
2278
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Mark this person.</action></glossterm><glossdef>
2279
2280
<para>
2281
2282
Mark the current person if he/she is not marked; unmark the
2283
person is he/she is. The marked person is shown with an x by
2284
his/her name. Marked persons are used by the t and x
2285
commands. Only one person may be marked at a time.
2286
2287
</para>
2288
2289
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove from list.</action></glossterm><glossdef>
2290
2291
<para>
2292
2293
Remove the current person from the browse list (not from the database).
2294
2295
</para>
2296
2297
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Enter tandem mode.</action></glossterm><glossdef>
2298
2299
<para>
2300
2301
Change to the tandem person mode with the current person and
2302
the marked person as the two persons. If no person is marked there is no change.
2303
2304
</para>
2305
2306
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Name this list.</action></glossterm><glossdef>
2307
2308
<para>
2309
2310
Lists of persons may be named, allowing you to quickly browse
2311
back to them by giving a list name in response to the b
2312
command from different
2313
modes. <application>LifeLines</application> will prompt you
2314
for the name. List names are most convenient when short.
2315
2316
</para>
2317
2318
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse new persons.</action></glossterm><glossdef>
2319
2320
<para>
2321
2322
Browse to a new person or list of persons. You can identify a
2323
person or list of persons by name, internal or user key or by
2324
list name.
2325
2326
</para>
2327
2328
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add to this list.</action></glossterm><glossdef>
2329
2330
<para>
2331
2332
Add more persons to the current browse
2333
list. <application>LifeLines</application> asks you to
2334
identify a new person or list of persons by name, key or list
2335
name, and they are added to and name-sorted into the current
2336
list.
2337
2338
</para>
2339
2340
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap mark/current.</action></glossterm><glossdef>
2341
2342
<para>
2343
2344
Swap the current person with the marked person in the list.
2345
2346
</para>
2347
2348
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2349
2350
<para>
2351
2352
Return to the <application>LifeLines</application> main menu.
2353
2354
</para>
2355
2356
</glossdef></glossentry></glosslist>
2357
2358
</para>
2359
2360
2361
2362
</sect1>
2363
2364
2365
2366
<sect1>
2367
2368
2369
2370
<title>
2371
2372
FAMILY BROWSE SCREEN
2373
2374
</title>
2375
2376
2377
2378
<para>
2379
2380
This browse screen displays information about a family. The top
2381
panel shows basic information about the family. The bottom
2382
panel shows the menu of available commands. If the database contains
2383
more than two parents for this family only the first two are displayed.
2384
2385
<screen>
2386
father: Thomas Trask WETMORE IV (1)
2387
born: 18 December 1949, New London, New London, Connecticut
2388
died:
2389
mother: Luann Frances GRENDA (2)
2390
born: 10 July 1949, Pittsburgh, Allegheny, Pennsylvania
2391
died:
2392
married: 1 August 1970, Governors Island, New York, New York
2393
child: Anna Vivian Wetmore, b. 1974, Alaska (3)
2394
child: Marie Margaret WETMORE, b. 1979, Conn. (4)
2395
child: Thomas Trask WETMORE V, b. 1982, Mass. (5)
2396
_______________________________________________________________________
2397
Please choose an operation: (pg 1/4)
2398
e Edit the family %s Add source r Remove spouse from
2399
f Browse to father %e Add event d Remove child from
2400
m Browse to mother %o Add other x Swap two children
2401
c Browse to children s Add spouse to family ? Other menu choices
2402
n Create new person a Add child to family q Return to main menu
2403
_______________________________________________________________________
2404
LifeLines -- Family Browse Screen (* toggles menu)
2405
2406
</screen>
2407
</para>
2408
2409
2410
2411
<para>
2412
2413
<glosslist>
2414
<glossentry><glossterm><keycap>e</keycap> <action>Edit the family.</action></glossterm><glossdef>
2415
2416
<para>
2417
2418
Edit the family's record. <application>LifeLines</application>
2419
writes the record to a file and puts you into an editor to
2420
edit the file. When you return from the editor,
2421
<application>LifeLines</application> asks you to confirm the
2422
update; the family is changed only if you do so.
2423
2424
</para>
2425
2426
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
2427
2428
<para>
2429
2430
Browse to the father/husband of the family, switching to
2431
person browse screen. If the father is not there, there is no change.
2432
2433
</para>
2434
2435
</glossdef>
2436
</glossentry>
2437
2438
<glossentry><glossterm><keycap>m</keycap><action>Browse to mother.</action>
2439
</glossterm>
2440
2441
<glossdef>
2442
2443
<para>
2444
2445
Browse to the mother/wife of the family, switching to person
2446
browse screen. If the mother is not there, there is no change.
2447
2448
</para>
2449
2450
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
2451
2452
<para>
2453
2454
Browse to a child in the family, switching to the person
2455
browse screen. If the family has more than one child,
2456
<application>LifeLines</application> asks you to identify a
2457
specific child.
2458
2459
</para>
2460
2461
</glossdef></glossentry><glossentry><glossterm><keycap>n</keycap> <action>Create new person.</action></glossterm><glossdef>
2462
2463
<para>
2464
2465
Create and add a new person to the
2466
database. <application>LifeLines</application> creates a
2467
record template and puts you into the screen editor to edit
2468
the record. When you return from the editor,
2469
<application>LifeLines</application> asks you to confirm the
2470
operation. If you do, the new person is added to the
2471
database. If not, the new person is not added. In both cases
2472
the display does not change.
2473
2474
</para>
2475
2476
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Add spouse to family.</action></glossterm><glossdef>
2477
2478
<para>
2479
2480
Add a spouse to the
2481
family. <application>LifeLines</application> asks you to
2482
identify the new spouse. If the command you ran just before
2483
the s command were the n command,
2484
<application>LifeLines</application> guesses that the new
2485
spouse will be the person just
2486
created. <application>LifeLines</application> asks if this is
2487
the case, and if so, makes that person the second spouse in
2488
the family. If not, <application>LifeLines</application> asks
2489
you to identify the other spouse.
2490
2491
</para>
2492
2493
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add child to family.</action></glossterm><glossdef>
2494
2495
<para>
2496
2497
Add a child to the
2498
family. <application>LifeLines</application> asks you to
2499
identify the new child. If the command you ran just before the
2500
a command were the n command,
2501
<application>LifeLines</application> guesses that the new
2502
child will be the person just
2503
created. <application>LifeLines</application> asks if this is
2504
the case, and if so, adds that child to the family. If not,
2505
<application>LifeLines</application> asks you to identify the
2506
child. If the family already has children,
2507
<application>LifeLines</application> also asks where to place
2508
the new child in the family.
2509
2510
</para>
2511
2512
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Remove spouse from.</action></glossterm><glossdef>
2513
2514
<para>
2515
2516
Remove a parent/spouse from the
2517
family. <application>LifeLines</application> asks you to
2518
identify the person, and if you do, removes him or her. The
2519
person is not removed from the database.
2520
2521
</para>
2522
2523
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Remove child from.</action></glossterm><glossdef>
2524
2525
<para>
2526
2527
Remove a child from the
2528
family. <application>LifeLines</application> asks you to
2529
identify the child should, and if you do, removes the child
2530
from the family. The person is not removed from the database.
2531
2532
</para>
2533
2534
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Swap two children.</action></glossterm><glossdef>
2535
2536
<para>
2537
2538
Swap (change the chronological order) of any two children in
2539
the family. <application>LifeLines</application> asks you to
2540
identify the two children and then swaps them.
2541
2542
</para>
2543
2544
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Enter family tandem.</action></glossterm><glossdef>
2545
2546
<para>
2547
2548
This command takes you to the tandem family browse
2549
screen. <application>LifeLines</application> asks you to
2550
identify a second family, and then takes you to the tandem
2551
family screen, displaying both the two families.
2552
2553
</para>
2554
2555
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
2556
2557
<para>
2558
2559
Browse to a new person or list of persons. You can identify a
2560
person or list by name, by key, or by list name. If you
2561
successfully identify a new person or persons you will switch
2562
into the person or list browse screens.
2563
2564
</para>
2565
2566
</glossdef></glossentry><glossentry><glossterm><keycap>z</keycap> <action>Browse to person.</action></glossterm><glossdef>
2567
2568
<para>
2569
2570
Zip browse to a new person.
2571
<application>LifeLines</application> asks you to identify a
2572
person by name or key value, and if you do, browses to that
2573
person.
2574
2575
</para>
2576
2577
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2578
2579
<para>
2580
2581
Return to the <application>LifeLines</application> main menu.
2582
2583
</para>
2584
2585
</glossdef></glossentry></glosslist>
2586
2587
</para>
2588
2589
2590
2591
</sect1>
2592
2593
2594
2595
<sect1>
2596
2597
2598
2599
<title>
2600
2601
TANDEM PERSON BROWSE MODE
2602
2603
</title>
2604
2605
2606
2607
<para>
2608
2609
The tandem person browse screen displays information about two
2610
persons. Its main use it to support the person merging
2611
operation. The top two panels show two persons in the format
2612
used in the person and list screen displays. The bottom panel
2613
gives the menu of available commands. For example:
2614
2615
2616
<screen>
2617
person: Thomas Trask WETMORE Sr (25)
2618
born: 13 March 1866, St. Mary's Bay, Digby, Nova Scotia
2619
died: 17 February 1947, New London, New London, Connecticut
2620
father: Daniel Lorenzo WETMORE, b. 1821, N.S., d. 1903, Conn. (48)
2621
mother: Mary Ann DOTY, b. 1824, N.S., d. 1897, Conn. (59)
2622
spouse: Margaret Ellen KANEEN, b. 1855, Eng., d. 1900, Conn. (26)
2623
______________________________________________________________________
2624
person: Thomas Trask WETMORE IV (1)
2625
born: 18 December 1949, New London, New London, Connecticut
2626
died:
2627
father: Thomas Trask WETMORE III, b. 1925, Conn. (6)
2628
mother: Joan Marie HANCOCK, b. 1928, Conn. (7)
2629
spouse: Luann Frances GRENDA, m. 1970, N.Y. (2)
2630
______________________________________________________________________
2631
Please choose an operation:
2632
e Edit top person s Browse top spouse/s a Add family
2633
t Browse to top c Browse top children j Merge bottom to top
2634
f Browse top father b Browse to persons x Switch top/bottom
2635
m Browse top mother d Copy top to bottom q Return to main menu
2636
______________________________________________________________________
2637
LifeLines - Two Person Browse Screen
2638
</screen>
2639
2640
2641
</para>
2642
2643
2644
2645
<para>
2646
2647
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit top person.</action></glossterm><glossdef>
2648
2649
<para>
2650
2651
Edit the top person's
2652
record. <application>LifeLines</application> writes the record
2653
to a file, and puts you in the screen editor to edit the
2654
file. When you return from the editor,
2655
<application>LifeLines</application> asks you to confirm the
2656
update; the person is changed only if you do so.
2657
2658
</para>
2659
2660
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Browse to top.</action></glossterm><glossdef>
2661
2662
<para>
2663
2664
Switch to the person display with the top person as current person.
2665
2666
</para>
2667
2668
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse top father.</action></glossterm><glossdef>
2669
2670
<para>
2671
2672
Replace the top person with his/her father.
2673
2674
</para>
2675
2676
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse top mother.</action></glossterm><glossdef>
2677
2678
<para>
2679
2680
Replace the top person with his/her mother.
2681
2682
</para>
2683
2684
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse top spouse/s.</action></glossterm><glossdef>
2685
2686
<para>
2687
2688
Replace the the top person with his/her spouse. If the person
2689
has more than one spouse, <application>LifeLines</application>
2690
asks you to identify one.
2691
2692
</para>
2693
2694
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse top children.</action></glossterm><glossdef>
2695
2696
<para>
2697
2698
Replace the top person with one of his/her children. If the person has more
2699
than one child, <application>LifeLines</application> asks you to identify the one.
2700
2701
</para>
2702
2703
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
2704
2705
<para>
2706
2707
Browse to a new person or list of persons. <application>LifeLines</application> asks you to identify a new
2708
person or persons by name, key or list name, and then does as described in the section on identifying a
2709
person.
2710
2711
</para>
2712
2713
</glossdef></glossentry><glossentry><glossterm><keycap>d</keycap> <action>Copy top to bottom.</action></glossterm><glossdef>
2714
2715
<para>
2716
2717
Copy the top person into the bottom person. A new person is not created; the same
2718
person is displayed twice.
2719
2720
</para>
2721
2722
</glossdef></glossentry><glossentry><glossterm><keycap>a</keycap> <action>Add family.</action></glossterm><glossdef>
2723
2724
<para>
2725
2726
Create a new family record; <application>LifeLines</application> assumes the two displayed persons are to become
2727
the spouses/parents in the new family; they must be of opposite sex.
2728
2729
</para>
2730
2731
</glossdef></glossentry><glossentry><glossterm><keycap>j</keycap> <action>Merge bottom to top.</action></glossterm><glossdef>
2732
2733
<para>
2734
2735
Merge the bottom person into the top person. <application>LifeLines</application> combines the two person
2736
records and places you in the screen editor to edit the combined record. When you are done, if you
2737
confirm the operation, <application>LifeLines</application> removes the bottom person from the database, and the top person is
2738
given the combined record. See the section on merging.
2739
2740
</para>
2741
2742
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Switch top/bottom.</action></glossterm><glossdef>
2743
2744
<para>
2745
2746
Swap the two persons in the display.
2747
2748
</para>
2749
2750
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2751
2752
<para>
2753
2754
Return to the <application>LifeLines</application> main menu.
2755
2756
</para>
2757
2758
</glossdef></glossentry></glosslist>
2759
2760
</para>
2761
2762
2763
2764
</sect1>
2765
2766
2767
2768
<sect1>
2769
2770
2771
2772
<title>
2773
2774
TANDEM FAMILY BROWSE MODE
2775
2776
</title>
2777
2778
2779
2780
<para>
2781
2782
The tandem family browse screen displays information about two families. Its main use it to support the
2783
family merging operation.The top two panels provide information about the two families you are
2784
browsing, and the bottom panel holds the menu of available commands. For example:
2785
<screen>
2786
father: Thomas Trask WETMORE IV (1)
2787
born: 18 December 1949, New London, New London, Connecticut
2788
mother: Luann Frances GRENDA (2)
2789
born: 10 July 1949, Pittsburgh, Allegheny, Pennsylvania
2790
married: 1 August 1970, Governors Island, New York, New York
2791
child: Anna Vivian WETMORE, b. 1974, Alaska (3)
2792
__________________________________________________________________
2793
father: Thomas Trask WETMORE III (6)
2794
born: 26 October 1925, New London, New London, Connecticut
2795
wife: Joan Marie Hancock (7)
2796
born: 6 June 1928, New London, New London, Connecticut
2797
married: 5 February 1949, New London, New London, Connecticut
2798
child: Thomas Trask WETMORE IV, b. 1949, Conn. (1)
2799
__________________________________________________________________
2800
Please choose an operation: (pg 1/3)
2801
e Edit top person m Browse to mothers )b Scroll bottom down
2802
t Browse to top (t Scroll top up (( Scroll both up
2803
b Browse to bottom )t Scroll top down ? Other menu choices
2804
f Browse to fathers (b Scroll bottom up q Return to main menu
2805
__________________________________________________________________
2806
LifeLines -- Two Family Browse Screen (* toggles menu)
2807
</screen>
2808
2809
2810
</para>
2811
2812
2813
2814
<para>
2815
2816
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit top family.</action></glossterm><glossdef>
2817
2818
<para>
2819
2820
This command lets you edit the top family's record. <application>LifeLines</application> writes the record into
2821
a file, and then puts you into an editor to edit that information. When you return from the editor,
2822
<application>LifeLines</application> asks you whether you are sure you want to update the family in the database. The family
2823
is changed only if you answer yes.
2824
2825
</para>
2826
2827
</glossdef></glossentry><glossentry><glossterm><keycap>t</keycap> <action>Browse to top.</action></glossterm><glossdef>
2828
2829
<para>
2830
2831
Change to the family browse screen with the top family the current family.
2832
2833
</para>
2834
2835
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to bottom.</action></glossterm><glossdef>
2836
2837
<para>
2838
2839
Change to the single family browse screen with the bottom family the current
2840
family.
2841
2842
</para>
2843
2844
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to fathers.</action></glossterm><glossdef>
2845
2846
<para>
2847
2848
Change to the tandem person screen with the fathers of the two
2849
families as the two persons.
2850
2851
</para>
2852
2853
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mothers.</action></glossterm><glossdef>
2854
2855
<para>
2856
2857
Change to the tandem person screen with the mothers of the two
2858
families as the two persons.
2859
2860
</para>
2861
2862
</glossdef></glossentry><glossentry><glossterm><keycap>(t</keycap> <action>Scroll top up.</action></glossterm><glossdef>
2863
2864
<para>
2865
2866
TODO
2867
2868
</para>
2869
2870
</glossdef></glossentry><glossentry><glossterm><keycap>)t</keycap> <action>Scroll top down.</action></glossterm><glossdef>
2871
2872
<para>
2873
2874
TODO
2875
2876
</para>
2877
2878
</glossdef></glossentry><glossentry><glossterm><keycap>(b</keycap> <action>Scroll bottom up.</action></glossterm><glossdef>
2879
2880
<para>
2881
2882
TODO
2883
2884
</para>
2885
2886
</glossdef></glossentry><glossentry><glossterm><keycap>)b</keycap> <action>Scroll bottom down.</action></glossterm><glossdef>
2887
2888
<para>
2889
2890
TODO
2891
2892
</para>
2893
2894
</glossdef></glossentry><glossentry><glossterm><keycap>((</keycap> <action>Scroll both up.</action></glossterm><glossdef>
2895
2896
<para>
2897
2898
TODO
2899
2900
</para>
2901
2902
</glossdef></glossentry><glossentry><glossterm><keycap>))</keycap> <action>Scroll both down.</action></glossterm><glossdef>
2903
2904
<para>
2905
2906
TODO
2907
2908
</para>
2909
2910
</glossdef></glossentry><glossentry><glossterm><keycap>#</keycap> <action>Toggle childnos.</action></glossterm><glossdef>
2911
2912
<para>
2913
2914
TODO
2915
2916
</para>
2917
2918
</glossdef></glossentry><glossentry><glossterm><keycap>(1-9)</keycap> <action>Browse to child.</action></glossterm><glossdef>
2919
2920
<para>
2921
2922
TODO
2923
2924
</para>
2925
2926
</glossdef></glossentry><glossentry><glossterm><keycap>j</keycap> <action>Merge bottom to top.</action></glossterm><glossdef>
2927
2928
<para>
2929
2930
Merge the bottom family into the top family. <application>LifeLines</application> combines the two
2931
family records and places you in the screen editor to edit the combined record. When you are done, if
2932
you confirm the operation, <application>LifeLines</application> deletes the bottom family from the database, and the top
2933
family is given the combined record. See the section on merging.
2934
2935
</para>
2936
2937
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap> <action>Switch top/bottom.</action></glossterm><glossdef>
2938
2939
<para>
2940
2941
Swap the two families in the display.
2942
2943
</para>
2944
2945
<para>
2946
[There are some more miscellaneous commands available on the menus.]
2947
</para>
2948
2949
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
2950
2951
<para>
2952
2953
Return to the <application>LifeLines</application> main menu.
2954
2955
</para>
2956
2957
</glossdef></glossentry></glosslist>
2958
2959
</para>
2960
2961
2962
2963
</sect1>
2964
2965
2966
2967
<sect1>
2968
2969
2970
2971
<title>
2972
2973
PEDIGREE BROWSE MODE
2974
2975
</title>
2976
2977
2978
2979
<para>
2980
2981
The pedigree browse screen displays a four-generation pedigree for the current person. The top panel
2982
holds the pedigree, and the bottom panel holds the menu of available commands. For example:
2983
<screen>
2984
John WETMORE [1755-1848] (32)
2985
Daniel Van Cott WETMORE [1791-1881] (41)
2986
Anna VAN COTT [1757-1802] (33)
2987
Daniel Lorenzo WETMORE [1821-1903] (48)
2988
Thomas TRASK [-1836] (81)
2989
Hannah TRASK [1797-1829] (46)
2990
Susannah PORTER [1754-] (82)
2991
Thomas Trask WETMORE Sr [1866-1947] (25)
2992
Samuel DOTY [1759-] (501)
2993
Samuel DOTY [1787-] (74)
2994
Hephzibah PORTER [1764-1853] (502)
2995
Mary Ann DOTY [1827-1897] (59)
2996
Nathan SAVERY [1748-1826] (510)
2997
Lydia SAVERY [1806-] (75)
2998
Deidamia SABEAN [1765-1845] (511)
2999
__________________________________________________________________
3000
Please choose an operation:
3001
e Edit the person m Browse to mother g Browse to family
3002
i Browse to person s Browse to spouse/s b Browse to persons
3003
f Browse to father c Browse to children q Return to main menu
3004
__________________________________________________________________
3005
LifeLines - Pedigree Browse Mode</screen>
3006
3007
</para>
3008
3009
3010
3011
<para>
3012
3013
<glosslist><glossentry><glossterm><keycap>e</keycap> <action>Edit the person.</action></glossterm><glossdef>
3014
3015
<para>
3016
3017
Edit the current person.
3018
3019
</para>
3020
3021
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Browse to person.</action></glossterm><glossdef>
3022
3023
<para>
3024
3025
Change to the person display mode with the current person.
3026
3027
</para>
3028
3029
</glossdef></glossentry><glossentry><glossterm><keycap>f</keycap> <action>Browse to father.</action></glossterm><glossdef>
3030
3031
<para>
3032
3033
Browse to the father of the current person, shifting the pedigree one
3034
generation back. If the father is not in the database, there is no change.
3035
3036
</para>
3037
3038
</glossdef></glossentry><glossentry><glossterm><keycap>m</keycap> <action>Browse to mother.</action></glossterm><glossdef>
3039
3040
<para>
3041
3042
Browse to the mother of the current person, shifting the pedigree one
3043
generation back. If the mother is not in the database, there is no change.
3044
3045
</para>
3046
3047
</glossdef></glossentry><glossentry><glossterm><keycap>s</keycap> <action>Browse to spouse/s.</action></glossterm><glossdef>
3048
3049
<para>
3050
3051
Browse to a spouse of the current person, shifting the display to the pedigree of
3052
that person. If the current person has more than one spouse, <application>LifeLines</application> asks you to identify the spouse;
3053
if the person has no spouse there is no change.
3054
3055
</para>
3056
3057
</glossdef></glossentry><glossentry><glossterm><keycap>c</keycap> <action>Browse to children.</action></glossterm><glossdef>
3058
3059
<para>
3060
3061
Browse to a child of the current person, shifting the pedigree one generation
3062
forward. If the current person has more than one child, <application>LifeLines</application> asks you to identify the child; if
3063
the person has no children there is no change.
3064
3065
</para>
3066
3067
</glossdef></glossentry><glossentry><glossterm><keycap>g</keycap> <action>Browse to family.</action></glossterm><glossdef>
3068
3069
<para>
3070
3071
Change to the family display; the family will be the one that the current person
3072
belongs to as spouse or parent. If there are more than one, <application>LifeLines</application> asks you to identify the proper
3073
one.
3074
3075
</para>
3076
3077
</glossdef></glossentry><glossentry><glossterm><keycap>b</keycap> <action>Browse to persons.</action></glossterm><glossdef>
3078
3079
<para>
3080
3081
Browse to another person or list of persons; if you identify a single person the
3082
display remains in the pedigree display; if you identify more than one person the display changes to
3083
the list browse mode.
3084
3085
</para>
3086
3087
</glossdef></glossentry><glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
3088
3089
<para>
3090
3091
Leave the pedigree browsing mode and return to the main menu.
3092
3093
</para>
3094
3095
</glossdef></glossentry></glosslist>
3096
3097
</para>
3098
3099
3100
</sect1>
3101
3102
3103
<sect1>
3104
3105
3106
<title>
3107
SEARCH MENU
3108
</title>
3109
3110
<para>
3111
If you choose Search database from the main menu, <application>LifeLines</application> displays the search menu:
3112
<screen>
3113
How would you like to find a record?
3114
v Review visit history (12 records)
3115
c Review change history (3 records)
3116
f Full database scan
3117
q Return to previous menu
3118
</screen>
3119
The first two items will depend on your previous activity. If you have
3120
browsed to individuals or family records in the database,
3121
the first item will appear similar to what's shown above,
3122
if you haven't it will just contain a note that the visit history is empty.
3123
The second item will appear similar to what's shown above if you
3124
have changed individual records in this session
3125
with <application>LifeLines</application>, otherwise it will contain
3126
a note that the change history is empty.
3127
</para>
3128
<para>
3129
Selecting a non-empty visit history or change history will bring up a list
3130
of individuals (or families) that are in the history, allowing you to
3131
browse to that individual or family.
3132
</para>
3133
<para>
3134
If you choose Full database scan off the search menu,
3135
<application>LifeLines</application> displays the fullscan menu.
3136
<screen>
3137
What scan type?
3138
f Full name scan
3139
n Name fragment (whitespace-delimited) scan
3140
r Refn scan
3141
q Return to previous menu
3142
</screen>
3143
The first two items on this menu allow you to search all the NAME
3144
records in the current database.
3145
If you choose Full name scan you are prompted for a
3146
search pattern and then <application>LifeLines</application> searches for all
3147
the individual NAME records whose value matches the pattern supplied.
3148
If you choose the Name fragment scan, you will be prompted for a
3149
search pattern and then <application>LifeLines</application> will search for
3150
whitespace delimited words within individual NAME records that match the
3151
pattern supplied.
3152
</para>
3153
<sect2>
3154
<title>
3155
Search Patterns
3156
</title>
3157
<para>
3158
The pattern supplied to the search commands is used to match against
3159
the names in the database. The following characters have special meaning
3160
when used in a pattern:
3161
<informaltable pgwide='0' frame='none'>
3162
<tgroup cols='2'>
3163
<colspec colwidth='0.5in'></colspec>
3164
<tbody>
3165
<row>
3166
<entry>?</entry>
3167
<entry>Matches any single character</entry>
3168
</row>
3169
3170
<row>
3171
<entry>*</entry>
3172
<entry>
3173
Matches zero or more occurrences of any character
3174
</entry>
3175
</row>
3176
3177
<row>
3178
<entry>SUB</entry>
3179
<entry>
3180
a control Z (^Z) is similar to '*', this matches zero
3181
or more occurences of any characters other than '.'.
3182
(of course you probably can't type this on unix)
3183
</entry>
3184
</row>
3185
3186
<row>
3187
<entry>[ab]</entry>
3188
<entry>
3189
A set of characters enclosed in square brackets
3190
matches the single characters listed between the
3191
brackets. If the dash '-' character is to be included,
3192
it must immediately follow the opening bracket '['.
3193
If the closing bracket ']' character is to be included,
3194
it must be preceded by a quote '`'.
3195
</entry>
3196
</row>
3197
3198
<row>
3199
<entry>[a-z]</entry>
3200
<entry>
3201
Matches a single character in the range 'a' to 'z'.
3202
Ranges and sets may be combined within the same set of
3203
brackets.
3204
</entry>
3205
</row>
3206
3207
3208
<row>
3209
<entry>!R</entry>
3210
<entry>
3211
Matches a single character not in the range 'R'.
3212
If range 'R' includes the dash '-' character, the dash
3213
must immediately follow the '!'.
3214
</entry>
3215
</row>
3216
3217
<row>
3218
<entry>!</entry>
3219
<entry>
3220
Makes the following pattern match
3221
any string except those what it would normally match.
3222
</entry>
3223
</row>
3224
3225
<row>
3226
<entry>QUOTE</entry>
3227
<entry>
3228
(On DOS this is `, on UNIX it is \)
3229
Makes the next character a regular (nonspecial)
3230
character.
3231
Note that to match the quote character itself, it must
3232
be quoted.
3233
Note that this character must be escaped if used within
3234
string constants ("\\").
3235
</entry>
3236
</row>
3237
</tbody>
3238
</tgroup>
3239
</informaltable>
3240
</para>
3241
<para>
3242
Upper and lower case alphabetic characters are considered identical,
3243
i.e., 'a' and 'A' match each other.
3244
(What constitutes a lowercase letter depends on the current locale
3245
settings.)
3246
</para>
3247
<para>
3248
Spaces and control characters (other than control z) are treated as normal
3249
characters,
3250
</para>
3251
3252
<para>
3253
As an example, consider the following NAME record:
3254
<programlisting>
3255
1 NAME <userinput>John /Smith/</userinput>
3256
</programlisting>
3257
When doing a full name search, the value searched is the complete gedcom name
3258
value including the slashes used to delimit the surname.
3259
in order to have a match, the search pattern
3260
must match the slashes. Thus
3261
3262
<programlisting>
3263
*smith
3264
</programlisting>
3265
will not match this name, whereas
3266
<programlisting>
3267
*smith/
3268
</programlisting>
3269
will match.
3270
</para>
3271
3272
<para>
3273
When doing a name fragment search, the slashes are removed from the surname
3274
before trying to match the name, thus
3275
<programlisting>
3276
smith
3277
smi*
3278
joh*
3279
*hn
3280
</programlisting>
3281
will all match this NAME record.
3282
</para>
3283
3284
</sect2>
3285
</sect1>
3286
3287
<sect1>
3288
3289
<title>
3290
ADD OPERATION
3291
</title>
3292
3293
3294
3295
<para>
3296
3297
If you choose the add operation from the main menu, <application>LifeLines</application> displays the add menu:
3298
<screen>
3299
What do you want to add?
3300
p Person - add new person to the database
3301
f Family - create family record from one or two spouses
3302
c Child - add a child to an existing family
3303
s Spouse - add a spouse to an existing family
3304
q Quit - return to the previous menu
3305
</screen>
3306
3307
3308
</para>
3309
3310
3311
3312
<para>
3313
3314
These operations work in a straightforward way. <application>LifeLines</application> asks you the necessary questions, and lets
3315
you cancel at any time. The operations provided by this menu are also available from the browsing
3316
modes, and are often easier to perform there.
3317
3318
</para>
3319
3320
3321
3322
3323
</sect1>
3324
3325
3326
3327
<sect1>
3328
3329
3330
3331
<title>
3332
3333
DELETE OPERATION
3334
3335
</title>
3336
3337
3338
3339
<para>
3340
3341
If you choose the delete operation at the main menu, <application>LifeLines</application> displays the delete menu:
3342
<screen>
3343
What do you want to delete?
3344
c Child - remove a child from his/her family
3345
s Spouse - remove a spouse from a family
3346
p Person - remove a person completely
3347
q Quit - return to the previous menu
3348
</screen>
3349
3350
3351
</para>
3352
3353
3354
3355
<para>
3356
3357
These operations also work in a straightforward way. <application>LifeLines</application> asks you the necessary questions and
3358
lets you cancel at any time.
3359
3360
3361
</para>
3362
3363
3364
3365
<para>
3366
3367
You may also remove a child from his/her family, or remove a spouse/parent from his/her family,
3368
from the person browsing mode. In both cases, only a relationship is removed, not a person. On the other
3369
hand, the delete menu must be used if you want to completely remove a person from the database; this
3370
cannot be done from the browsing mode.
3371
3372
3373
</para>
3374
3375
3376
3377
<para>
3378
3379
There is no special operation for removing a family record. <application>LifeLines</application> silently removes any family
3380
record that has no parent or child associated with it.
3381
3382
</para>
3383
3384
3385
3386
</sect1>
3387
3388
3389
3390
<sect1>
3391
3392
3393
3394
<title>
3395
3396
CODESET CONVERSION
3397
3398
</title>
3399
3400
3401
3402
<para>
3403
3404
(This section was previously entitled CHARACTER TRANSLATION.)
3405
3406
</para>
3407
3408
<para>
3409
3410
The intention is that you need only specify the internal codeset for
3411
each database you create (and this step may be automated via the NewDbProps
3412
property), and all else works pretty well without tuning. That is,
3413
lifelines tries to guess the correct codeset for your environment (including
3414
guessing the console and windows codesets when operating under MS-Windows,
3415
which it should do fairly well).
3416
3417
</para>
3418
3419
<para>
3420
3421
However, you may encounter situations where you wish to alter the codeset
3422
behavior, or the codeset conversion is not operating correctly (in which case
3423
we hope you will report the problem to the mailing list and/or sourceforge
3424
bugs list).
3425
3426
</para>
3427
3428
<para>
3429
3430
There are two ways to amend codeset conversion. The first method is by
3431
changing configuration variables. For example, if you wish to generate an
3432
HTML report of all your data, which includes names in Russian (in Cyrillic
3433
letters), for your cousin, and you know that your cousin's computer has no
3434
font for Cyrillic letters, you might wish to temporarily adjust your
3435
report output codeset so that you will get interpolated ASCII letters for
3436
the Russian letters. You could do this by temporarily altering the
3437
configuration variable ReportCodesetOut to be "ASCII" (actually, if any of
3438
your data has characters in it that are reserved in HTML, such as the less
3439
than sign, or the ampersand, you would probaby want "ASCII//HTML").
3440
3441
</para>
3442
3443
<para>
3444
3445
The second way to change codeset conversion, and the only way in lifelines
3446
3.0.6, is to edit the embedded character translation tables, in which you
3447
actually specify the letters you want converted, letter by letter, and how
3448
you want them converted. This method, unlike the first, even works in
3449
databases with no specified internal codeset. </para>
3450
3451
<para>
3452
3453
If you choose the modify character translation tables operation from the main menu, <application>LifeLines</application> displays
3454
the character translation menu:
3455
<screen>
3456
Which character mapping do you want to edit?
3457
e Editor to Internal mapping
3458
m Internal to Editor mapping
3459
i GEDCOM to Internal mapping
3460
x Internal to GEDCOM mapping
3461
d Internal to Display mapping
3462
r Internal to Report mapping
3463
q Return to main menu
3464
</screen>
3465
3466
3467
</para>
3468
3469
3470
3471
<para>
3472
3473
<application>LifeLines</application> can do codeset conversion in changing
3474
text from one form to another, and lifelines supports five different
3475
forms.
3476
3477
</para>
3478
3479
3480
3481
<para>
3482
3483
</para>
3484
<glosslist>
3485
<glossentry><glossterm>internal</glossterm><glossdef>
3486
3487
<para>
3488
3489
for records in the database
3490
3491
</para>
3492
</glossdef></glossentry>
3493
3494
<glossentry><glossterm>editor</glossterm><glossdef>
3495
3496
<para>
3497
for records being edited
3498
</para>
3499
</glossdef></glossentry>
3500
3501
<glossentry><glossterm>display</glossterm><glossdef>
3502
3503
<para>
3504
for records being displayed
3505
</para>
3506
</glossdef></glossentry>
3507
3508
<glossentry><glossterm>report</glossterm><glossdef>
3509
3510
<para>
3511
for records written to output file
3512
</para>
3513
</glossdef></glossentry>
3514
3515
<glossentry><glossterm>GEDCOM</glossterm><glossdef>
3516
3517
<para>
3518
for records read in from or written out to GEDCOM
3519
</para>
3520
</glossdef></glossentry>
3521
</glosslist>
3522
3523
3524
<para>
3525
3526
When converting text from one form to another
3527
<application>LifeLines</application> normally uses iconv conversion, and
3528
codesets specified in configuration variables. This may be augmented by
3529
codeset translation or extension using the text conversion (*.tt) files in
3530
the tt subdirectory. To use the tables in the tt subdirectory,
3531
you need to set
3532
the property "TTPATH" in your <application>LifeLines</application>
3533
configuration file to the path of the tt directory. There are two types
3534
of files in this directory.
3535
3536
</para>
3537
<para>
3538
3539
Files of the form <codeset>_<codeset1>.tt convert from one
3540
codeset to another. For example, CP1250_UTF-8.tt can be used to convert
3541
characters in codeset CP1250 to their representations in UTF-8.
3542
3543
</para>
3544
<para>
3545
3546
Files of the form <codeset>__<subcodeset>.tt apply a
3547
conversion within the codeset, for example, UTF-8__html.tt is a
3548
sub-conversion that converts UTF-8 characters that have special escape
3549
codes within html to those special codes. For example, specifing the
3550
report codeset to be UTF-8//html will apply the html sub-conversion to
3551
all the data being written. Probably not what you really wanted.
3552
See the report language function convertcode() in the reportmanual for
3553
details.
3554
3555
</para>
3556
<para>
3557
3558
If your system lacks iconv, or you need more specialized
3559
conversion than provided with iconv, you may either write a text
3560
conversion file (a tt file), or you may edit one of the in-database
3561
translation tables.
3562
3563
</para>
3564
<para>
3565
3566
The in-database translation tables convert between forms (as listed
3567
above). Every translation table converts either to the internal form, or
3568
from the internal form. That is, the internal form is used as an
3569
intermediate step in all operations. There are six supported translation
3570
tables. The following table shows the six tables and describes when they
3571
are applied:
3572
3573
</para>
3574
3575
<glosslist>
3576
<glossentry><glossterm>internal to editor</glossterm><glossdef>
3577
3578
<para>
3579
when converting from internal, database form to editor form
3580
</para>
3581
</glossdef></glossentry>
3582
3583
<glossentry><glossterm>editor to internal</glossterm><glossdef>
3584
3585
<para>
3586
when converting from editor form back to internal, database form
3587
</para>
3588
</glossdef></glossentry>
3589
3590
<glossentry><glossterm><acronym>GEDCOM</acronym> to internal</glossterm><glossdef>
3591
3592
<para>
3593
when reading <acronym>GEDCOM</acronym> input records and writing them to
3594
database
3595
</para>
3596
</glossdef></glossentry>
3597
3598
<glossentry><glossterm>internal to <acronym>GEDCOM</acronym></glossterm><glossdef>
3599
3600
<para>
3601
when writing internal database records to external <acronym>GEDCOM</acronym> file
3602
</para>
3603
3604
</glossdef></glossentry>
3605
<glossentry><glossterm>internal to display</glossterm><glossdef>
3606
3607
<para>
3608
when displaying a record in a browsing mode display screen
3609
</para>
3610
</glossdef></glossentry>
3611
3612
<glossentry><glossterm>internal to report</glossterm><glossdef>
3613
3614
<para>
3615
when writing internal database records to external report file
3616
</para>
3617
</glossdef></glossentry>
3618
</glosslist>
3619
3620
<para>
3621
3622
After you select a translation table you are placed in the editor to edit the table. Translation tables are
3623
made up of lines that look like:
3624
<synopsis><replaceable>pattern</replaceable> <replaceable>pattern</replaceable></synopsis>
3625
where a tab separates the patterns. Each pattern is an arbitrary sequence of verbatim <acronym>ASCII</acronym> characters
3626
and escape sequences. Translation occurs by finding all occurrences that match left patterns and
3627
replacing them with the corresponding right patterns.
3628
3629
</para>
3630
3631
3632
3633
<para>
3634
There are five escape mechanisms used in patterns:
3635
</para>
3636
3637
<glosslist>
3638
<glossentry><glossterm>#nnn</glossterm><glossdef>
3639
3640
<para>
3641
nnn is a decimal character value
3642
</para>
3643
</glossdef></glossentry>
3644
3645
<glossentry><glossterm>$hh</glossterm><glossdef>
3646
3647
<para>
3648
hh is a hexadecimal character value
3649
</para>
3650
</glossdef></glossentry>
3651
3652
<glossentry><glossterm>\ #</glossterm><glossdef>
3653
<!-- note above has extra space between \ and # - without this
3654
conversion to pdf gets confused openjade does some tex processing...
3655
-->
3656
3657
<para>
3658
represents the # character
3659
</para>
3660
</glossdef></glossentry>
3661
3662
<glossentry><glossterm>\$</glossterm><glossdef>
3663
3664
<para>
3665
represents the $ character
3666
</para>
3667
</glossdef></glossentry>
3668
3669
<glossentry><glossterm>\\</glossterm><glossdef>
3670
<para>
3671
represents the \ character
3672
</para>
3673
</glossdef></glossentry>
3674
</glosslist>
3675
3676
<para>
3677
3678
It is possible, and desirable, to provide a short name for
3679
the translation table, using the "##!name: " command. An
3680
example would be
3681
3682
</para>
3683
3684
<programlisting>
3685
##!name: UTF-8 to latex
3686
</programlisting>
3687
3688
<para>
3689
3690
Naming the translation table is desirable because these
3691
names are displayed, at least in part and if they fit, on
3692
the translation table menu.
3693
3694
</para>
3695
3696
<para>
3697
3698
It is possible to format the file using a character other than
3699
tab as the separator between source and destination code. To do
3700
requires using the "##!sep" command. Those exact six characters
3701
must begin the line, and then the next character is the new
3702
separator for all following lines. For clarity, this should only
3703
occur once, and near the top of the file before any actual
3704
translation lines, and a fairly clear separator should be used
3705
(e.g., the equal sign "=").
3706
3707
</para>
3708
3709
<para>
3710
3711
Any line which is blank, or which begins with two hash marks (##), is
3712
ignored. Therefore, comments begin with two hash marks.
3713
3714
</para>
3715
3716
<para>
3717
3718
For advanced users, it is possible to mix different types of
3719
conversion, for example iconv conversion and also translation
3720
table conversion, in the same form step. For example, it is possible
3721
to convert internal database text (internal form) first via the
3722
"internal to GEDCOM" in-database translation table, and then via
3723
the iconv conversion from configured internal codeset to configured
3724
GEDCOM codeset. In-database translation tables are always applied
3725
in the internal codeset, so when converting to the internal form,
3726
they are applied after iconv and/or tt conversions, and when
3727
converting from internal form, they are applied first.
3728
3729
</para>
3730
3731
<para>
3732
3733
An example of adding a mixin in-database translation table might
3734
be to escape certain characters which are control characters
3735
to an output computer language, e.g., latex. One could create an
3736
"Internal to Report" mapping in UTF-8 (if the database is internally
3737
UTF-8) to escape any characters that may occur in place names or
3738
textual descriptions and inadvertently cause grief in latex
3739
processing.
3740
3741
</para>
3742
3743
<para>
3744
3745
However, in this case, one could also write a tt file to achieve
3746
the same results, and be shared across databases, by naming it, eg,
3747
UTF-8__latex.tt. The double underscore ("__") signifies that this
3748
is a conversion to be applied to text which is in UTF-8, and to
3749
trigger lifelinesn to use this, one must specify a report codeset
3750
such as "UTF-8//latex" (if UTF-8 output is desired, but with the
3751
latex conversion first applied), or "ISO-8859-1//latex" (if
3752
ISO-8859-1 output is desired, but with the latex conversion first
3753
applied).
3754
3755
</para>
3756
3757
</sect1>
3758
3759
3760
3761
<sect1>
3762
3763
<title>
3764
3765
MISCELLANEOUS UTILITIES
3766
3767
</title>
3768
3769
3770
3771
<para>
3772
3773
If you choose the miscellaneous utilities operation,
3774
<application>LifeLines</application> displays the utilities menu:
3775
<screen>
3776
What utility do you want to perform?
3777
s Save the database in a GEDCOM file
3778
r Read in data from a GEDCOM file
3779
R Pick a GEDCOM file and read in
3780
k Find a person's key value
3781
i Identify a person from key value
3782
d Show database statistics
3783
m Show memory statistics
3784
e Edit the place abbreviation file
3785
o Edit the user options file
3786
c Character set options
3787
q Return to the main menu
3788
</screen>
3789
3790
3791
</para>
3792
3793
3794
<glosslist>
3795
<glossentry><glossterm><keycap>s</keycap> <action>Save the database in a GEDCOM file.</action></glossterm><glossdef>
3796
<para>
3797
3798
This command saves the complete <application>LifeLines</application> database in a
3799
<acronym>GEDCOM</acronym> file. All person, family, event, source and user-defined records are stored. This command
3800
may be used to periodically back up your database. When you use this command, <application>LifeLines</application> asks you
3801
for the name of the file. If you have defined the <envar>LLARCHIVE</envar> shell variable, <application>LifeLines</application> will store
3802
the file in the directory named in the variable.
3803
3804
</para>
3805
3806
</glossdef></glossentry><glossentry><glossterm><keycap>r</keycap> <action>Read in data from a GEDCOM file.</action></glossterm><glossdef>
3807
3808
<para>
3809
3810
This command allows you restore a complete database from a
3811
<acronym>GEDCOM</acronym> file. When you select this command, <application>LifeLines</application> asks you for the name of the <acronym>GEDCOM</acronym> file.
3812
This command can also be used to import data from a <acronym>GEDCOM</acronym> file to an existing database. When
3813
<application>LifeLines</application> performs this command, it first reads the entire <acronym>GEDCOM</acronym> file and checks it for validity.
3814
If there are problems in the file, <application>LifeLines</application> describes them, writing them to the file err.log, and does
3815
not add any records to the database. If there are no problems, <application>LifeLines</application> adds all the records found in
3816
the file to the database (only header and trailer records are not stored in the database).
3817
3818
</para>
3819
<para>
3820
Normally, <application>LifeLines</application> will replace the XREF's (the
3821
identifiers for individuals, families, sources, notes, etc.) in the
3822
<acronym>GEDCOM</acronym> with it's own.
3823
These identifiers are reserved by the <acronym>GEDCOM</acronym> for internal
3824
use of genealogy programs. However, if the identifiers are compatible with
3825
<application>LifeLines</application> internal representation and there are no
3826
conflicts with existing identifiers, <application>LifeLines</application> will
3827
ask you if you want to perserve the identifiers in the
3828
<acronym>GEDCOM</acronym>
3829
file rather than assign new values.
3830
</para>
3831
</glossdef></glossentry>
3832
3833
<glossentry><glossterm><keycap>k</keycap> <action>Find a person's key value.</action></glossterm><glossdef>
3834
3835
<para>
3836
3837
This command finds the internal key value of a person.
3838
3839
</para>
3840
3841
</glossdef></glossentry><glossentry><glossterm><keycap>i</keycap> <action>Identify a person from key value.</action></glossterm><glossdef>
3842
3843
<para>
3844
3845
This command identifies the person that has a particular internal
3846
key value.
3847
3848
</para>
3849
</glossdef></glossentry>
3850
3851
<glossentry><glossterm><keycap>d</keycap> <action>Show database statistics.</action></glossterm><glossdef>
3852
3853
<para>
3854
3855
This command summarizes the contents of the current database. It
3856
displays the number of person, family, source, event and other records in the database.
3857
3858
</para>
3859
</glossdef></glossentry>
3860
3861
<glossentry><glossterm><keycap>m</keycap> <action>Show memory statistics.</action></glossterm><glossdef>
3862
3863
<para>
3864
3865
This command is used by the author for debugging.
3866
3867
</para>
3868
</glossdef></glossentry>
3869
3870
<glossentry><glossterm><keycap>e</keycap> <action>Edit the place abbreviation file.</action></glossterm><glossdef>
3871
3872
<para>
3873
3874
This command allows you to edit the place abbreviations
3875
file. This file defines the abbreviations that are used by
3876
<application>LifeLines</application> when it creates lists of
3877
persons for you to select from. Each line in the file has the
3878
format:<synopsis><replaceable>word</replaceable>:<replaceable>
3879
abbr </replaceable></synopsis>where word is a word to be
3880
abbreviated, and abbr is its abbreviation. The word and its
3881
abbreviation are separated by a colon. For example:
3882
3883
<example>
3884
3885
<title>
3886
Example of using abbreviations
3887
</title>
3888
3889
<literallayout>Connecticut:Conn.
3890
Massachusetts:Mass.
3891
Nova Scotia:N.S.</literallayout></example>
3892
3893
</para>
3894
3895
3896
3897
<para>
3898
3899
When <application>LifeLines</application> constructs lists of persons for you to select from, it looks up the last component of
3900
certain <structfield>PLAC</structfield> lines in this file, and if it finds that component, replaces it with its abbreviation.
3901
3902
</para>
3903
</glossdef></glossentry>
3904
3905
<glossentry><glossterm><keycap>o</keycap>
3906
<action>Edit the user options file.</action>
3907
</glossterm><glossdef>
3908
3909
<para>
3910
3911
This command allows you to edit the user options file. The user options file
3912
is a record kept in the database that holds user selectable options. Each
3913
option has a name and a string value. Each line in the options file has the
3914
format:<synopsis><replaceable>option</replaceable>=<replaceable>value</replaceable></synopsis>
3915
where option is the name of an option and value is the option's string value.
3916
If the value is more than one line long, then the last character in each
3917
non-final line must be a backslash. The escapes \n and \t are also recognized
3918
in version 3.0.7 and better (to represent a carriage return and a tab, respectively).
3919
These (\n and \t) are primarily for use in custom record templates.
3920
In version 3.0.14 there are 39 options. Note that all of these may also be specified in
3921
the configuration file, to apply to all databases, but if specified in
3922
both places, the entry in the database (user options table) governs.
3923
For more information, see the sample configuration file; each option is preceded
3924
by a brief explanation.
3925
3926
</para>
3927
3928
<para>
3929
The list of options can be found in the section 'System and User Properties'
3930
below.
3931
</para>
3932
</glossdef></glossentry>
3933
</glosslist>
3934
3935
<para>
3936
3937
For example if you would like to replace the default person
3938
record template with the following:
3939
3940
<example>
3941
3942
<title>
3943
Example of replacing the default person record template
3944
</title>
3945
3946
<programlisting>
3947
3948
0 INDI
3949
1 NAME //
3950
1 SEX</programlisting></example>
3951
you would edit the user option file to contain:<example>
3952
3953
<title>
3954
Example of replaced default person record template
3955
</title>
3956
3957
<literallayout>INDIREC=0 INDI\
3958
1 NAME //\
3959
1 SEX</literallayout>
3960
</example>
3961
3962
or, using the \n escape so as to keep the entry on one line:<example>
3963
3964
<title>
3965
Example of replaced single line default person record template
3966
</title>
3967
3968
<literallayout>INDIREC=0 INDI\n1 NAME //\n1 SEX</literallayout>
3969
</example>
3970
3971
</para>
3972
3973
<glosslist>
3974
<glossentry><glossterm><keycap>q</keycap> <action>Return to main menu.</action></glossterm><glossdef>
3975
3976
<para>
3977
This command returns you to the main menu.
3978
</para>
3979
3980
</glossdef></glossentry>
3981
</glosslist>
3982
3983
3984
</sect1>
3985
3986
<sect1>
3987
3988
<title>
3989
IMPORT ERRORS
3990
</title>
3991
3992
<para>
3993
Errors generated during a GEDCOM import are logged to a file,
3994
by default named errs.log.
3995
</para>
3996
<para>
3997
A number of errors are related to having an incorrect XREF value.
3998
An XREF is the internal name used to Identify a family, individual, note,
3999
source or other record. An XREF is bracked by two @ signs. As an example
4000
</para>
4001
<programlisting> 0 @F6@ FAM
4002
1 HUSB @I25@
4003
1 WIFE @I26@
4004
1 CHIL @I17@</programlisting>
4005
<para>
4006
Here F6 is the internal name of this family. The family refers
4007
to other individuals by specifing their XREF values. Also I25, I26 and I17
4008
are XREF values of individuals.
4009
</para>
4010
<para>
4011
XREF values used within <application>LifeLines</application> are totally under
4012
the control of <application>LifeLines</application>.
4013
The values that are used are always of the form, a single letter, followed by
4014
a number. However, when importing a gedcom
4015
<application>LifeLines</application> should accept almost
4016
anything as an XREF, converting it to what is needed for internal use.
4017
For the curious, the letters that <application>LifeLines</application> uses
4018
are I for Individual, F for Family, S for Source, E for Events, and X for
4019
other records.
4020
4021
</para>
4022
<glosslist><glossentry><glossterm>Bad NAME syntax.</glossterm><glossdef>
4023
4024
<para>
4025
4026
A level 1 NAME record must have a value, and the value must not be a pointer, and may
4027
have no more than two slashes.
4028
</para>
4029
4030
<example><title>
4031
Example of bad NAME syntax (too many slashes in this case)
4032
</title>
4033
<programlisting> 0 @I99@ INDI
4034
1 NAME Mary /Smith/ nee /Jones/
4035
</programlisting></example>
4036
4037
</glossdef></glossentry><glossentry>
4038
<glossterm>Family F13 has an incorrect key.</glossterm>
4039
<glossdef><para></para></glossdef></glossentry>
4040
<glossentry>
4041
<glossterm>Person XYZ has an incorrect key: skipped.</glossterm>
4042
<glossdef>
4043
4044
<para>
4045
4046
The XREF values must be unique. These error messages are
4047
generated if a XREF is found to refer to two different records.
4048
For example, the XREF for a family is the same as one for an individual.
4049
4050
</para>
4051
4052
<example><title>
4053
Example of XREF XYZ being defined twice
4054
</title>
4055
<programlisting> 0 @XYZ@ INDI
4056
1 NAME Mary /Smith/ nee /Jones/
4057
0 @XYZ@ FAM
4058
1 HUSB @I48@
4059
</programlisting></example>
4060
4061
</glossdef></glossentry><glossentry><glossterm>Person defined here has no name.</glossterm><glossdef>
4062
4063
<para>
4064
4065
Each INDI record must have at least one level 1 NAME record, if the
4066
configuration option RequireNames is non-zero.
4067
4068
</para>
4069
4070
</glossdef></glossentry><glossentry><glossterm>Person INDI_XYZ is multiply defined: skipped.</glossterm><glossdef>
4071
4072
<para>
4073
4074
No XREF value of an INDI may be reused. This message indicates that
4075
INDI_XYZ has been used to identify two different persons.
4076
4077
</para>
4078
4079
<example><title>
4080
Example of person multiply defined
4081
</title>
4082
<programlisting> 0 @INDI_XYZ@ INDI
4083
1 NAME John /Smith/
4084
0 @INDI_XYZ@ INDI
4085
1 NAME Jack /Smith/
4086
</programlisting></example>
4087
4088
</glossdef></glossentry><glossentry><glossterm>The family defined here has no key.</glossterm><glossdef>
4089
4090
<para>
4091
4092
Each FAM record must have an XREF value.
4093
(The XREF is the letters between "0" and "FAM".)
4094
4095
</para>
4096
4097
<example><title>
4098
Example of family record missing key
4099
</title>
4100
<programlisting> 0 FAM
4101
1 HUSB @I1@
4102
</programlisting></example>
4103
4104
</glossdef></glossentry><glossentry><glossterm>Family F123 is referred to but
4105
not defined.</glossterm><glossdef>
4106
4107
<para>
4108
4109
A FAMS or FAMC record on an Individual refers to a family
4110
but there is no FAM record with that XREF.
4111
4112
</para>
4113
4114
</glossdef></glossentry><glossentry><glossterm>The person defined here has no key: skipped.</glossterm><glossdef>
4115
4116
<para>
4117
4118
Each INDI record must have an XREF value.
4119
(The XREF is the letters between "0" and "INDI".)
4120
4121
</para>
4122
4123
<example><title>
4124
Example of person record missing key
4125
</title>
4126
<programlisting> 0 INDI
4127
1 NAME John /Smith/
4128
</programlisting></example>
4129
4130
</glossdef></glossentry><glossentry><glossterm>This line has a level number that is too large.</glossterm><glossdef>
4131
4132
<para>
4133
4134
A child level must be one higher than its parent level.
4135
4136
</para>
4137
4138
<example><title>
4139
Example of level number which is too high
4140
</title>
4141
<programlisting> 0 @I99@ INDI
4142
1 NAME //
4143
3 NOTE name is missing
4144
</programlisting></example>
4145
4146
</glossdef></glossentry><glossentry><glossterm>This FAMS line is missing a
4147
value field (INDI I99).</glossterm><glossdef>
4148
4149
<para>
4150
4151
Lineage-linking tags must have a value, including tags FAMC, FAMS, FATH, MOTH, HUSB, WIFE, CHIL.
4152
4153
</para>
4154
4155
<example><title>
4156
Example of lineage-linking line which is missing required value
4157
</title>
4158
<programlisting> 0 @I99@ INDI
4159
1 NAME John /Smith/
4160
2 FAMS
4161
</programlisting></example>
4162
4163
</glossdef></glossentry></glosslist>
4164
4165
</sect1>
4166
4167
<sect1>
4168
4169
4170
4171
<title>
4172
4173
HANDLING SOURCE, EVENT AND USER-DEFINED RECORDS
4174
4175
</title>
4176
4177
4178
4179
<para>
4180
4181
<application>LifeLines</application> supports source, event
4182
and other, user-defined record types. You can access these
4183
features in two ways: either through the x operation from the
4184
main menu, or via commands in the individual and family browse
4185
screens. The first approach might be most convenient when you
4186
are solely working with these record types. The second makes
4187
it easier to work with source, event and user-defined records
4188
in parallel with your person and family records; this can be
4189
useful for instance when you want to create references from
4190
your person and family record to your source, event and user
4191
defined records as you create them, and to view and edit
4192
records that you have referenced from within a person or
4193
family record.
4194
4195
</para>
4196
4197
<para>
4198
4199
Using the first of these two possibilities
4200
<application>LifeLines</application> displays the following
4201
menu:
4202
4203
<screen>
4204
What activity do you want to perform?
4205
4206
s Browse source records
4207
e Browse event records
4208
x Browse other records
4209
1 Add a source record to the database
4210
2 Edit source record from the database
4211
3 Add an event record to the database
4212
4 Edit event record from the database
4213
5 Add an other record to the database
4214
6 Edit other record from the database
4215
q Return to main menu
4216
</screen>
4217
4218
Using the second variant (from the person and family browse
4219
screens), the following six commands are available. The first
4220
three are described alongside with their counterparts in the x
4221
menu (they do mostly, but not entirely, the same things); the
4222
last three are described separately:
4223
4224
<screen>
4225
%s Add source
4226
%e Add event
4227
%o Add other
4228
</screen>
4229
4230
<screen>
4231
$s List sources
4232
$n List notes
4233
$$ List references
4234
</screen>
4235
4236
</para>
4237
4238
4239
4240
<para>
4241
4242
The handling of source, event and user-defined records in
4243
<application>LifeLines</application> is still in
4244
development. For example, sources cannot yet be searched by
4245
REFN or be deleted.
4246
4247
</para>
4248
4249
<glosslist><glossentry><glossterm><keycap>s</keycap>
4250
<action>Browse source records.</action></glossterm><glossdef>
4251
4252
<para>
4253
This will bring up a list of all source records by number, showing
4254
REFN, title, and author for each. A record may be selected
4255
from this list to edit.
4256
</para>
4257
4258
</glossdef></glossentry><glossentry><glossterm><keycap>e</keycap>
4259
<action>Browse event records.</action></glossterm><glossdef>
4260
4261
<para>
4262
This will bring up a list of all event records by number. As of
4263
yet this does not display any information about each event.
4264
(Suggestions as to how to summarize events are welcome).
4265
A record may be selected from this list to edit.
4266
</para>
4267
4268
</glossdef></glossentry><glossentry><glossterm><keycap>x</keycap>
4269
<action>Browse other records.</action></glossterm><glossdef>
4270
4271
<para>
4272
This will bring up a list of all other records by number,
4273
showing the 0 level line as summary. A record may be selected
4274
from this list to edit.
4275
</para>
4276
4277
</glossdef></glossentry><glossentry><glossterm><keycap>1</keycap>
4278
<action>Add a source record to the
4279
database.</action></glossterm><glossdef>
4280
4281
<para>
4282
4283
This operation (or alternatively <keycap>%s</keycap> from the
4284
person, family or auxiliary browse screens) is used to add a
4285
new source record to the database.
4286
<application>LifeLines</application> creates a template source
4287
and puts you in the screen editor to edit the template. The
4288
default template is:
4289
4290
<programlisting> 0 SOUR
4291
1 REFN
4292
1 TITL <replaceable>Title</replaceable>
4293
1 AUTH <replaceable>Author</replaceable>
4294
4295
</programlisting>
4296
4297
</para>
4298
4299
4300
4301
<para>
4302
4303
Do not change the <structfield>0 SOUR</structfield>
4304
line. Otherwise you may edit this record any way you like. The
4305
<structfield>1 REFN</structfield> line is a special line you
4306
can use to give the source a symbolic name that can be used in
4307
other records to refer to the source record. See the section
4308
on using <structfield>REFN</structfield> values. Because many
4309
sources have a title and an author, the default template has
4310
these lines. You may adjust the source template via the
4311
SOURREC user option (either at the database level, via the
4312
user options, or globally, via the configuration file). Here
4313
is how I recorded one of the sources in my database:
4314
4315
<example>
4316
4317
<title>
4318
Example of a source record
4319
</title>
4320
4321
<programlisting>0 SOUR
4322
1 REFN <userinput>jcw</userinput>
4323
1 TITL <userinput>The Wetmore Family of America, and its Collateral Branches: with</userinput>
4324
2 CONT <userinput>Genealogical, Biographical, and Historical Notices</userinput>
4325
1 AUTH <userinput>James Carnahan Wetmore</userinput>
4326
1 PUBL
4327
2 DATE <userinput>1861</userinput>
4328
2 PLAC <userinput>Albany, New York</userinput>
4329
2 INST <userinput>Munsell and Rowland</userinput>
4330
2 ADDR <userinput>78 State Street</userinput></programlisting></example>
4331
4332
</para>
4333
4334
<para>
4335
4336
The add source command in the x menu is equivalent to the
4337
<keycap>%s</keycap> command available in the person or family
4338
browse screen, in terms of entering the source record; after
4339
saving the source record though, there is one significant
4340
difference, in that that you then are presented with the
4341
following prompt (also, the key value of the new record is
4342
displayed in the status bar at this point):
4343
</para>
4344
4345
<screen>
4346
Please choose from the following options:
4347
1: Insert xref automatically at bottom of current record.
4348
2: Edit current record now to add xref manually.
4349
3: Browse new record (without adding xref).
4350
4: Return to current record (without adding xref).
4351
4352
Commands: j Move down k Move up i Select q Quit
4353
</screen>
4354
4355
<para>
4356
4357
The four options perform the following actions:
4358
4359
</para>
4360
4361
<para>
4362
4363
1: LifeLines adds a reference to the new source record at the
4364
bottom of the person or family record that was visible in the
4365
display screen when you prompted LifeLines to create the new
4366
source record.
4367
4368
</para>
4369
4370
<para>
4371
4372
2: LifeLines will open the person or family record that was
4373
visible in the display screen when you prompted LifeLines to
4374
create the new source record, so that you can manually enter a
4375
reference to the newly created source record (perhaps as a
4376
source reference to an event that you are planning to add).
4377
4378
</para>
4379
4380
<para>
4381
4382
3: LifeLines lets you browse (and optionally reopen for
4383
editing) your newly added source record.
4384
4385
</para>
4386
4387
<para>
4388
4389
4: You are returned to the person or family record that was
4390
visible in the display screen when you prompted LifeLines to
4391
create the new source record. No reference is added to the new
4392
record.
4393
4394
</para>
4395
4396
</glossdef></glossentry><glossentry><glossterm><keycap>2</keycap> <action>Edit source record from the database.</action></glossterm>
4397
<glossdef>
4398
4399
<para>
4400
4401
Use this operation to edit an existing source record already in
4402
the database. When you select this operation
4403
<application>LifeLines</application> asks you to identify a source:
4404
<screen>
4405
Which source record do you want to edit?
4406
enter key or refn:
4407
</screen>
4408
4409
4410
</para>
4411
4412
4413
4414
<para>
4415
4416
Identify a source by entering its key value, with or without the leading S, or by entering its <structfield>REFN</structfield>
4417
value. <application>LifeLines</application> retrieves the record and puts you in the editor with the record.
4418
4419
</para>
4420
4421
</glossdef></glossentry><glossentry><glossterm><keycap>3</keycap> <action>Add an event record to the database.</action></glossterm><glossdef>
4422
4423
<para>
4424
4425
This operation (or alternatively <keycap>%e</keycap> from the person,
4426
family or auxiliary browse screens) adds a new event record to the
4427
database. <application>LifeLines</application> creates a template
4428
event and puts you in the screen editor to edit the template. The
4429
default template is:
4430
<programlisting>0 EVEN
4431
1 REFN
4432
1 DATE
4433
1 PLAC
4434
1 INDI
4435
2 NAME
4436
2 ROLE
4437
1 SOUR</programlisting>
4438
4439
</para>
4440
4441
<para>
4442
4443
You may adjust the event template via the EVENREC user option (either
4444
at the database level, via the user options, or globally, via the
4445
configuration file).
4446
4447
</para>
4448
4449
<para>
4450
4451
Do not change the <structfield>0 EVEN</structfield>
4452
line. Otherwise you may edit this record any way you like. The
4453
<structfield>1 REFN</structfield> line allows you to give this
4454
event a symbolic name you can use when you want to refer to
4455
this event from other records. See the section on using
4456
<structfield>REFN</structfield> values. The default template
4457
suggests that an event has a date, a place, and refers to
4458
persons in roles with respect to the event. There is far less
4459
experience with event-based <acronym>GEDCOM</acronym> than
4460
there is with simple person and family
4461
<acronym>GEDCOM</acronym>. You may even be wondering why you
4462
would need event records when you can simply tuck events away
4463
in person and family records. This is a topic that may get
4464
covered in an appendix.
4465
4466
</para>
4467
4468
<para>
4469
4470
The add event command in the x menu is equivalent to the
4471
<keycap>%e</keycap> command available in the person or family
4472
browse screen, in terms of entering the event record; after
4473
saving the event record though, there is one significant
4474
difference, in that that you then are presented with the
4475
following prompt (also, the key value of the new record is
4476
displayed in the status bar at this point):
4477
</para>
4478
4479
<screen>
4480
Please choose from the following options:
4481
1: Insert xref automatically at bottom of current record.
4482
2: Edit current record now to add xref manually.
4483
3: Browse new record (without adding xref).
4484
4: Return to current record (without adding xref).
4485
4486
Commands: j Move down k Move up i Select q Quit
4487
</screen>
4488
4489
<para>
4490
4491
The four options perform the following actions:
4492
4493
</para>
4494
4495
<para>
4496
4497
1: LifeLines adds a reference to the new event record at the
4498
bottom of the person or family record that was visible in the
4499
display screen when you prompted LifeLines to create the new
4500
event record.
4501
4502
</para>
4503
4504
<para>
4505
4506
2: LifeLines will open the person or family record that was
4507
visible in the display screen when you prompted LifeLines to
4508
create the new event record, so that you can manually enter a
4509
reference to the newly created event record.
4510
4511
</para>
4512
4513
<para>
4514
4515
3: LifeLines lets you browse (and optionally reopen for
4516
editing) your newly added event record.
4517
4518
</para>
4519
4520
<para>
4521
4522
4: You are returned to the person or family record that was
4523
visible in the display screen when you prompted LifeLines to
4524
create the new event record. No reference is added to the new
4525
record.
4526
4527
</para>
4528
4529
</glossdef></glossentry><glossentry><glossterm><keycap>4</keycap> <action>Edit event record from the database.</action></glossterm><glossdef>
4530
4531
<para>
4532
4533
Use this operation to edit an existing event record from the
4534
database . When you select this operation
4535
<application>LifeLines</application> asks you to identify an
4536
event:
4537
4538
<screen>
4539
Which event record do you want to edit?
4540
enter key or refn:
4541
</screen>
4542
4543
4544
</para>
4545
4546
4547
4548
<para>
4549
4550
You identify a event by entering its key value, with or
4551
without the leading E, or by entering its
4552
<structfield>REFN</structfield>
4553
value. <application>LifeLines</application> retrieves the
4554
record and places you in the screen editor with the record.
4555
4556
</para>
4557
4558
</glossdef></glossentry><glossentry><glossterm><keycap>5</keycap> <action>Add an other record to the database.</action></glossterm><glossdef>
4559
4560
<para>
4561
4562
This operation (or alternatively <keycap>%o</keycap> from the
4563
person, family or auxiliary browse screens) adds a new
4564
user-defined record to the database.
4565
<application>LifeLines</application> creates a template and
4566
puts you in the screen editor to edit the template. The
4567
default template is
4568
4569
<programlisting>0 XXXX
4570
1 REFN
4571
</programlisting>
4572
</para>
4573
4574
4575
4576
<para>
4577
4578
Replace <replaceable>XXXX</replaceable> with the tag string
4579
you select for the type of the new record. You are free to
4580
choose any tag value except <structfield>INDI</structfield>,
4581
<structfield>FAM</structfield>,
4582
<structfield>SOUR</structfield> and
4583
<structfield>EVEN</structfield>. For example, if you keep
4584
record information about the ships that your North American
4585
immigrant ancestors arrived on, you would keep records about
4586
those ships in your database; the tag
4587
<structfield>SHIP</structfield> suggests itself for such
4588
records. The <structfield>1 REFN</structfield> line allows you
4589
to give this record a symbolic name you can use when you want
4590
to refer to it from other records. See the section on using
4591
<structfield>REFN</structfield> values. You may adjust the
4592
other template via the OTHR user option (either at the database
4593
level, via the user options, or globally, via the configuration
4594
file).
4595
4596
</para>
4597
4598
<para>
4599
4600
The add other record command in the x menu is equivalent to the
4601
<keycap>%o</keycap> command available in the person or family
4602
browse screen, in terms of entering the other record; after
4603
saving the record though, there is one significant difference,
4604
in that that you then are presented with the following prompt
4605
(also, the key value of the new record is displayed in the
4606
status bar at this point):
4607
</para>
4608
4609
<screen>
4610
Please choose from the following options:
4611
1: Insert xref automatically at bottom of current record.
4612
2: Edit current record now to add xref manually.
4613
3: Browse new record (without adding xref).
4614
4: Return to current record (without adding xref).
4615
4616
Commands: j Move down k Move up i Select q Quit
4617
</screen>
4618
4619
<para>
4620
4621
The four options perform the following actions:
4622
4623
</para>
4624
4625
<para>
4626
4627
1: LifeLines adds a reference to the new other record at the
4628
bottom of the person or family record that was visible in the
4629
display screen when you prompted LifeLines to create the new
4630
other record.
4631
4632
</para>
4633
4634
<para>
4635
4636
2: LifeLines will open the person or family record that was
4637
visible in the display screen when you prompted LifeLines to
4638
create the new other record, so that you can manually enter a
4639
reference to the newly created other record (perhaps as a
4640
note reference to an event that you are planning to add).
4641
4642
</para>
4643
4644
<para>
4645
4646
3: LifeLines lets you browse (and optionally reopen for
4647
editing) your newly added other record.
4648
4649
</para>
4650
4651
<para>
4652
4653
4: You are returned to the person or family record that was
4654
visible in the display screen when you prompted LifeLines to
4655
create the new other record. No reference is added to the new
4656
record.
4657
4658
</para>
4659
4660
</glossdef></glossentry><glossentry><glossterm><keycap>6</keycap> <action>Edit other record from the database.</action></glossterm><glossdef>
4661
4662
<para>
4663
4664
Use this operation to edit an existing user-defined record
4665
from the database. When you select this operation
4666
<application>LifeLines</application> asks you to identify the
4667
record:
4668
4669
<screen>
4670
What record do you want to edit?
4671
enter key or refn:
4672
</screen>
4673
4674
4675
</para>
4676
4677
<para>
4678
4679
You identify a record by entering its key value, with or
4680
without the leading X, or by entering its
4681
<structfield>REFN</structfield>
4682
value. <application>LifeLines</application> retrieves the
4683
record and places you in the screen editor with the record.
4684
4685
</para>
4686
4687
</glossdef></glossentry><glossentry><glossterm><keycap>$s</keycap>
4688
<action>List sources</action></glossterm><glossdef>
4689
4690
<para>
4691
4692
This command is available in the person and family browse
4693
screens. It will bring up a list of all source records that
4694
are referenced within the currently displayed person or family
4695
record, by the order they appear in the person/family record,
4696
showing REFN, title, and author for each. A record may be
4697
selected from this list to view in the auxiliary browse screen
4698
(and optionally be edited from there).
4699
4700
</para>
4701
4702
4703
</glossdef></glossentry><glossentry><glossterm><keycap>$n</keycap>
4704
<action>List notes</action></glossterm><glossdef>
4705
4706
<para>
4707
4708
This command is available in the person and family browse
4709
screens. It will bring up a list of all note records that are
4710
referenced within the currently displayed person or family
4711
record, by the order they appear in the person/family record,
4712
showing REFN, title, and author for each. A record may be
4713
selected from this list to view in the auxiliary browse screen
4714
(and optionally be edited from there).
4715
4716
</para>
4717
4718
</glossdef></glossentry><glossentry><glossterm><keycap>$$</keycap>
4719
<action>List all references</action></glossterm><glossdef>
4720
4721
<para>
4722
4723
This command is available in the person and family browse
4724
screens. It will bring up a list of all records that are
4725
referenced within the currently displayed person or family
4726
record, by the order they appear in the person/family record,
4727
showing REFN, title, and author for each. A record may be
4728
selected from this list to view in the auxiliary browse screen
4729
(and optionally be edited from there).
4730
4731
</para>
4732
4733
</glossdef></glossentry></glosslist>
4734
4735
</sect1>
4736
4737
4738
4739
<sect1>
4740
4741
<title>
4742
FAMILY STRUCTURE AND MERGING PERSONS AND FAMILIES
4743
</title>
4744
4745
<para>
4746
4747
<application>LifeLines</application> 3.0.2 has relaxed most of
4748
restrictions on family structure that were imposed by earlier
4749
versions. For example, a family record may have more than one
4750
parent/spouse of the same sex; a person may be a child in more
4751
than family. This is a controversial issue. Some users insist
4752
that family relationships should imply biological relatedness,
4753
and that all other relationships should be handled by
4754
different means. Others insist that non-traditional families
4755
(any number of parents/spouses of any sex) should be allowed,
4756
and that children can be members of more than one family (eg,
4757
natural family and adoptive
4758
family). <application>LifeLines</application> no longer takes
4759
a position on this matter; you are free to set up families any
4760
way you like; the operations that add spouses and children to
4761
families no longer check for non-traditional arrangements. It
4762
is possible that a future release will include a user option
4763
to either disallow or to ask for confirmation about
4764
non-traditional relationships.
4765
4766
</para>
4767
4768
4769
4770
<para>
4771
4772
<application>LifeLines</application> provides features for
4773
merging persons together and for merging families
4774
together. The person merging feature is accessed from the
4775
tandem person browse mode, and the family merging feature is
4776
accessed from the tandem family browse mode. You browse to the
4777
two persons or families you want to merge and then use the j
4778
command. Merging is necessary when you discover that two or
4779
more person records, or two or more family records, represent
4780
the same person or family, respectively.
4781
4782
</para>
4783
4784
4785
4786
<para>
4787
4788
Versions of <application>LifeLines</application> prior to
4789
3.0.2 required that persons and families meet certain criteria
4790
before they could be merged. The criteria ensured that the
4791
merged persons and families would still meet traditional
4792
family structuring rules. With the relaxation of the
4793
structuring rules, restrictions on merging have also been
4794
removed. It is now possible to create non-traditional
4795
relationships by merging traditional persons and/or
4796
families. For example, if you merge two persons that happen to
4797
be children in two different families, the merged person will
4798
be a child in both families. If you want to maintain only
4799
traditional relationships in your database you may have to
4800
makes further to changes to relationships after you complete a
4801
merge operation.
4802
4803
</para>
4804
4805
4806
4807
</sect1>
4808
4809
4810
4811
<sect1>
4812
4813
4814
4815
<title>
4816
4817
LINKING RECORDS TOGETHER AND USING THE REFN FEATURE
4818
4819
</title>
4820
4821
4822
4823
<para>
4824
4825
Records in a <application>LifeLines</application> database may
4826
refer to other records via cross-reference links. The
4827
lineage-linked references are maintained directly by
4828
<application>LifeLines</application> through operations found
4829
in the browsing mode menus. These references are the links
4830
from a person to families (<structfield>1 FAMC</structfield>
4831
and <structfield>1 FAMS</structfield>), and the links from a
4832
family to persons (<structfield>1 HUSB</structfield>,
4833
<structfield>1 WIFE</structfield> and <structfield>1
4834
CHIL</structfield>). Because
4835
<application>LifeLines</application> maintains these links you
4836
are not allowed to change these lines when you are editing
4837
records. There are a couple of seeming exceptions to this
4838
rule. For example, you may change the order of <structfield>1
4839
CHIL</structfield> lines in a family record in order to change
4840
the order of children in a family, and you may change the
4841
order of <structfield>1 FAMS</structfield> lines in a person
4842
record to change the order of families the person was a spouse
4843
or parent in. These operations are allowed because they don't
4844
affect which person records refer to which family records and
4845
vice versa.
4846
4847
</para>
4848
4849
4850
4851
<para>
4852
4853
Besides the lineage-links that are maintained by
4854
<application>LifeLines</application>, you may place your own
4855
links in records. Probably the most common example of this is
4856
referring events within a person record to the record of the
4857
information source for the event. For example:
4858
4859
4860
<example>
4861
4862
<title>
4863
Example of referring events from a person record
4864
</title>
4865
4866
<programlisting>0 @I23@ INDI
4867
1 NAME <userinput>Thomas/Whitmore/</userinput>
4868
1 BIRT
4869
2 DATE <userinput>about 1615</userinput>
4870
2 PLAC <userinput>England</userinput>
4871
2 SOUR @S3@
4872
...
4873
0 @S3@ SOUR
4874
1 REFN <userinput>cat</userinput>
4875
1 TITL <userinput>New England Marriages Prior to 1700</userinput>
4876
1 AUTH <userinput>Clarence Almon Torrey</userinput>
4877
...</programlisting></example>
4878
4879
</para>
4880
4881
4882
4883
<para>
4884
4885
The <structfield>2 SOUR</structfield> <replaceable>@S3@</replaceable> line in the person record refers to the source record. <application>LifeLines</application> allows any specific
4886
structure within a record (in this case a birth event) to refer to another record. It is not possible to refer
4887
to a specific location within another record, though this may be supported eventually.
4888
4889
4890
</para>
4891
4892
4893
4894
<para>
4895
4896
This example implies that when linking one record to another you must know the key of the target
4897
record (S3 in the example). This is not desirable because internal record keys may change when the
4898
records are exported from one database or imported to another.
4899
4900
</para>
4901
4902
4903
4904
<para>
4905
4906
Because internal key values are not permanent,
4907
<application>LifeLines</application> allows you to assign a
4908
permanent user-defined key to any record in the database using
4909
the <structfield>1 REFN</structfield> line. The value of this
4910
line is a string that you choose as your permanent key value
4911
for the record. When adding a link to a record that has a user
4912
<structfield>REFN</structfield> key value, you may use that
4913
value instead of the internal key value. For example, when
4914
adding the person in the previous example you could edit the
4915
new record as follows:
4916
4917
<example>
4918
4919
<title>
4920
Example of adding a new person
4921
</title>
4922
4923
<programlisting>0 INDI
4924
1 NAME <userinput>Thomas/Whitmore/</userinput>
4925
1 BIRT
4926
2 DATE <userinput>about 1615</userinput>
4927
2 PLAC <userinput>England</userinput>
4928
2 SOUR <userinput><cat></userinput></programlisting></example>
4929
4930
</para>
4931
4932
4933
4934
<para>
4935
4936
Instead of using the actual key value of the source, S3, the
4937
<structfield>REFN</structfield> value cat was used. The
4938
<structfield>REFN</structfield> value must be enclosed by
4939
angle brackets when used this
4940
way. <application>LifeLines</application> automatically
4941
replaces the <structfield>REFN</structfield> link with the
4942
proper internal key value when the record is stored in the
4943
database.
4944
4945
4946
</para>
4947
4948
4949
4950
<para>
4951
4952
The <structfield>REFN</structfield> value may also be used
4953
when searching for person, source, event and user-defined
4954
records. You should not add more than one
4955
<structfield>REFN</structfield> line to a record, and every
4956
<structfield>REFN</structfield> value should be unique.
4957
4958
</para>
4959
4960
</sect1>
4961
4962
4963
<sect1>
4964
4965
4966
4967
<title>
4968
4969
System and User Properties
4970
4971
</title>
4972
4973
<para>
4974
There are a number of properties that can be specified to customize
4975
the behavior of <application>LifeLines</application>. These properties can
4976
be specified in <application>LifeLines</application>
4977
configuration files, in each <application>LifeLines</application> database
4978
or in some cases by environment variables.
4979
</para>
4980
<para>
4981
System Properties are properties that have a predefined meaning to lifelines,
4982
such as LLEDITOR (see its meaning below). User Properties typically have no
4983
predefined meanings as they are simply a string that a report looks up in the
4984
property tables. It can be anything a user desires. To simplify report
4985
writing a number of User Properties are predefined with specific meanings.
4986
These User Property Names begin with 'user.' and are listed below. For
4987
example, many reports have abstracted the concept of the user's name to
4988
the property user.fullname. By defining this property in your llines startup
4989
file, it allows a report to reference your name as the source of the data
4990
being printed without having it hard-coded in the report.
4991
</para>
4992
<para>
4993
When <application>LifeLines</application> begins execution, it reads any
4994
specified configuration files and extracts Properties from the files read.
4995
It is possible for multiple configuration files to be read. Properties
4996
defined in these files will be stored in the global property table. If
4997
multiple definitions of the same property are seen, the latest definition
4998
overrides prior definitions. Configuration files are read as follows:
4999
</para>
5000
5001
<informaltable pgwide='0' frame='none'>
5002
<tgroup cols='2'>
5003
<colspec colwidth='0.5in'></colspec>
5004
<tbody>
5005
<row>
5006
<entry>Note:</entry>
5007
<entry>
5008
If a configuration file defines LLCONFIGFILE, it is not entered in the global
5009
table, but the value of this parameter is read as a configuration file after
5010
completion of reading the current file.
5011
</entry>
5012
</row>
5013
<row>
5014
<entry>Note:</entry>
5015
<entry>
5016
In the following, the name of a user configuration file is listed as
5017
.linesrc. On windows versions of lifelines this name is lines.cfg.
5018
</entry>
5019
</row>
5020
<row>
5021
<entry>1</entry>
5022
<entry>
5023
If a configuration file name is passed to the program with the -C option,
5024
or if LLCONFIGFILE is defined as an environment variable use the value
5025
supplied as the name of the configuration file. Do not read configuration
5026
information from the files listed in 2a, 2b, 2c, or 2d.
5027
</entry>
5028
</row>
5029
<row>
5030
<entry>2a</entry>
5031
<entry>
5032
If the file /etc/lifelines.conf exists, read it. '/etc' is a placeholder for
5033
the standard location for system configuration files as defined when
5034
lifelines was built. It is often /etc or /usr/local/etc.
5035
</entry>
5036
</row>
5037
<row>
5038
<entry>2b.</entry>
5039
<entry>
5040
If the file $HOME/.linesrc exists, load parameters from it.
5041
</entry>
5042
</row>
5043
<row>
5044
<entry>2c.</entry>
5045
<entry>
5046
If the file .linesrc exists in the current directory read parameters from it.
5047
</entry>
5048
</row>
5049
<row>
5050
<entry>2d</entry>
5051
<entry>
5052
If LLCONFIGFILE is defined in the command line or database table and it's
5053
value is the name of a file, load parameters from that file.
5054
</entry>
5055
</row>
5056
</tbody>
5057
</tgroup>
5058
</informaltable>
5059
5060
<para>
5061
When <application>LifeLines</application> searches for a property it looks for it as follows:
5062
</para>
5063
<glosslist>
5064
5065
<glossentry><glossterm>cmdline table</glossterm><glossdef>
5066
5067
<para>
5068
First, <application>LifeLines</application> looks in the cmdline table. This table contains the
5069
values that have been specified using the -I option to
5070
<application>LifeLines</application>.
5071
</para>
5072
</glossdef></glossentry>
5073
5074
<glossentry><glossterm>database table</glossterm><glossdef>
5075
5076
<para> Next, <application>LifeLines</application> looks in the database table. This table contains the
5077
values which have been stored in the current database.
5078
</para>
5079
</glossdef></glossentry>
5080
5081
<glossentry><glossterm>global table</glossterm><glossdef>
5082
5083
<para>
5084
Next, <application>LifeLines</application> looks in the global table. This table contains the
5085
values found when reading in the configuration files.
5086
</para>
5087
</glossdef></glossentry>
5088
5089
<glossentry><glossterm>environment table</glossterm><glossdef>
5090
5091
<para>
5092
Finally, <application>LifeLines</application> looks in the environment table.
5093
Only a handful of properties may be set from the environment, namely
5094
LLPROGRAMS, LLREPORTS, LLARCHIVES, LLDATABASES, and LLEDITOR.
5095
</para>
5096
</glossdef></glossentry>
5097
</glosslist>
5098
5099
<para>
5100
Properties are named group.subgroup.property or group.property, or even
5101
just property.
5102
The following keys are available at the moment:
5103
</para>
5104
5105
<glosslist>
5106
<glossentry><glossterm>LLPROGRAMS</glossterm><glossdef>
5107
5108
<para>
5109
<envar>LLPROGRAMS</envar> is the search path for
5110
<application>LifeLines</application> report generating and
5111
other programs.
5112
</para>
5113
</glossdef></glossentry>
5114
5115
<glossentry><glossterm>LLREPORTS</glossterm><glossdef>
5116
5117
<para>
5118
<envar>LLREPORTS</envar> is used to select a directory where
5119
all generated reports and program outputs will be placed.
5120
</para>
5121
</glossdef></glossentry>
5122
5123
<glossentry><glossterm>LLARCHIVES</glossterm><glossdef>
5124
5125
<para>
5126
<envar>LLARCHIVES</envar> is used to select a
5127
directory where all database backup files will be stored
5128
</para>
5129
</glossdef></glossentry>
5130
5131
<glossentry><glossterm>LLDATABASES</glossterm><glossdef>
5132
5133
<para>
5134
<envar>LLDATABASES</envar> is a list of
5135
directories that contain database directories used to locate
5136
database directories themselves
5137
</para>
5138
</glossdef></glossentry>
5139
5140
<glossentry><glossterm>LLNEWDBDIR</glossterm><glossdef>
5141
5142
<para>
5143
<envar>LLNEWDBDIR</envar> a single directory where new databases
5144
specified without paths will be created.
5145
This is a convenience for users
5146
who generally put all their databases under a single common
5147
directory.
5148
</para>
5149
</glossdef></glossentry>
5150
5151
<glossentry><glossterm>LLEDITOR</glossterm><glossdef>
5152
5153
<para>
5154
Overrides the default screen editor
5155
</para>
5156
</glossdef></glossentry>
5157
</glosslist>
5158
5159
<para>
5160
Codeset Information:
5161
</para>
5162
<para>
5163
For the following parameters related to codeset, the values are a
5164
String denoting code set in use in data. Special handling is provided
5165
for UTF-8, which may be entered as "UTF-8", "utf-8", or "65001". (The
5166
official, and preferred, name is UTF-8.
5167
</para>
5168
<glosslist>
5169
<glossentry><glossterm>GedcomCodeset</glossterm><glossdef>
5170
5171
<para>
5172
Specifies the default Codeset to use when processing Gedcom files.
5173
There are actually 3 properties.
5174
<glossterm>GedcomCodesetOut</glossterm> and <glossterm>GedcomCodesetIn</glossterm>
5175
can be used to specify the codeset for output or input. If either of these is
5176
not specified <glossterm>GedcomCodeset</glossterm> is used. Most Gedcom files should
5177
contain a codeset property, so this is not usually relevant when reading a Gedcom
5178
file, unless the input Gedcom file lacks a codeset property. This is used, however,
5179
when writing out a Gedcom file.
5180
NB: This is ignored if the database has no internal codeset specified.
5181
</para>
5182
</glossdef></glossentry>
5183
5184
<glossentry><glossterm>EditorCodeset</glossterm><glossdef>
5185
5186
<para>
5187
Specifies the codeset to use for editing. There are actually 3 properties.
5188
<glossterm>EditorCodesetOut</glossterm> and <glossterm>EditorCodesetIn</glossterm>
5189
can be used to specify the codeset for output or input. If either of these is
5190
not specified <glossterm>EditorCodeset</glossterm> is used. This property allows
5191
lifelines to convert from its internal codeset to the one you use in your editor, so
5192
this is important when your editor does not use the same codeset as your database.
5193
NB: This is ignored if the database has no internal codeset specified.
5194
</para>
5195
</glossdef></glossentry>
5196
5197
<glossentry><glossterm>ReportCodeset</glossterm><glossdef>
5198
5199
<para>
5200
Specifies the codeset to use for reports. There are actually 3 properties.
5201
<glossterm>ReportCodesetOut</glossterm> and <glossterm>ReportCodesetIn</glossterm>
5202
can be used to specify the codeset for output or input. If either of these is
5203
not specified <glossterm>ReportCodeset</glossterm> is used. Recently created
5204
reports may actually specify their codeset, in which case this is not used, but
5205
for reports which do not include a specification of codeset, the
5206
<glossterm>ReportCodesetIn</glossterm> (or <glossterm>ReportCodeset</glossterm>)
5207
specifies how the report will be understood. In any case, the output of a
5208
report program will be written in the codeset given by
5209
<glossterm>ReportCodesetOut</glossterm> (or <glossterm>ReportCodeset</glossterm>).
5210
NB: This is ignored if the database has no internal codeset specified.
5211
</para>
5212
</glossdef></glossentry>
5213
5214
<glossentry><glossterm>GuiCodeset</glossterm><glossdef>
5215
5216
<para>
5217
Specifies the codeset to use for interaction with the graphical user interface.
5218
There are actually 3 properties.
5219
<glossterm>GuiCodesetOut</glossterm> and <glossterm>GuiCodesetIn</glossterm>
5220
can be used to specify the codeset for output or input. If either of these is
5221
not specified <glossterm>GuiCodeset</glossterm> is used.
5222
</para>
5223
</glossdef></glossentry>
5224
5225
<glossentry><glossterm>LongDisplayDate</glossterm><glossdef>
5226
5227
<para>
5228
Six comma separated numbers. Specifing the format for
5229
days, months, years, date format, era format, and complex format.
5230
If string does not contain 6 comma separated numbers all formats are
5231
set to 0, except date format is set to 14.
5232
These formats are used by <application>LifeLines</application> to display dates in long format.
5233
</para>
5234
</glossdef></glossentry>
5235
5236
<glossentry><glossterm>LongDisplayDatePic</glossterm><glossdef>
5237
5238
<para>
5239
a custom ymd date picture. A string in which %y, %m and %d will be
5240
converted to the corresponding year, month and day.
5241
This picture is used by <application>LifeLines</application> to display dates in long format.
5242
</para>
5243
</glossdef></glossentry>
5244
5245
<glossentry><glossterm>ShortDisplayDate</glossterm><glossdef>
5246
5247
<para>
5248
Six comma separated numbers. Specifing the format for
5249
days, months, years, date format, era format, and complex format.
5250
If string does not contain 6 comma separated numbers all formats are
5251
set to 0, except date format is set to 14.
5252
These formats are used by <application>LifeLines</application> to display dates in short format.
5253
</para>
5254
</glossdef></glossentry>
5255
5256
<glossentry><glossterm>ShortDisplayDatePic</glossterm><glossdef>
5257
5258
<para>
5259
a custom ymd date picture. A string in which %y, %m and %d will be
5260
converted to the corresponding year, month and day.
5261
This picture is used by <application>LifeLines</application> to display dates in short format.
5262
</para>
5263
</glossdef></glossentry>
5264
5265
<glossentry><glossterm>LocaleDir</glossterm><glossdef>
5266
5267
<para>
5268
run-time specification of locale directory
5269
</para>
5270
</glossdef></glossentry>
5271
5272
<glossentry><glossterm>NewDbProps</glossterm><glossdef>
5273
5274
<para>
5275
if specified, properties to add to a newly created database.
5276
The string is of the form "option1=value1\noption2=value2".
5277
</para>
5278
</glossdef></glossentry>
5279
5280
<glossentry><glossterm>IllegalChar</glossterm><glossdef>
5281
5282
<para>
5283
Apparently not used at this time.
5284
</para>
5285
</glossdef></glossentry>
5286
5287
<glossentry><glossterm> DenySystemCalls</glossterm><glossdef>
5288
5289
<para>
5290
If set to a non-zero value will disable use of the <function>system</function>
5291
function.
5292
</para>
5293
</glossdef></glossentry>
5294
5295
<glossentry><glossterm>UiLocaleCollate</glossterm><glossdef>
5296
5297
<para>
5298
ui collating sequence
5299
</para>
5300
</glossdef></glossentry>
5301
5302
<glossentry><glossterm>UiLocaleMessages</glossterm><glossdef>
5303
<para>
5304
ui messages locale
5305
</para>
5306
</glossdef></glossentry>
5307
5308
<glossentry><glossterm>RptLocaleCollate</glossterm><glossdef>
5309
5310
<para>
5311
Report Collating Sequence
5312
</para>
5313
</glossdef></glossentry>
5314
5315
<glossentry><glossterm>RptLocaleMessages</glossterm><glossdef>
5316
5317
<para>
5318
Report Messages Locale
5319
</para>
5320
</glossdef></glossentry>
5321
5322
<glossentry><glossterm>ShortOmitString</glossterm><glossdef>
5323
5324
<para>
5325
If defined this string replaces characters at the end of an event being
5326
printed.
5327
</para>
5328
</glossdef></glossentry>
5329
5330
<glossentry><glossterm>DisplayKeyTags</glossterm><glossdef>
5331
5332
<para>
5333
If set to 1 an i or f is prepended to individual and family keys when shown
5334
on-screen.
5335
</para>
5336
</glossdef></glossentry>
5337
5338
<glossentry><glossterm>AnnotatePointers</glossterm><glossdef>
5339
5340
<para>
5341
If set to 1 a descriptive comment is added to pointers when editing family or
5342
individual records to help identify who is being refered to. These tags
5343
are removed when the edit is finished and not stored in the database.
5344
</para>
5345
5346
</glossdef></glossentry>
5347
5348
<glossentry><glossterm>TTPATH</glossterm><glossdef>
5349
5350
<para>
5351
list of directories to search for translation table files (*.tt)
5352
</para>
5353
</glossdef></glossentry>
5354
5355
<glossentry><glossterm>TTPATH.debug</glossterm><glossdef>
5356
5357
<para>
5358
if defined, <application>LifeLines</application> outputs debug information
5359
related to translation table processing.
5360
</para>
5361
</glossdef></glossentry>
5362
5363
<glossentry><glossterm>InputPath</glossterm><glossdef>
5364
5365
<para>
5366
path to look for in when reading in gedcom files
5367
</para>
5368
</glossdef></glossentry>
5369
5370
<glossentry><glossterm>INDIREC</glossterm><glossdef>
5371
5372
<para>
5373
The default template to use whenever creating a new individual.
5374
If not specified, the concatenation of the following is used:
5375
<programlisting>
5376
"0 INDI\n1 NAME Fname/Surname\n1 SEX MF\n"
5377
"1 BIRT\n 2 DATE\n 2 PLAC\n"
5378
"1 DEAT\n 2 DATE\n 2 PLAC\n1 SOUR\n"
5379
</programlisting>
5380
</para>
5381
</glossdef></glossentry>
5382
5383
<glossentry><glossterm>FAMRECBODY</glossterm><glossdef>
5384
5385
<para>
5386
The default template to use whenever creating a new family.
5387
If not specified, the following is used:
5388
<programlisting>
5389
"1 MARR\n 2 DATE\n 2 PLAC\n 2 SOUR\n"
5390
</programlisting>
5391
Note: Unlike the others, this should not
5392
include the 0 level FAM tag.)
5393
</para>
5394
</glossdef></glossentry>
5395
5396
<glossentry><glossterm>SOURREC</glossterm><glossdef>
5397
5398
<para>
5399
The default template to use whenever creating a new source.
5400
If not specified, the following is used in english:
5401
<programlisting>
5402
"0 SOUR\n1 REFN\n1 TITL Title\n1 AUTH Author"
5403
</programlisting>
5404
</para>
5405
</glossdef></glossentry>
5406
5407
<glossentry><glossterm>EVENREC</glossterm><glossdef>
5408
5409
<para>
5410
The default template to use whenever creating a new event.
5411
If not specified, the following is used in english:
5412
<programlisting>
5413
"0 EVEN\n1 REFN\n1 DATE\n1 PLAC\n1 INDI\n 2 NAME\n 2 ROLE\n1 SOUR"
5414
</programlisting>
5415
</para>
5416
</glossdef></glossentry>
5417
5418
<glossentry><glossterm>OTHR</glossterm><glossdef>
5419
5420
<para>
5421
The default template to use whenever creating a new other record.
5422
If not specified, the following is used in english:
5423
<programlisting>
5424
"0 XXXX\n1 REFN"
5425
</programlisting>
5426
</para>
5427
</glossdef></glossentry>
5428
5429
<glossentry><glossterm>HDR_SUBM</glossterm><glossdef>
5430
5431
<para>
5432
string to use when writing gedcom files for the SUBM.
5433
Default is
5434
<programlisting>
5435
"1 SUBM".
5436
</programlisting>
5437
</para>
5438
</glossdef></glossentry>
5439
5440
<glossentry><glossterm>HDR_GEDC</glossterm><glossdef>
5441
5442
<para>
5443
String containing the GEDC block for the header record when exporting GEDCOM.
5444
The default is
5445
<programlisting>
5446
"1 GEDC\n2 VERS 5.5\n2 FORM LINEAGE-LINKED".
5447
</programlisting>
5448
</para>
5449
</glossdef></glossentry>
5450
5451
<glossentry><glossterm>HDR_CHAR</glossterm><glossdef>
5452
5453
<para>
5454
String containing the CHAR block for the header record when exporting GEDCOM.
5455
The default is
5456
<programlisting>
5457
"1 CHAR ASCII".
5458
</programlisting>
5459
</para>
5460
</glossdef></glossentry>
5461
5462
<glossentry><glossterm>ReportLog</glossterm><glossdef>
5463
5464
<para>
5465
name of file to print report program errors to, if not specified
5466
use stdout curses window.
5467
</para>
5468
</glossdef></glossentry>
5469
5470
<glossentry><glossterm>CrashLog_llexec</glossterm><glossdef>
5471
5472
<para>
5473
file to write crash log into for llexec. If not set, log is written to
5474
the file <filename>CrashLog_llexec.log</filename>.
5475
</para>
5476
</glossdef></glossentry>
5477
5478
<glossentry><glossterm>CrashLog_llines</glossterm><glossdef>
5479
5480
<para>
5481
file to write crash log into for llines. If not set, log is written to
5482
the file <filename>CrashLog_llines.log</filename>.
5483
</para>
5484
</glossdef></glossentry>
5485
<glossentry><glossterm>LLTTEXPORT</glossterm><glossdef>
5486
5487
<para>
5488
directory to write translation tables to. Default is the current
5489
directory.
5490
</para>
5491
</glossdef></glossentry>
5492
5493
<glossentry><glossterm>ImportLog</glossterm><glossdef>
5494
5495
<para>
5496
where to log errors found while importing a gedcom file.
5497
default is errs.log.
5498
</para>
5499
</glossdef></glossentry>
5500
5501
<glossentry><glossterm>gettext.path</glossterm><glossdef>
5502
5503
<para>
5504
for windows, if specified path to (re)load gettext dll
5505
</para>
5506
</glossdef></glossentry>
5507
5508
<glossentry><glossterm>iconv.path</glossterm><glossdef>
5509
5510
<para>
5511
for Windows, path to link dynamically to gettext and iconv
5512
</para>
5513
</glossdef></glossentry>
5514
5515
<glossentry><glossterm>user.fullname</glossterm><glossdef>
5516
5517
<para>
5518
The full name of the current user. If not found as a property it is fetched
5519
from the system when possible.
5520
</para>
5521
</glossdef></glossentry>
5522
5523
<glossentry><glossterm>user.email</glossterm><glossdef>
5524
5525
<para>
5526
The email address of the current user. If not found as a property it is
5527
fetched from the system when possible.
5528
</para>
5529
</glossdef></glossentry>
5530
5531
<glossentry><glossterm>user.address</glossterm><glossdef>
5532
5533
<para>
5534
Postal address of the current user.
5535
</para>
5536
</glossdef></glossentry>
5537
5538
<glossentry><glossterm>user.phone</glossterm><glossdef>
5539
5540
<para>
5541
The phone number of the current user.
5542
</para>
5543
</glossdef></glossentry>
5544
5545
<glossentry><glossterm>user.url</glossterm><glossdef>
5546
5547
<para>
5548
URL to the users home page.
5549
</para>
5550
</glossdef></glossentry>
5551
</glosslist>
5552
5553
</sect1>
5554
5555
</chapter>
5556
</book>
Loggerhead is a web-based interface for Breezy
Version: 2.0.1