-
Notifications
You must be signed in to change notification settings - Fork 15
Expand file tree
/
Copy pathwordsdoc.htm
More file actions
4611 lines (4018 loc) · 209 KB
/
wordsdoc.htm
File metadata and controls
4611 lines (4018 loc) · 209 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<HTML>
<HEAD>
<TITLE>WORDS 1.97F (LATIN-ENGLISH DICTIONARY) PROGRAM DOCUMENTATION</TITLE>
</HEAD>
<BODY>
<H1><CENTER>WORDS Version 1.97FC</CENTER>
<CENTER>LATIN-ENGLISH DICTIONARY PROGRAM</CENTER></H1>
<BR><BR>
<A HREF="#SUMMARY"><B>SUMMARY</B></A><BR>
<BR>
<A HREF="#INSTALLATION"><B>INSTALLATION</B></A><BR>
<A HREF="#Is There a Problem">Is There a Problem?</A><BR>
<BR>
<A HREF="#INTRODUCTION"><B>INTRODUCTION</B></A><BR>
<BR>
<A HREF="#OPERATIONAL DESCRIPTION"><B>OPERATIONAL DESCRIPTION</B></A><BR>
<A HREF="#Program Operation">Program Operation</A><BR>
<A HREF="#Modes of Operation">Modes of Operation</A><BR>
<A HREF="#Command Line Operation">Command Line Operation</A><BR>
<A HREF="#Latin-to-English Examples">Latin-to-English Examples</A><BR>
<A HREF="#English-to-Latin Examples">English-to-Latin Examples</A><BR>
<A HREF="#Design of the Meaning Line">Design of the Meaning Line</A><BR>
<A HREF="#Signs and Abbreviations in Meaning">Signs and Abbreviations in Meaning</A><BR>
<BR>
<A HREF="#PROGRAM DESCRIPTION"><B>PROGRAM DESCRIPTION</B></A><BR>
<A HREF="#Codes in Inflection Line">Codes in Inflection Line</A><BR>
<A HREF="#Help for Parameters">Help for Parameters</A><BR>
<A HREF="#Special Cases">Special Cases</A><BR>
<A HREF="#Uniques">Uniques</A><BR>
<A HREF="#Tricks">Tricks</A><BR>
<A HREF="#Trimming of uncommon results">Trimming of uncommon results</A><BR>
<BR>
<A HREF="#GUIDING PHILOSOPHY"><B>GUIDING PHILOSOPHY</B></A><BR>
<A HREF="#Purpose">Purpose</A> <BR>
<A HREF="#Method">Method</A><BR>
<A HREF="#Word Meanings">Word Meanings</A><BR>
<A HREF="#Proper Names">Proper Names</A><BR>
<A HREF="#Letter Conventions (u/v, i/j, w)">Letter Conventions (u/v, i/j, w)</A><BR>
<BR>
<A HREF="#DICTIONARY"><B>DICTIONARY</B></A><BR>
<A HREF="#Dictionary Codes">Dictionary Codes</A><BR>
<A HREF="#AGE">AGE</A><BR>
<A HREF="#AREA">AREA</A><BR>
<A HREF="#GEO">GEO</A><BR>
<A HREF="#FREQ">FREQ</A><BR>
<A HREF="#SOURCE">SOURCE</A><BR>
<A HREF="#Current Distribution of DICTLINE Flags">
Current Distribution of DICTLINE Flags</A><BR>
<A HREF="#Dictionary Conventions">Dictionary Conventions</A><BR>
<A HREF="#Evolution of the Dictionary">Evolution of the Dictionary</A><BR>
<A HREF="#Text Dictionary - DICTPAGE.TXT">Text Dictionary - DICTPAGE.TXT</A><BR>
<A HREF="#Latin Spellchecking - Text Processor List - LISTALL.ZIP">
Latin Spellchecking - Text Processor List - LISTALL.ZIP</A><BR>
<BR>
<A HREF="#INFLECTIONS"><B>INFLECTIONS</B></A><BR>
<BR>
<A HREF="#ENGLISH to LATIN"><B>ENGLISH to LATIN</B></A><BR>
<A HREF="#English Parsing of Meanings">English Parsing of Meanings</A><BR>
<A HREF="#Ordering English-to-Latin Output">Ordering English-to-Latin Output</A><BR>
<BR>
<A HREF="#TESTS AND STATUS"><B>TESTS AND STATUS</B></A><BR>
<A HREF="#Testing">Testing</A><BR>
<A HREF="#Current Status and Future Plans">Current Status and Future Plans</A><BR>
<BR>
<A HREF="#USER MODIFICATIONS"><B>USER MODIFICATIONS</B></A><BR>
<A HREF="#Writing DICT.LOC and UNIQUES.LAT">Writing DICT.LOC and UNIQUES.LAT</A><BR>
<A HREF="#DICT.LOC">DICT.LOC</A><BR>
<A HREF="#UNIQUES.LAT">UNIQUES.LAT</A><BR>
<BR>
<A HREF="#DEVELOPERS AND REHOSTING"><B>DEVELOPERS AND REHOSTING</B></A><BR>
<A HREF="#Program source code and data">Program source code and data</A><BR>
<A HREF="#License">License</A><BR>
<A HREF="#Rehosting WORDS">Rehosting WORDS</A><BR>
<A HREF="#Feedback">Feedback</A><BR>
<BR><BR>
<A NAME="SUMMARY">
<H2><CENTER>SUMMARY</CENTER>
</H2></A> <BR>
<BR>
<P>
This program, WORDS, takes keyboard input or a file of Latin text lines and
provides an analysis of each word individually. It uses an INFLECT.SEC,
UNIQUES.LAT, ADDONS.LAT, STEMFILE.GEN, INDXFILE.GEN, and DICTFILE.GEN, and
possibly .SPE and DICT.LOC.
<P>
The dictionary contains over 39000 entries, as would be counted in an
ordinary dictionary. This expands to almost twice that number of
individual stems (the count that the program may display at startup), and,
through additional word construction with hundreds of prefixes and
suffixes, may generate more, leading to many hundreds of thousands of
'words' that can be formed by declension and conjugation. This version of
WORDS provides a tool to help in translations for the Latin student. It
is now a large dictionary by any measure and can be helpful to advanced
users. The dictionary will continue to grow - slowly. <BR>
<BR>
<A NAME="INSTALLATION">
<H2><CENTER>INSTALLATION</CENTER>
</H2></A> <BR>
<P>
The WORDS program, with its accompanying data files should run on any
machine for which it is adapted, any monitor. Simply download the
self-extracting EXE files or the compressed file for the appropriate
system and execute/decompress it in your chosen subdirectory on the hard
disk, creating the necessary files. Then call/run WORDS, or do as instructed
in any README.
<P>The load includes SPQR.ICO, a possible icon for WORDS,
but just that, only an icon.
You have to install the program as per the directions
(put the downloaded files in a folder,
run them to expand to the WORDS system, then run from that folder).
However, If you are Windows-wise, you can use Explorer and
make a shortcut and put it on the desktop.
Windows will make a generic icon,
but you can change it (using Properties)
to whatever other icon you can find, for instance,
the one included with the package. Or not.
Make sure that the Properties on the icon
has as Target the WORDS.EXE
in the folder in which the system is loaded.
<P>
See the particular page for each specific system. <BR>
<A HREF="http://www.erols.com/whitaker/wordsdos.htm"><B>DOS</B></A><BR>
<A HREF="http://www.erols.com/whitaker/wordsw95.htm"><B>Windows 95/NT/98/2000/XP</B></A><BR>
<A HREF="http://www.erols.com/whitaker/wordslux.htm"><B>Linux and FreeBSD</B></A><BR>
<A HREF="http://www.erols.com/whitaker/wordsos2.htm"><B>OS/2</B></A><BR>
<A HREF="http://www.erols.com/whitaker/wordsmac.htm"><B>MAC OS X</B></A><BR>
<BR><BR>
<A NAME="Is There a Problem">
<H4>Is There a Problem?</H4></A>
<P>Did you download the two appropriate file(s) to your hard disk,
as listed in the download page for your system?
<P>Can you verify that they are there and full size (megabytes as indicated)?
<P>Did you execute/run/unzip these programs?
<P>If self-extracted, were you asked where to put the generated files?
(Maybe a default C:\WORDS)?
If not, did you put them in the folder/subdirectory from which you wish to operate?
<P>Can you verify that the full set of files (about 10 MB) was generated in that folder/subdirectory,
or wherever you chose? At least
WORDS.EXE, INFLECT.SEC, UNIQUES.LAT, ADDONS.LAT, STEMFILE.GEN, INDXFILE.GEN, and DICTFILE.GEN,
plus documentation.
<P>Did you run/execute WORDS in that folder/subdirectory? e.g. <BR>
<B>C:\WORDS</B>
<P>If when you try to run there is no WORDS.EXE (or equivalent),
the system should let you know.<BR>
If there is no INFLECTS.SEC, the program will say so and abort immediately.<BR>
If there are no dictionary files, the program will tell you, but will start
(you can get Roman numerals!).<BR>
If there is no ADDONS.LAT or UNIQUES.LAT, the program will tell you,
and if they are there it will tell you how many.<BR>
<BR><BR>
<A NAME="INTRODUCTION">
<H3><CENTER>INTRODUCTION</CENTER>
</H3></A><BR>
<BR>
<P>
I am no expert in Latin, indeed my training is limited to a couple of
years in high school more than 50 years ago. But I always felt that Latin, as
presented after two millennia, was a scientific language. It had the
interesting property of inflection, words were constructed in a logical
manner. I admired this feature, but could never remember the vocabulary
well enough when it came time to exercise it on tests.
<P>
I decided to automate an elementary-level Latin vocabulary list. As a
first stage, I produced a computer program that will analyze a Latin word
and give the various possible interpretations (case, person, gender,
tense, mood, etc.), within the limitations of its dictionary. This might
be the first step to a full parsing system, but, although just a
development tool, it is useful by itself.
<P>
<B>Please remember that this is only a computer exercise in automating a
Latin dictionary. I am not a Latin scholar and anything in the program or
documentation is filtered by me from reading the cited Latin dictionaries. Please
let no one go to his teacher and cite my interpretation as an authority. </B>
<P>
While developing this initial implementation, based on different sources,
I learned (or re-learned) something that I had overlooked at the
beginning. Latin courses, and even very large Latin dictionaries, are put
together under very strict ground rules. Some dictionary might be based
exclusively on 'Classical' (200 BC - 200 AD) texts; it might have every
word that appears in every surviving writing of Cicero, but nothing much
before or since. Such a dictionary will be inadequate for translating
medieval theological or scientific texts. In another example, one
textbook might use Caesar as their main source of readings (my high school
texts did), while another might avoid Caesar and all military writings
(either for pacifist reasons, or just because the author had taught Caesar
for 30 years and had grown bored with going over the same material, year
after year). One can imagine that the selection of words in such
different texts would differ considerably; moreover, even with the same
words, the meanings attached would be different. This presents a problem
in the development of a dictionary for general use.
<P>
One could produce a separate dictionary for each era and application or a
universal dictionary with tags to indicate the appropriate application and
meaning for each word. With such a tag arrangement one would not be
offered inappropriate or improbable interpretations. The present system
has such a mechanism, but it is not fully exploited.
<P>
The Version 1.97E dictionary may be found to be of fairly general use for
the student; it has all the easy words that every text uses. It also has the
adverbs, prepositions, and conjunctions, which are not as
sensitive to application as are the nouns and verbs. The system also
tests a few hundred prefixes and suffixes, if the raw word cannot be
found. Beyond that, there are a large number of TRICKS which may be applied.
These may be thought of as correcting for variations in spelling.
This allows an interpretation of many words which would otherwise
be marked unknown. The result of this analysis is fairly straightforward
in most cases, accurate but esoteric in some others. Some constructions
are recognized Latin words, and some are perfectly reasonable words which
may never have been used by Cicero or Caesar but might have been used by
Augustine or a monk of Jarrow. For about 1 in 10 constructed words the
result has no relation to the normal dictionary meaning.
<P>
BE WARNED! The program will go to great lengths if all tricks are
invoked. If you get a word formed with an enclitic, prefix, suffix, and
syncope, be very suspicious! It my well be right, but look carefully.
(Try siquempiamque!)
<P>
The final try is to look at the input as two words run together. In
most cases this works out, and is especially useful for late Latin number
usage. However, this algorithm may go very wrong. If it is not obviously
right, it is probably incorrect.
<P>
With this facility, and a 39000 word dictionary, trials on some tested
classical texts and the Vulgate Bible give hit rates of far better than
99%, excluding proper names (there are very few proper names in this
dictionary). (I am an old soldier so the dictionary may have
every possible word for attack or destroy. The system is near perfect for
Caesar.) The question arises, what hit rate can be expected for a general
dictionary. Classical Latin dictionaries have no references to the
terminology of Christian theology. The legal documents and deeds of the
Middle Ages are a challenge of jargon and abbreviations. These areas
require special knowledge and vocabulary, but even there the ability to
handle the non-specialized words is a large part of the effort.
<P>
The development system allows the inclusion of specialized vocabulary (for
instance a SPEcial dictionary for specialized words not wanted in most
dictionaries), and the opportunity for the user to add additional words to
a DICT.LOC.
<P>
It was initially expected that there would be special dictionaries for
special applications. That is why there is the possibility of a SPECIAL
dictionary. Now the general dictionary is coded by AGE and application
AREA. Thus special words used initially/only by St Thomas Aquinas would
be Medieval (AGE code F) and Ecclesiastical (AREA code E). Eventually
there needs to be a filter that allows one, upon setting parameters for
Medieval and Ecclesiastical, to push those words over others. Right now
there are not have enough non-classical vocabulary to rely on such a
scheme. The problem is that one needs a very complete classical
dictionary before one can assure that new entries are uniquely Medieval,
that they are not just classical words that appear in a Medieval text.
And the updated is only into the D's. So the situation is that the
mechanism is there, but not sufficient data. Nevertheless that is exactly
the application I had in mind when I set out to do the program.
<P>
One can set a parameter to exclude medieval words if there is a classical
word answering the same parse. Likewise, the program can ignore rare
meanings if there is a common meaning for the parse.
<P>
The program may be larger than is necessary for the present
application. It is still in development but some effort has now been put
into optimization. Nevertheless there is lots of room for speeding it up.
Specifically, the program is disk-oriented is order to run on small machines,
such as DOS with the 640KB limitation. Rejecting this limitation and assuming
that the user has tens of megabytes of memory (clearly realistic today)
would allow faster processing. The next version may go that way.
<P>
This is a free program, which means it is proper to copy it and pass it on
to your friends. Consider it a developmental item for which there is no
charge. However, just for form, it is Copyrighted (c).
Permission is hereby freely given for any and all use of program and data.
You can sell it as your own, but at least tell me.
<P>
This version is distributed without obligation, but the developer would
appreciate comments and suggestions.
<P>
<BR>
William A Whitaker <BR>
PO Box 3036 <BR>
McLean VA 22103-3036 <BR>
USA <BR>
whitaker@erols.com <BR>
<BR>
<A NAME="OPERATIONAL DESCRIPTION">
<H3><CENTER>OPERATIONAL DESCRIPTION</CENTER>
</H3></A> <BR>
<P>
This write up is rudimentary and assumes that the user is experienced with
computers, and as an example assumes a PC with a Windows OS.
Other systems operate essentially the same.
<P>
The WORDS program, Version 1.97E, with it's accompanying data files should
run on PC in Windows 95/98/NT, any monitor. Simply download the
self-extracting EXE file and execute it in your chosen subdirectory/folder to
UNZIP the files into a subdirectory of a hard disk. Then call WORDS.
<P>
There are a number of files associated with the program. These must be in
the subdirectory/folder of the program, and the program must be run from that
subdirectory. WORDS.EXE is the executable program. INFLECT.SEC holds the
encoded inflection records. STEMFILE.GEN contains the stems of the
GENERAL dictionary in a searchable form.
DICTFILE.GEN is an indexed form of the GENERAL dictionary entries with form
information and meanings. INDXFILE.GEN contains a set of indexes into the
DICTFILE. In some versions, there may be a set of files for a SPECIAL (.SPE)
dictionary of the same structure as the GENERAL dictionary, but there is
no SPECIAL dictionary in the present distribution. A LOCAL dictionary may
also be used. This is a limited dictionary of a different form, human
readable and writeable. The knowledgeable user can augment and modify it
on-line. It would consist of the file DICT.LOC. UNIQUES.LAT contains
certain words which regular processing does not get. ADDONS.LAT contains
the set of prefixes, suffixes and enclitics (-que, -ve) and the like.
Other files may be generated by the program, so run it in a configuration
that allows the creation of files.
<P>
All these files are necessary to run the program (except the optional
dictionaries SPE and LOC). This excess of files is a consequence of the
present developmental nature of the program. The files are very simple,
almost human-readable. Presumably, a later version could condense and
encode them. Nevertheless, beyond the original COPY, the user need not
worry about them.
<P>
Additionally, there are files that the program may produce on request.
All of these share the name WORD, with various extensions, and they are
all ASCII/DOS text files which can be viewed and processed with an ordinary
editor. The casual user may not want to get involved with
these. WORD.OUT will record the whole output, WORD.UNK will list only
words the program is unable to interpret. These outputs are turned on
through the PARAMETERS mechanism.
<P>
PARAMETERS may be changed while running the program by inputting a line
containing a '#' mark as the only (or first) character. Alternatively,
WORD.MOD contains the MODES that can be set by CHANGE_PARAMETERS. If this
file does not exist, default modes will be used. The file may be produced
or changed when changing parameters. It can also be modified, if the user
is sufficiently confident, with an editor, or deleted, thereby reverting
to defaults.
<P>
There is another set of developers parameters which may be set
with the input of '!'. These MODES may be changed and saved in a
file WORD.MDV. These are not normal user facilities, probably no one but
the developer would be interested. In any specific release these
facilities may, or may not, work. They are just mentioned here in case
they ever come up accidentally, and to point out that there are other
capabilities, actual and possible, which may be invoked if there is a
special need. The user is invited to review these parameters to see
if any address an unusual need.
<P>
WORD.OUT is the file produced if the user requests
output to a file. This output can be used for later manipulation with a
text editor, especially when the input was a text file of some length. If
the parameter UNKNOWNS_ONLY is set, the output serves as a sort of a Latin
spell checker. Those words it cannot match may just not be in the
dictionary, but alternatively they may be typos. A WORD.UNK file of
unknowns can be generated.
<BR>
<BR>
<A NAME="Program Operation">
<H4>Program Operation</H4></A>
<P>
To start the program, in the subdirectory that contains all the files,
type WORDS. A setup procedure will execute, processing files. Then the
program will ask for a word to be keyed in. Input the word and give a
return (ENTER). Information about the word will be displayed.
<P>
One can input a whole line at a time, however long,
but only one line since the return
at the end of line will start the processing. If the results would fill
more than a computer screen, the output is halted until the user responds
to the 'MORE' message with a return. A file containing a text, a series
of lines, can be input by keying in the character '@', followed (with no
spaces) by the DOS name of the file of text. This input file need not be
in the program subdirectory, just use the full path and name of the
file. This is usually accompanied with the setting of the parameter
switches to create and write to an output file, WORD.OUT.
<P>
One can have a comment in the file, a terminal portion of a line that is
not parsed. This could be an English meaning, a source where the word was
found, an indication that it may have been miscopied, etc. A comment
begins with a double dash [--] and continues to the end of the line. The
'--' and everything after on that line is ignored by the program.
<P>
A simple # character input at the start of a line (that is, a line
containing only #) will permit the user to set modes to prevent the
process from trying prefixes and suffixes to get a match on an item
unknown to the dictionary, put output to a file, etc. Going into the
CHANGE_PARAMETERS, the '?' character calls help for each entry.
<P>
Another set of parameters is invoked by the character !. These developer parameters
are fairly specialized and are probably not required by the average user,
nevertheless they are available for special applications.
<P>
Two successive returns with no text will terminate the program (except in
text being read from an @ disk file.)
<A NAME="Modes of Operation">
<H4>Modes of Operation</H4></A>
<P>The mode of operation of WORDS can be specialized by setting some combination
of available parameters. Here are a couple of example situations.
<P>If you want only meanings to show up, set the # parameter
<BR>
DO_ONLY_MEANINGS => Yes
<BR>
<P>If you do not even want to see the dictionary form (principle parts) set
# parameter
<BR>
DO_DICTIONARY_FORM => No
<BR>
<P>If you want to accept only the dictionary entry (amo, but not amas), set
the ! parameter (this is the tricky one, requiring two parameters set)
<BR>
DO_ONLY_INITIAL_WORD => Yes
<BR>
<P>This will ten require you to input one enrty per line, which is not
unreasonable for a dictionary look-up process. Then you will be offered
another, otherwise unavailable, option
<BR>
FOR_WORD_LIST_CHECK => Yes
<BR>
<P>There are a large number of other options. The user is invited
to consider all the options if needing anything more than the basic parse.
<P>Of course, for both sets of parameters, you will want to go to the end
of the parameter setting menu and save this set so you can restart with
the same situation.
<A NAME="Command Line Operation">
<H4>Command Line Operation</H4></A>
The main mode of usage for WORDS is a simple call, followed by screen interaction.
<P>
But there are other, command line, options.
WORDS may be called with arguments on the same line, in a number of different modes.
The program will execute with these arguments as input.
Remember that the saved parameter settings (in WORD.MOD and WORD.MDV)
are controlling, even for command line input.
<P>
Single argument, either a simple Latin word or an input file.
<P>
WORDS amo
<BR>which will cause it to execute for that input and then terminate. This is
for a quick word.
<P>
WORDS infile
<BR>causes WORDS to execute with the contents of the inflie.
The infile may be from any folder if the full path name is given.
<P>
With two arguments the options are: inputfile and outputfile,
two Latin words, or a language shift to English (Latin being the startup default)
and an English word (with no part of speech).
<P>
WORDS infile outfile
<BR>The program will read as input the INFILE and write
the output to the OUTFILE (as though it were WORD.OUT). It will then
await further input from the user. It terminates with a return. If the
parameters are not legal file names, the program will assume they are
Latin words to be processed as command line input.
<P>
WORDS amo amas
<P>
WORDS ^e love
<BR>switches to English input from the default Latin and searches for love.
<P>
With three arguments there could be three Latin words or a language shift
and and English word and part of speech.
<P>
WORDS amo amas amat
<P>
WORDS ^e love v
<P>
More than three arguments must all be Latin words.
<P>
WORDS amo amas amat amamus amatis amant
<P>
There cannot be more than one English word in the argument list,
since there can only be one English word per line for WORDS input.
<P>
An input file (either from interactive with @ or from command line)
can have changes of language, but the ^E or ^L must be on a seperate line.
Note that this capability can create confusing situations.
An input file that starts off Latin then switches to English will be
correctly processed. But if it is followed by a similiar input file, the
second file will start off English (from the setting in the earlier file) and fail
on the Latin input. Thus even submitting the same file twice in a run
will give different results. Ithis problem can be alleviated by starting each
input file with an explicit language instruction, but this will not normally be
the situation.
<A NAME="Latin-to-English Examples">
<H4>Latin-to-English Examples</H4>
<P>
Following are annotated examples of output. Examination of these will
give a good idea of the system. The present version may not match these
examples exactly - things are changing - but the principle is there. A
recent modification is the output of dictionary forms or 'principal parts'
(shown below for some examples).
<PRE><TT>=>agricolarum
agricol.arum N 1 1 GEN P M
agricola, agricolae N M [XAXBO]
farmer, cultivator, gardener, agriculturist; plowman, countryman, peasant;
</TT></PRE>
<P>
This is a simple first declension noun, and a unique interpretation. The
'1 1' means it is first declension, with variant 1. This is an internal
coding of the program, and may not correspond exactly with the grammatical
numbering. The 'N' means it is a noun. It is the form for genitive
(GEN), plural ('P'). The stem is masculine (M).
The stem is given as 'agricol' and the ending is
'arum'. The stem is normal in this case, but is a product of the program,
and may not always correspond to conventional usage.
<P>On the next line is given the expansion of the form that one might find
in a paper dictionary, the nominitive and genitive (agricola, agricolae).
The [XAXBO] is an internal code of the program and is documented below as Dictionary Codes.
Several codes are associated with each dictionary entry (presently AGE, AREA, GEO, FREQ, SOURCE).
These provide some information to enhance the interpretation of the dictionary entry.
In this case, the interesting piece is the B, which signifies
that this word is found frequently in texts, in the top 10 percent.
The O says it has been verified in the Oxford Latin Dictionary.
The A says it is an agrigultural word.
<P>The declension/conjugation numbers for nouns and verbs are
essentially arbitary (but will be familiar to Latin students).
The variants are complete inventions.
They have no real meaning, just codes for the program.
<P>(In the case of adjectives, they are even more arbitary,
although a Latin student might see how I came by them.
Again they are only codes for the program.
The initial release of the program did not put these out,
but there is some interest on the part of students, so they are now included.
The user may ignore them altogether.
There is no relation between the declension/variant codes of a noun
and the accompaning adjective.
They only agree in case, number, and gender (NOM S N),
which are listed in the output.)
<PRE><TT>=>feminae
femin.ae N 1 1 GEN S F
femin.ae N 1 1 DAT S F
femin.ae N 1 1 NOM P F
femin.ae N 1 1 VOC P F
femina, feminae N F [XXXAX]
woman; female;
</TT></PRE>
<P>
This word has several possible interpretations in case and number
(Singular and Plural). The gender is Feminine. Presumably, the user can
examine the adjoining words and reduce the set of possibilities.
<PRE><TT>=>cornu
corn.u N 4 1 ABL S F
cornus, cornus N F [XXXCO]
cornel-cherry-tree (Cornus mas); cornel wood; javelin (of cornel wood);
corn.u N 4 2 NOM S N
corn.u N 4 2 DAT S N
corn.u N 4 2 ABL S N
corn.u N 4 2 ACC S N
cornu, cornus N N [XXXAO]
horn; hoof; beak/tusk/claw; bow; horn/trumpet; end, wing of army; mountain top;
*
</TT></PRE>
<P>
Here is an example of another declension and two variants. The
Masculine (and few Feminine) (-us) nouns of the declension are '4 1' and the Neuter
(-u) nouns are coded as '4 2'. This word has both.
The horn parse is very frequent (A), while the cornel option (C) is
less so but still common.
<PRE><TT>=>ego
ego PRON 5 1 NOM S C
[XXXAX]
I, me; myself;</TT></PRE>
<P>
A pronoun is much like a noun. The gender is common (C), that is, it may
be masculine or feminine. For some odd words, especially including pronouns,
there is no dictionary form given.
<PRE><TT>=>illud
ill.ud PRON 6 1 NOM S N
ill.ud PRON 6 1 ACC S N
ille, illa, illud PRON [XXXAX]
that; those (pl.); also DEMONST; that person/thing; the well known; the former;
*
</TT></PRE>
<P>The asterisk means that there are other, less probable forms which have been
trimmed, but which may be recovered by running with the TRIM parameter reset.
<PRE><TT>=>hic
h.ic PRON 3 1 NOM S M
hic, haec, hoc PRON [XXXAX]
this; these (pl.); also DEMONST;
hic ADV POS
hic ADV [XXXCX]
here, in this place; in the present circumstances;</TT></PRE>
<P>
In this case there is a adjectival/demonstrative pronoun, or it may be an
adverb. The POS means that the comparison of the adverb is positive.
<PRE><TT>=>bonum
bon.um N 2 1 ACC S M
bonus, boni N M [XXXCO]
good/moral/honest/brave man; man of honor, gentleman; better/rich people (pl.);
bon.um N 2 2 NOM S N
bon.um N 2 2 ACC S N
bonum, boni N N [XXXAO]
good, good thing, profit, advantage; goods (pl.), possessions, wealth, estate;
bon.um ADJ 1 1 NOM S N POS
bon.um ADJ 1 1 ACC S M POS
bon.um ADJ 1 1 ACC S N POS
bonus, bona -um, melior -or -us, optimus -a -um ADJ [XXXAO]
good, honest, brave, noble, kind, pleasant, right, useful; valid; healthy;
*
</TT></PRE>
<P>
Here we have an adjective, but it might also be a noun. The
interpretation of the adjective says that it is POSitive, and that
is the meaning listed, as is the convention for all dictionaries.
The user must generate form this the meanings for other comparisons.
Check the comparison value before deciding on the real meaning.
Again, there is an asterisk, indicating further inflected forms were trimmed out.
<PRE><TT>=>facile
facil.e ADJ 3 2 NOM S N POS
facil.e ADJ 3 2 ABL S X POS
facil.e ADJ 3 2 ACC S N POS
facilis, facile, facilior -or -us, facillimus -a -um ADJ [XXXAX]
easy, easy to do, without difficulty, ready, quick, good natured, courteous;
facile ADV POS
facile, facilius, facillime ADV [XXXBO]
easily, readily, without difficulty; generally, often; willingly; heedlessly;
*
</TT></PRE>
<P>
Here is an adjective or and adverb. Although they are related in meaning,
they are different words.
<PRE><TT>=>acerrimus
acerri.mus ADJ 3 3 NOM S M SUPER
acer, acris -e, acrior -or -us, acerrimus -a -um ADJ [XXXAO]
sharp, bitter, pointed, piercing, shrill; sagacious, keen; severe, vigorous;
</TT></PRE>
<P>
Here we have an adjective in the SUPERlative. The meanings are all
POSitive and the user must add the -est by himself.
<PRE><TT>=>optime
optime ADV SUPER
bene, melius, optime ADV [XXXAO]
well, very, quite, rightly, agreeably, cheaply, in good style; better; best;
opti.me ADJ 1 1 VOC S M SUPER
bonus, bona -um, melior -or -us, optimus -a -um ADJ [XXXAO]
good, honest, brave, noble, kind, pleasant, right, useful; valid; healthy;
</TT></PRE>
<P>Here is an adjective or and adverb, both are SUPERlative.
<PRE><TT>=>monuissemus
monu.issemus V 2 1 PLUP ACTIVE SUB 1 P
moneo, monere, monui, monitus V [XXXAX]
remind, advise, warn; teach; admonish; foretell, presage;
</TT></PRE>
<P>
Here is a verb for which the form is PLUPerfect, ACTIVE, SUBjunctive, 1st
person, Plural. It is 2nd conjugation, variant 1.
<PRE><TT>=>amat
am.at V 1 1 PRES ACTIVE IND 3 S
amo, amare, amavi, amatus V [XXXAO]
love, like; fall in love with; be fond of; have a tendency to;
</TT></PRE>
<P>
Another regular verb, PRESent, ACTIVE, INDicative.
<PRE><TT>=>amatus
amat.us VPAR 1 1 NOM S M PERF PASSIVE PPL
amo, amare, amavi, amatus V [XXXAO]
love, like; fall in love with; be fond of; have a tendency to;
amat.us ADJ 1 1 NOM S M POS
amatus, amata, amatum ADJ [XXXEO] uncommon
loved, beloved;
</TT></PRE>
<P>
Here we have the PERFect, PASSIVE ParticiPLe, in the NOMinative, Singular,
Masculine. In addition, there is the ADJective that is formed from
this participle. If the ADJective is common, it will likely have its own
dictionary entry. Sometimes there may be a special or idiomatic meaning
not obvious from the verb, or the meaning may stray from the original.
In this case, the verb is very frequent, but the use as a adjective is uncommon.
<PRE><TT>=>amatu
amat.u SUPINE 1 1 ABL S N
amo, amare, amavi, amatus V [XXXAO]
love, like; fall in love with; be fond of; have a tendency to;
</TT></PRE>
<P>
Here is the SUPINE of the verb in the ABLative Singular.
<PRE><TT>=>orietur
ori.etur V 4 1 FUT IND 3 S
orior, oriri, oritus sum V DEP [XXXAO]
rise (sun/river); arise/emerge, crop up; get up (wake); begin; originate from;
be born/created; be born of, decend/spring from; proceed/be derived (from);
ori.etur V 3 1 FUT IND 3 S
orior, ori, ortus sum V DEP [XXXBO]
rise (sun/river); arise/emerge, crop up; get up (wake); begin; originate from;
be born/created; be born of, decend/spring from; proceed/be derived (from);
</TT></PRE>
<P>
For DEPondent verbs the passive form is to be translated as if it were
active voice, so there is no VOICE given in the output.
<PRE><TT>=>ab
ab PREP ABL
ab PREP ABL [XXXAO]
by (agent), from (departure, cause, remote origin/time); after (reference);
</TT></PRE>
<P>
Here is a PREPosition that takes an ABLative for an object.
<PRE><TT>=>sine
sin.e N 2 2 NOM P N
sin.e N 2 2 ACC P N
sinum, sini N N [XXXCX]
bowl for serving wine, etc;
sin.e V 3 1 PRES ACTIVE IMP 2 S
sino, sinere, sivi, situs V [XXXAX]
allow, permit;
sine PREP ABL
sine PREP ABL [XXXAX]
without;
*
</TT></PRE>
<P>
Here is a PREPosition that might also be a Verb or a Noun.
While as a preperation it is so common that it is unlikely
that any other use would occur, there is no way to indicate that.
Just be reminded that the frequency given for a verb is for the
sum of all the couple of hundred forms of the verb, not just
the one form that is parsed.
<PRE><TT>=>contra
contra ADV POS
contra ADV [XXXAO]
facing, face-to-face, in the eyes; towards/up to; across; in opposite direction;
against, opposite, opposed/hostile/contrary/in reply to; directly over/level;
otherwise, differently; conversely; on the contrary; vice versa;
contra PREP ACC
contra PREP ACC [XXXAO]
against, facing, opposite; weighed against; as against; in resistance/reply to;
contrary to, not in conformance with; the reverse of; otherwise than;
towards/up to, in direction of; directly over/level with; to detriment of;
</TT></PRE>
<P>
Here is a PREPosition that might also be an ADVerb. This is a very common
situation, with the meanings being much the same.
<PRE><TT>=>et
et CONJ
et CONJ [XXXAX]
and, and even; also, even; (et ... et = both ... and);
</TT></PRE>
<P>
Here is a straight CONJunction.
<PRE><TT>=>vae
vae INTERJ
vae INTERJ [XXXBX]
alas, woe, ah; oh dear; (Vae, puto deus fio - Vespasian); Bah!, Curses!;
</TT></PRE>
<P>
Here is a straight INTERJection.
<PRE><TT>=>septem
septem NUM 2 0 X X X CARD
septem, septimus -a -um, septeni -ae -a, septie(n)s NUM [XXXAX]
7 - (CARD answers 'how many');</TT></PRE>
<P>
Numbers are recognized as such and given a value.
An additional provision is the attempt to recognize and display the value
of Roman numerals, even combinations of appropriate letters that do not
parse conventionally to a value but may be ill-formed Roman numerals.
<PRE><TT>=>VII
VII NUM 2 0 X X X CARD
7 as a ROMAN NUMERAL;
</TT></PRE>
<P>Beyond simple dictionary entry words, the program
can construct additional words with prefixes, suffixes and other ADDONS.
<PRE><TT>=>populusque
que TACKON
-que = and (enclitic, translated before attached word); completes plerus/uter;
popul.us N 2 1 NOM S M
populus, populi N M [XXXAO]
people, nation, State; public/populace/multitude/crowd; a following;
members of a society/sex; region/district (L+S); army (Bee);
</TT></PRE>
<P>Here the input word is recognized as a combination of a base word
and an enclitic (-que) tacked on. This particular enclitic is
extremely common and its omission, or the omission of the process
that handles it, would result in an very large number of UNKNOWNs
in the output.
<PRE><TT>=>pseudochristus
pseudo PREFIX
false, fallacious, deceitful; sperious; imitation of;
christ.us N 2 1 NOM S M
Christus, Christi N M [XEXAO]
Christ;</TT></PRE>
<P>Here there is a prefix and a base. The user must make the combination
into a word or phrase.
<P>
Generally, the meaning is given for the base word, as is usual for
dictionaries. For the verb, it will be a present meaning, even when the
tense given is perfect. For a noun, it will be the singular, and the user
must interpret when the form is plural.
<P>For an adjective, the positive meaning is given,
even if a comparative or superlative form is output.
The user is invited to expand to
comparative (-er) and superlative (-est).
For a few adjectives, the only stem in the dictionary is COMP or SUPER.
When there is just one comparison,
the WORDS dictionary gives that expanded meaning.
This might be considered inconsistant,
in that it expects the user to observe the FORM to interpret the meaning,
but it is consisent with ordinary dictionary practice.
<P>Initially there were more defective adjective entries.
I had accepted assertions in OLD or L+S and others like
'comparative does not exist'.
Later on I went over to the position that
even if theCicero did not use it, someone might.
I started generating COMP and SUPER where it seemed reasonable.
One can also count on a suffix to correct most omissions, and it will.
<P>Sometimes a word is constructed from a suffix and a stem of a different
part of speech.
Thus an adverb may be constructed from its adjective.
It will show the base adjective meaning and an indication of how to
make the adverb in English. The user must make the proper interpretation.
<P>
In some cases an adjective will be found that is a participle of a verb
that is also found. The participle meaning, as inferred by the user from
the verb meaning, is not superseded by the explicit adjective entry, but
supplemented by it with possible specialized meanings. <BR>
<BR>
<A NAME="English-to-Latin Examples">
<H4>English-to-Latin Examples</H4></A>
<P>~E (tilde E/e plus Enter/CR)
changes mode from Latin-to-English to English-to-Latin. ~L changes back.
<P>A single input English word is followed by the desired part of speech.
Omitting the part of speech defaults to all, which is not recommended
for any word which can be ambiguous. Since the program is looking for a
part of speech, it would be inconvenient to support the input of several
English words on a line. While a (@) file of words can be processed in the
English mode, it must be one word per line.
<P>Output looks much like a paper dictionary entry, with form, part of speech,
gender, etc. Also included are the WORDS coded declension/conjugation and the
TRANS flags, which give age, frequency and source, information for the user
in selecting the best trnslation. The output may also contain a vertical bar
leading the meaning. This is a continuation symbol which states that there
are other meanings for the Latin word. The user might want to run the Latin
phase of WORDS to get the full set of meanings so that no unintended conflicts
appear.
<PRE><TT>
love v
amo, amare, amavi, amatus V 1 1 [XXXAO]
love, like; fall in love with; be fond of; have a tendency to;
diligo, diligere, dilexi, dilectus V 3 1 [XXXAX]
select, pick, single out; love, value, esteem; approve, aspire to, appreciate;
amo, amare, additional, forms V 9 1 [BXXEO]
love, like; fall in love with; be fond of; have a tendency to;
ardeo, ardere, arsi, arsus V 2 1 [XXXAO]
be on fire; burn, blaze; flash; glow, sparkle; rage; be in a turmoil/love;
adamo, adamare, adamavi, adamatus V 1 1 TRANS [XXXBO]
fall in love/lust with; love passionately/adulterously; admire greatly; covet;
deamo, deamare, deamavi, deamatus V 1 1 TRANS [XXXCO]
love dearly; be passionately/desperately in love with; be delighted with/obliged
*
in prep
in PREP ABL [XXXAX]
in, on, at (space); in accordance with/regard to/the case of; within (time);
ante PREP ACC [XXXAO]
in front/presence of, in view; before (space/time/degree); over against, facing;
super PREP ABL [XXXAX]
over (space), above, upon, in addition to; during (time); concerning; beyond;
in PREP ACC [XXXAX]
into; about, in the mist of; according to, after (manner); for; to, among;
prae PREP ABL [XXXAX]
before, in front; in view of, because of;
praeter PREP ACC [XXXAX]
besides, except, contrary to; beyond (rank), in front of, before; more than;
*