Language and Names in Fiction

A name performs three functions simultaneously, whether the writer intends it or not.

Phonetic personality. Hard consonants (Cormac, Drax, Viktor) suggest strength, danger, or coldness. Soft vowel-heavy names (Elara, Ophelia, Ezio) suggest delicacy, femininity, or beauty by the conventions of English phonaesthesia. These associations are cultural rather than universal — Japanese phonaesthesia is different from English — but for an Anglophone readership, they operate automatically. The writer can use them, subvert them, or ignore them. Ignoring them is not neutral; it’s just unconscious.

Cultural positioning. "Tariq Hassan" and "Tyler Henderson" position characters in different social and ethnic contexts before the story makes a single claim about race or background. This is not a reason to avoid names that carry cultural coding; it’s a reason to choose them deliberately. The name signals a social reality. The question is whether the story will engage with that reality or treat it as decorative.

Historical resonance. Names carry the weight of famous bearers. A villain named Iago triggers Shakespearean associations even in a story set in contemporary London. A character named Cassandra carries a structural prediction about their narrative role. Writers who name characters after mythological or historical figures are making an implicit promise that the resonance will be honored, or deliberately subverted — and either can be effective, but accidental resonance that the story ignores is a loose thread.

The most successful character names are phonetically appropriate, culturally coherent with the world, and either historically resonant (when that resonance is intentional) or historically blank (when the character needs no such preloading). Very few names achieve all three by accident.

The naming conventions of geography are among the most reliable indicators of world-building competence. Consistent place naming implies a consistent cultural history; inconsistent naming implies a world assembled from convenient borrowings.

Tolkien’s Middle-earth is the standard here because the linguistic consistency is so thoroughgoing. The Shire’s hobbit place names (Hobbiton, Bywater, Buckland) are derived from English pastoral conventions. The Elvish names follow Quenya or Sindarin phonological rules depending on which elvish culture named the place. The Dwarven names follow Norse conventions. These aren’t decorative differences; they’re evidence of three distinct cultures with distinct linguistic histories that have occupied the same geography at different times and left different naming traces. The world feels ancient partly because the names behave the way real-world names behave — layered, inconsistent across cultures, coherent within them.

The failure mode is borrowing from multiple real-world languages for atmospheric effect without any logic about which culture would have named which place. A fantasy map with "Castle Schwarzwald" next to "Fort Azeroth" next to "the Shimmer Peaks" isn’t evoking anything coherent — it’s assembling linguistic textures that each gesture toward different moods without connecting to each other or to the world’s history.

Realist fiction has different naming obligations. In contemporary fiction set in real places, street names and neighborhood names should match actual geography. Placing fictional streets in real cities requires care — either use genuinely fictional neighborhoods (the approach of many procedurals) or use real ones accurately. When a New York crime novel places a chase through streets that don’t connect in the real city, it breaks the verisimilitude that the realist mode depends on.

When a fiction requires invented names for people, places, or things, the craft requirement is internal consistency rather than real-world authenticity. The reader doesn’t need to believe the names come from a real language; they need to believe the names come from the same invented language.

Phonological consistency is the minimum requirement. Decide which phonemes are available in the language and stick to them. A culture that uses harsh Germanic consonants shouldn’t suddenly have a character named Alaia. A world where all the elven names are polysyllabic and vowel-heavy shouldn’t introduce an elven character named Thrax. The inconsistency doesn’t need to be explained; readers feel it as wrongness before they can articulate why.

Morphological patterns add depth. If place names follow a consistent pattern — "ar-" prefix for cities near water, "-heim" suffix for fortified strongholds — readers begin to read the geography from the names themselves. Brandon Sanderson uses this systematically: the naming conventions in each Stormlight Archive culture follow distinct phonological rules that encode cultural identity. Alethi names sound different from Veden names from Horneater names, and the difference is consistent enough that readers use the names as cultural markers even without being told explicitly.

Readability is a constraint. Tolkien could get away with Galadriel and Saruman because the phonological rules of his naming systems produce names that English readers can pronounce with reasonable confidence. Unpronounceable names — strings of consonants, unfamiliar diacritics, apostrophes in positions that English phonology can’t parse — create a barrier rather than atmosphere. The reader who can’t mentally pronounce a character’s name can’t form a stable mental representation of them. The name becomes an obstacle rather than a portal. The rule: invented names should be easily pronounceable by the target readership, even if they don’t come from any real-world language.

For most fiction, naming conventions suffice. A consistent phonological system for names produces the impression of linguistic depth without requiring the writer to construct a grammar and lexicon.

The situations that require actual constructed languages are limited: fiction in which characters speak the invented language in dialogue that readers need to parse; fiction whose central intellectual argument is about language itself (Ursula K. Le Guin’s The Dispossessed, China Miéville’s Embassytown); and fiction whose cultural authenticity demands it because the invented language maps directly onto a culture the story is making serious claims about.

Tolkien’s Quenya and Sindarin were necessary for him personally — he invented the languages first and built the world around them — but they’re not replicable as a model for most writers. The languages gave his world its distinctive depth, but that depth came at the cost of decades of work. For a writer building a fantasy world over the course of a novel, a consistent naming system with clear phonological rules is the practical equivalent. It creates the same impression of depth without requiring linguistic expertise.

Embassytown is the one modern novel where the constructed language is load-bearing: the entire plot turns on specific properties of how the aliens use language, and Miéville had to design those properties precisely to make the plot work. That’s different from inventing a fantasy naming system for atmosphere.

Realist fiction imposes the narrowest naming constraints. Names should be appropriate to the character’s time, place, class, and culture. A working-class Irish-American from South Boston in the 1970s named Xanthe Beaumont is named by someone who hasn’t thought about what names people actually had in that context. Contemporary realist fiction that doesn’t attend to demographic naming conventions makes the world feel assembled rather than observed.

Historical Fiction adds the obligation of period accuracy. Naming conventions shift substantially across historical periods — names common in the 1600s are rare today; names common today would be anachronistic in the 1600s. Research is required, and shortcuts are visible to readers with knowledge of the period.

Fantasy relaxes the historical constraint but imposes internal consistency in its place. The freedom of invention comes with a responsibility that realist fiction doesn’t have: the writer is the sole authority on what the naming conventions are, and readers will notice violations of those conventions even without being able to name the rule being broken.

Science Fiction divides along the realism axis. Near-future science fiction set on recognizably human Earth should use names that feel like plausible extrapolations of current naming trends. Far-future space opera can invent freely, subject to the consistency requirements above.

Phonological clash — mixing naming systems derived from incompatible real-world languages — is the most common failure in fantasy. The fix is to choose one primary phonological model and derive all names from it, with distinct secondary models for distinct cultures.

Nominal schematism — giving characters names that so transparently encode their function or moral status that the names read as labels rather than identities — undermines character complexity. A villain named "Malachar" or a wise mentor named "Eldric" is a character the writer has categorized rather than conceived. The name signals the archetype before the character can become more than one.

Apostrophes as atmosphere — using apostrophes in invented names to signal alien-ness without any phonological logic about what they’re supposed to do — has become so common in fantasy and science fiction as to be a genre cliché. If an apostrophe marks a glottal stop, a click, or a tonal distinction, that’s a phonological decision. If it’s there because it looks exotic, it’s decorating a naming system rather than constructing one.

Real-world names in the wrong context — using names that carry strong contemporary cultural associations (first names that are extremely contemporary, surnames that are ethnically specific) in historical or fantastical settings where they shouldn’t exist — creates the same verisimilitude problem as anachronistic technology. The name is a piece of evidence about the world; like all evidence, it must be consistent with the other evidence the story presents.

Internal Consistency frames the broader principle of which language and naming are a specific application. Fantasy and Sci-Fi World-Building treats the architecture of speculative worlds, of which linguistic design is one layer.