Computer-Assisted Language Comparison: State of the Art. (22nd May 2020)

• Record Type: Journal Article
• Authors: Wu, Mei-Shin; Schweikhard, Nathanael E.; Bodt, Timotheus A.; Hill, Nathan W.; List, Johann-Mattis
• Is Part Of: Journal of open humanities data. Volume 6(2020)
• Publication Date: 2020-05-22
• Subjects: computer-assisted -- language comparison -- historical linguistics -- Hmong-Mien language family; Humanities -- Periodicals; 001.3
• DOI: 10.5334/johd.12
• Languages: English
• ISSNs: 2059-481X

Abstract

Historical language comparison opens windows onto a human past, long before the availability of written records. Since traditional language comparison within the framework of the comparative method is largely based on manual data comparison, requiring the meticulous sifting through dictionaries, word lists, and grammars, the framework is difficult to apply, especially in times where more and more data have become available in digital form. Unfortunately, it is not possible to simply automate the process of historical language comparison, not only because computational solutions lag behind human judgments in historical linguistics, but also because they lack the flexibility that would allow them to integrate various types of information from various kinds of sources. A more promising approach is to integrate computational and classical approaches within a computer-assisted framework, "neither completely computer-driven nor ignorant of the assistance computers afford" [1, p. 4]. In this paper, we will illustrate what we consider the current state of the art of computer-assisted language comparison by presenting a workflow that starts with raw data and leads up to a stage where sound correspondence patterns across multiple languages have been identified and can be readily presented, inspected, and discussed. We illustrate this workflow with the help of a newly prepared dataset on Hmong-Mien languages. Our illustration is accompanied by Python code and instructions on how to use additional web-based tools we developed so that users can apply our workflow for their own purposes.