11.07.2015 Views

View the meeting handbook - Linguistic Society of America

View the meeting handbook - Linguistic Society of America

View the meeting handbook - Linguistic Society of America

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Thursday, 4 JanuaryTutorialA Field Linguist's Guide to Making Long-Lasting Texts and DatabasesCapistrano Room4:00 - 7:00 PMOrganizers:Sponsor:Participants:Jeff Good (University at Buffalo, State University <strong>of</strong> New York)Heidi Johnson (University <strong>of</strong> Texas, Austin)Open Language Archives Community (OLAC) Working Group on OutreachLaura Buszard-Welcher (The Rosetta Project)Deborah Anderson (University <strong>of</strong> California, Berkeley)Michael Appleby (The LinguistList)Jessica Boynton (Eastern Michigan University)Naomi Fox (University <strong>of</strong> Utah)Connie Dickinson (Max Planck Institute for Psycholinguistics, Nijmegen/University <strong>of</strong> San Francisco, Quito)Over <strong>the</strong> last several decades, <strong>the</strong>re has been a dramatic increase in <strong>the</strong> technologies available for language documentation. This islargely a positive development--our records <strong>of</strong> an endangered language are no longer limited to ink on paper but can now includeaudio and video recordings <strong>of</strong> rich interactions among speakers. Field linguists know how to organize and analyze <strong>the</strong> data <strong>the</strong>ycollect, facilitating multiple uses for datasets and improving consistency in data entry. A plethora <strong>of</strong> s<strong>of</strong>tware programs is availablefor creating texts and databases, from ASCII text editors to web-accessible SQL databases. And <strong>the</strong>rein lies a problem: How canlinguists choose <strong>the</strong> tools that will serve <strong>the</strong>ir needs best in <strong>the</strong> present, while producing materials that will survive long into <strong>the</strong>future?The first problem is finding a font that represents <strong>the</strong> characters needed for transcribing and analyzing <strong>the</strong> language being documented.In <strong>the</strong> past, linguists have had to rely on fonts such as SIL Doulos, which had a life span <strong>of</strong> only a few years and were nearlyimpossible to port from one computer platform to ano<strong>the</strong>r. The solution to <strong>the</strong> font problem is Unicode, which defines a standard set<strong>of</strong> characters that includes all <strong>the</strong> characters for <strong>the</strong> world's most common writing systems, as well as <strong>the</strong> International PhoneticAlphabet.The next problem is choosing a format for digital files that can be used for <strong>the</strong> duration <strong>of</strong> a language documentation project andbeyond. Most <strong>of</strong> <strong>the</strong> readily available s<strong>of</strong>tware, such as Micros<strong>of</strong>t Word and FilemakerPro, produces files in proprietary formats thatcan only be read by <strong>the</strong> original program. Even files made a mere decade ago may not be readable using <strong>the</strong> latest version <strong>of</strong> <strong>the</strong> sameprogram. Linguists need to be able to produce files that <strong>the</strong>y can continue to use year after year, without having to continually converteach document to a new version <strong>of</strong> <strong>the</strong>ir s<strong>of</strong>tware. The solution is simple: Work should be saved frequently in nonproprietary, openformats.Commercial s<strong>of</strong>tware is also <strong>of</strong>ten not well-suited for language documentation tasks. Recordings need to be transcribed andannotated; most linguists want to interlinearize at least some <strong>of</strong> <strong>the</strong>ir texts; datasets, such as lexicons, need to be constructed in formatsthat support analysis, cross-referencing, and multiple styles <strong>of</strong> output. There is s<strong>of</strong>tware specifically created for languagedocumentation tasks, but <strong>the</strong> learning curve for much <strong>of</strong> it is steep, and <strong>the</strong> documentation is <strong>of</strong>ten inadequate for <strong>the</strong> beginning user.The purpose <strong>of</strong> this tutorial is to recommend tools and strategies for creating long-lived and useful texts and databases for languagedocumentation. The speakers present a set <strong>of</strong> commonly-used s<strong>of</strong>tware tools with tips for getting started and ideas for fully exploiting<strong>the</strong> tools' capabilities. The ultimate goal <strong>of</strong> this tutorial is to aid field linguists in gaining mastery <strong>of</strong> a small suite <strong>of</strong> tools that willexpedite <strong>the</strong>ir data collection, entry, and management tasks so that <strong>the</strong>y can focus <strong>the</strong>ir time and attention on <strong>the</strong> real work <strong>of</strong>translation and analysis.73

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!