← Latest papers
📄 social_science

The Development of Proto-Indo-European *kn- in Slavic

This paper argues that the Proto-Indo-European cluster *kn- developed into *gn- in Proto-Slavic due to the voicing of *k- before *n-, a conclusion supported by five etymological examples including words for "nit," "shinbone," and "anger."

Original authors: Ranko Matasović

Published 2026-10-09
📖 5 min read🧠 Deep dive

Original authors: Ranko Matasović

Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). ✨ This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Languages are not static monuments; they are living streams that change course over centuries, carrying the sounds and shapes of their ancestors into new forms. One of the most fascinating ways to trace these changes is by looking at how specific combinations of sounds behave as languages split apart and drift apart. In the family of Indo-European languages, which includes everything from English and German to Greek and Sanskrit, there is a particular cluster of sounds that has long puzzled linguists: the combination of a hard "k" sound followed immediately by an "n." In many ancient branches of this family, such as Celtic and Germanic, words began with this "kn" sound, like the English word "knight" or the German "Knie" for knee. However, when linguists look at the earliest stage of the Slavic languages, the ancestor of Russian, Polish, and Croatian, they find a curious gap. There are no reconstructed words in this ancient Slavic tongue that begin with "kn." For a long time, scholars assumed these words simply vanished or were replaced by other terms, but a new analysis suggests a different story: the sounds did not disappear; they transformed.

The question of where these missing words went is central to understanding the history of the Slavic people and their language. If a sound pattern exists in the common ancestor of a language family but is missing in one major branch, it usually means something systematic happened to it. In this case, the researcher Ranko Matasović from the University of Zagreb proposes that the ancient "kn" sound did not vanish but rather shifted into a "gn" sound. This means that where other languages kept the hard "k," the Slavic ancestors voiced it, turning it into a "g" before the "n." This is not a random change but a regular rule that applied to the beginning of words. To prove this, the paper does not rely on vague theories but instead reconstructs five specific words that likely underwent this transformation, showing how their meanings and forms align with this new sound law.

The first and most solid example concerns the word for a "nit," the egg of a louse. In Old English, this word was "hnitu," preserving the ancient "kn" sound. In Slavic languages, the word for the same thing is "gnida." Matasović argues that this is not a coincidence but a direct result of the sound shift. The ancient root likely began with "kn," and as the Slavic language evolved, that initial "k" softened into a "g" before the "n," creating the word "gnida" that is still used in various forms across Slavic countries today. This connection is supported by similar words in other languages that hint at the original "kn" sound, confirming that the Slavic version is a regular development rather than a borrowed word or a lost term.

The second example involves the shinbone. In many Indo-European languages, the word for "knee" is related to the shin, but the Slavic word for shinbone, "gnat," has been difficult to explain. Traditional theories tried to link it to the word for "knee," but the sound patterns did not fit. Matasović suggests a different origin: a root meaning "to groove" or "to hollow out." If the original word began with "kn," the shift to "gn" would perfectly explain the Slavic "gnat." This makes sense semantically as well, since a shinbone is a hollow, tube-like structure, much like a groove. This connection links the Slavic word to ancient roots found in Germanic and Celtic languages that also describe grooving or scraping, all pointing back to a single ancestor word that started with "kn" before becoming "gn" in Slavic.

The paper also examines words for "vermin" or "insects" and "anger," where the evidence is slightly less certain but still compelling. The Slavic word for vermin, "gnus," likely comes from a root meaning "to itch" or "scratch," a concept found in Baltic languages with a "kn" beginning. Similarly, the word for "anger," "gněv," is proposed to come from a root meaning "to tear" or "scratch," which also appears in other ancient languages with a "kn" start. In both cases, the shift from "kn" to "gn" provides a consistent explanation for the Slavic forms, whereas previous theories struggled to connect them to their roots. Even the verb meaning "to light a fire" or "stir up," "gnětiti," fits this pattern, linking to words for sparks or tinders in other languages that began with "kn."

What makes this finding significant is that it fills a gap in our understanding of how Slavic phonology works. For decades, handbooks of Slavic history noted the absence of initial "kn" words but offered no clear rule for what happened to them. Some scholars thought the sounds were simply lost, but the idea that they all vanished without a trace is statistically unlikely. Instead, the evidence suggests a regular, predictable change where the "k" became a "g." This rule appears to have no exceptions in the reconstructed vocabulary. While some of the proposed word connections are more tentative than others, the core argument stands firm: the Slavic languages did not lose the "kn" sound; they changed it into "gn." This discovery allows linguists to reconstruct the ancient vocabulary of the Slavic people with greater accuracy and deepens our understanding of how these languages evolved from their common Indo-European ancestor.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →