Notes to Fiction Writers

Should Fictional Names Be Translated?

Names, clues, jokes, world-building, and the occasional name that knows too much.

A fictional name can be just a name.

A character may be called Mara because the author liked the sound. A city may be called Velmorn because it appeared at 2:17 a.m. and refused to leave. A tavern may be called The Blue Hart because every fantasy world needs somewhere to serve stew and bad decisions.

Fine. Not every name needs to be translated. Not every name needs an explanation. Not every name is secretly carrying three prophecies, a linguistic puzzle, and the emotional collapse of a dynasty.

But sometimes, a fictional name is doing more work than it admits. It may contain a joke, a clue, a warning, a social marker, a piece of geography, a family history, or a tiny shard of world-building wearing capital letters and pretending to behave.

The real question is not: should this name be translated? The better question is: what does this name do?

Why names matter in English-to-French translation

In English, your reader may understand part of a name instantly. A word like winter, thorn, black, hollow, silver, or grave brings mood with it before the story has explained anything.

In French, that immediate signal may disappear. The name can still sound beautiful, memorable, or mysterious, while quietly losing the clue it was carrying.

That does not automatically mean the name should be translated. It means the decision should be conscious.

When names should be translated

Some names carry meaning so directly that leaving them untouched would remove part of the reader’s experience. This often happens with puns, transparent English words, descriptive place names, symbolic titles, or comic effects.

Take Diagon Alley in Harry Potter. In English, the name sounds like “diagonally.” It suggests a hidden, sideways route into the magical world. The French translation, Chemin de Traverse, does not copy the pun letter by letter. It recreates the function: a side path, slightly apart from the ordinary world.

That is the point. Good name translation is not always about translating the dictionary meaning. It is about translating the effect.

The same applies to many comic or voice-driven fantasy names. In Terry Pratchett’s Discworld, a name like Rincewind becomes Rincevent in French. The name is rebuilt so the French reader receives some of the oddness, motion, and comic energy.

In these cases, preserving the English spelling may preserve the shell, but lose the experience.

When untranslated names hide meaning

Leaving a name in English can preserve atmosphere. It can also bury meaning where the French reader will never find it. Rude, but common.

Consider Winterfell. For an English-speaking reader, winter is immediate: cold, North, hardness, threat, history. For a French reader, Winterfell can still feel like a strong fantasy name, but the transparent English signal becomes less transparent.

The mood survives. Some of the meaning may not.

That does not mean Winterfell should necessarily have been translated. A clumsy French version could easily do more damage than the loss it was trying to repair. The literary cemetery is full of noble attempts.

But it is exactly the kind of name a translator needs to notice.

This also matters when a name comes from another language, myth, religion, folklore, or a private naming system. Fantasy and science fiction authors often borrow from Latin, Old Norse, Welsh, Hebrew, Greek, Sanskrit, or a carefully invented pseudo-language cooked at midnight with dramatic intent and insufficient sleep.

Those names may be meant to feel ancient, sacred, alien, academic, brutal, ceremonial, or deliberately opaque. That background matters, even if the name itself stays untouched.

When names should stay untouched

After all that, it may sound as if every meaningful name should be translated. Convenient theory. Shame about literature.

Some names should stay exactly as they are.

Arrakis does not need to become “Sandy Murder Planet” in French. Tempting, yes. Wise, no.

Narnia does not need to be explained. Aslan does not need a French equivalent. Piranesi does not need to be rebuilt just because the reference has a history.

Some names work because of sound, myth, rhythm, opacity, or cultural echo. Their power comes from the fact that they feel like names belonging to a world, not labels pasted onto one.

Translating them would not add meaning. It would flatten the atmosphere. And fantasy worlds do not need extra flattening. Maps already do enough damage.

When translated names become debatable

A translated name can be clever, useful, and memorable — and still change the way readers perceive a character or a place.

Severus Snape becomes Severus Rogue in French. It works. It sounds sharp. It suggests someone unpleasant, harsh, suspicious.

But it also makes the character’s darkness more obvious. Snape is cold and snake-like, but still slightly ambiguous. Rogue points the French reader rather firmly toward “do not trust this man.”

Subtle? Less so.

That does not make the translation wrong. It means the translation chooses one effect and inevitably shifts another.

The same can happen with place names. King’s Landing becomes Port-Réal in French. Elegant? Yes. But it shifts the image slightly: from a landing place, almost an event fixed into geography, toward royal power and a named city.

Again: not wrong. Different.

What writers can do before translation

If you are writing fiction in English and considering a French translation, or in any language as a matter of fact, you do not need to prepare a forty-two-page naming bible for every horse, dagger, inn, forest, moon, and emotionally unstable prophecy.

Please rest. Hydrate. Step away from the spreadsheet.

But you should make a note of names that matter.

These notes do not dictate the translation. They give the translator the map before anyone walks into the swamp.

For example, a short note like “Thornmere is meant to sound beautiful but hostile” is enough to prevent the name from being treated as decorative noise.

Your translator does not need to be told how to translate every name. That would be horrifying for everyone involved.

But they do need to know which names are load-bearing.

The rule, if there is one

So, should fictional names be translated?

Sometimes, yes. Sometimes, no. Sometimes, adapted. Sometimes, left untouched but supported by context. Sometimes, debated quietly over coffee while the dictionary pretends not to judge.

The rule is not “translate names” or “never translate names.”

Find out what the name does. Then decide what the French reader needs to receive: the sound, the meaning, the effect, the mystery, the joke, or the warning.

A name is not always just a name. Sometimes it is a small piece of the book’s machinery. And if that machinery matters, it should not cross into French by accident.