<div>Catherine,</div> <div> </div> <div>I would like to participate in the roundtable. I'm working on a revised Biloxi dictionary, still very much in progress. I think this would be a good forum for discussion and ideas.</div> <div> </div> <div>Dave Kaufman<BR><BR><B><I>Catherine Rudin <carudin1@wsc.edu></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Call for Participation: Siouan Dictionaries Roundtable<BR>Siouan and Caddoan Conference<BR>Joplin, MO, June 20-21 2008<BR><BR>This year's Siouan and Caddoan Conference will include a roundtable<BR>session on making dictionaries of Siouan languages: pitfalls,<BR>successful practices, projects in progress, helpful hints, deeper issues<BR>of purpose and philosophy. <BR><BR>Your participation in this session is invited on two levels:<BR><BR>(1) If you would like an official spot on the program to give a brief<BR>presentation
on your own dictionary project, please get in touch with me<BR>as soon as possible. <BR>Catherine Rudin: carudin1(at)wsc.edu<BR>As of now there are two presentations scheduled, one on the recently<BR>completed Hocank dictionary (Iren Hartmann) and one on the newly-funded,<BR>about-to-begin Omaha and Ponca dictionary (Mark Awkuni-Swetland,<BR>Catherine Rudin, Rory Larson). We'd welcome additional presentations. <BR>Description/demonstration of any Siouan-language dictionary or<BR>dictionary project, at any stage of completion, would be appropriate. <BR>Depending on interest we'll adjust the time per project and if necessary<BR>split into a couple of sessions. <BR><BR>(2) We are counting on lots of audience participation - the main point<BR>of the panel, at least from my perspective, is to pick the collective<BR>brain of the Siouan linguistic community, so those of us just embarking<BR>on dictionary projects can benefit from all the expertise out there. <BR>Calling it a
"roundtable" is meant to suggest dialogue rather than<BR>lectures. To this end it would be great if everyone would think about<BR>issues involved in constructing a dictionary beforehand and bring in<BR>ideas, questions, answers, examples to show. We might even try to come<BR>up with a list of issues in advance, as a kind of agenda guide for the<BR>open discussion portion of the session.<BR><BR>Just to get the conversation going, here's a possible starter list. <BR>Feel free to add (or subtract, combine, or modify). <BR><BR>-What information should dictionary entries include?<BR>-What kinds of "front matter" are useful, essential, expendable? <BR>(grammar sketch, pronunciation guide, frequency lists, ...)<BR>-Grammar issues: how to best cover things like verb conjugation,<BR>allomorphy, etc. What grammatical categories need to be labelled? Do<BR>roots, prefixes, suffixes get separate entries, or do only whole words<BR>get listed?<BR>-Alphabetization: Does "ch" come after
all of the "c" words, or between<BR>ce and ci? (are ch, sh, th etc. "letters" for purposes of<BR>alphabetization? What about long vowels? What to do about alternative<BR>orthographies?<BR>-User-friendliness issues: what is it important to think about for<BR>various types of users (linguists, tribe members, language students,<BR>non-specialist public, etc.)<BR>-What makes a good example sentence? How many should be included?<BR>-Cultural information? How much to include, and how?<BR>-Tech issues: what are the best software/protocols to use, and why? <BR>What about linking sound files, pictures, etc.?<BR>-Electronic vs. paper dictionaries (how do desiderata or possibilities<BR>for database vs. printed version vs. web-based version differ?; what<BR>kind of field structure is necessary in order to include all needed<BR>information for all three?)<BR>-Pitfalls to avoid.<BR><BR>Looking forward to seeing many of you in Joplin, and to hearing
your<BR>insights!<BR>Catherine<BR><BR><BR></BLOCKQUOTE><BR><p>
<hr size=1>Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>