<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16643" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT color=#800080 size=4>I thought that I would share another option for
Dictionary software programs specific for indigenous languages. I
personally am acquainted with Doug Parks and Raymond Demallie at Indiana
University, and the high quality of their expertise and materials. I
thought the Lexi-group would be interested in part, of the discussion I have
recently had with the Kaw (Kansa) Nation Language Program Director.
He states: </FONT></DIV>
<DIV><FONT color=#800080 size=4></FONT> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>The program we have been using to develop the
expanded Kaw dictionary is the Indiana Dictionary Database, from the American
Indian Studies Research Institute at Indiana University (<A
href="mhtml:{F35F5EBF-401E-471A-88FC-D2C5039D5CFF}mid://00000016/!x-usc:http://www.indiana.edu/~aisri/projects/idd/idd.shtml">http://www.indiana.edu/~aisri/projects/idd/idd.shtml</A>).
It's a big and complicated program as far as editing is concerned, with maybe
twenty or more tables associated with each
entry. The on-board search engine is the best way
to navigate through it, but there is also a "combo screen" view that
allows you to browse through the entries at a glance, either from English
to Kaw or Kaw to English. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That said, anytime we feel the database is
"full enough" to fill some need in the community, we can export all the
material into other formats for the purpose of producing a simpler user's
dictionary. We did one of those last summer. It's a very bare-bones
English to Kaw dictionary book file. You can download the .pdf at <A
href="mhtml:{F35F5EBF-401E-471A-88FC-D2C5039D5CFF}mid://00000016/!x-usc:http://www.kawnation.com/WebKanza/LangResources/nglshknzdctnry.pdf">http://www.kawnation.com/WebKanza/LangResources/nglshknzdctnry.pdf</A>.
I think most entries in this version have the English entry, any related Kaw
glosses, and grammatical class (part of speech), and that's it.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>(Later) the examples and paradigmatic
forms, we'll print another version that will offer more information, and will be
searchable by ANY word that happens to appear anywhere in the entry form.
So, let's say you know the word kóⁿbla, but can't remember that it's the 1st
Singular/ "I" form of the verb góⁿya, 'to want.' You'll be able to search
for kóⁿbla, and it will turn up as a paradigmatic form for góⁿya under the
English entry 'want.'</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I think this is the crux of the discussion you
sent: Editing and use are separate considerations. I think if you're
using a special program like IDD, Shoebox/Toolbox, or D-Base , then you're
really working on the editing side, and you'll have very different concerns and
approaches than the end users of the product will have. You may in
fact need to worry about special parsers and inflectional/ derivational
concerns from time to time, as the discussion participants brought up.
You'll need to worry about back-and-forth indexing, repeated/ redundant
entries, integrity of parallel entry forms,
etc. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>End users, on the other hand, will
probably want something that looks like every other dictionary on the
planet: A book. Even if you're planning on producing an eBook with all the
searching benefits, I would wager that the end users will think of it
as just the file-version of a book, essentially an unprinted
dictionary manuscript. Their users' concerns, however, will be
addressed during the editing phase with a lot of preliminary planning and work
on the part of the editors. In my kóⁿbla example, for instance, end users
will be able to hunt down the meaning of a headword form through the search
function provided we do all the legwork well in advance of producing the
"end product" dictionary.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That's my opinion, anyway.</FONT></DIV>
<DIV><FONT face=Arial size=2>-Justin</FONT></DIV></DIV>
<span width="1" style="color: white;"/>__._,_.___</span>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- |**|begin egp html banner|**| -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=11682781/grpspId=1709195911/msgId=4474/stime=1210697003" width="1" height="1"> <br>
<!-- |**|end egp html banner|**| -->
<!-- |**|begin egp html banner|**| -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px solid #666; padding: 5px 0;" >
Your email settings: Individual Email|Traditional <br>
<a href="http://groups.yahoo.com/group/lexicographylist/join;_ylc=X3oDMTJnYnRnNjZqBF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMjEwNjk3MDAz">Change settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:lexicographylist-digest@yahoogroups.com?subject=Email Delivery: Digest">Switch delivery to Daily Digest</a> | <a href = "mailto:lexicographylist-fullfeatured@yahoogroups.com?subject=Change Delivery Format: Fully Featured">Switch to Fully Featured</a> <br>
<a href="http://groups.yahoo.com/group/lexicographylist;_ylc=X3oDMTJlaWdqZmwxBF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNocGYEc3RpbWUDMTIxMDY5NzAwMw--">
Visit Your Group
</a> |
<a href="http://docs.yahoo.com/info/terms/">
Yahoo! Groups Terms of Use
</a> |
<a href="mailto:lexicographylist-unsubscribe@yahoogroups.com?subject=Unsubscribe">
Unsubscribe
</a>
<br>
</div>
<br>
<!-- |**|end egp html banner|**| -->
<span style="color: white;"/>__,_._,___</span>
</BODY></HTML>