Parentheses and asides: what French text to speech does with them

Written French loves an aside. It opens a parenthesis to slip in a date, sets a phrase between commas to attribute it, suspends the main thread for a comment, then picks the thread back up. On the page these detours cost the reader nothing: the parenthesis and the commas say "this is off to the side, keep the thread." To the ear, everything rides on the voice, and that is exactly where a text to speech engine shows what it can do. This article looks at what it really does with parentheses and asides in French, on sentences you can reproduce.

The test sentence

Take a sentence that stacks the asides, the kind the press and specialist blogs produce all day:

> Le conseil municipal (réuni mardi soir, en présence du préfet) a voté le budget, que l'opposition juge, elle, insincère, avant la trêve estivale.

There are two different detours here. The parenthesis "(réuni mardi soir, en présence du préfet)" adds background: remove it and the sentence still stands. The aside ", elle," is a very short intrusion that underlines a contrast. A human reader lowers the voice a little and speeds up slightly across these stretches, then rises again to resume the main point. An engine has to decide what to do with a punctuation mark that is never spoken but that carries all the meaning.

What the engine does with parentheses

First, the reassuring part: parentheses are not read out. A good engine never says "open paren." It treats them as a signal, not as a character to pronounce. That is the minimum test, and most recent engines pass it. Some tools tuned first for English still trip on awkward cases, but on a plain French parenthesis the content is read and the marks vanish, which is the behaviour you want.

Second, and finer: the pause. Opening a parenthesis calls for a short silence, and closing it does too. An engine that honours that breath marks the boundary cleanly between the main clause and the aside, and the listener follows without effort. An engine that skips it glues the parenthesis to the rest, and the sentence turns into a block where you can no longer tell what is central from what is incidental. Punctuation is what carries that pause, which is why a well punctuated text listens better than a careless one, a point we set out in our piece on how text to speech breathes with punctuation.

Where the limit shows is intonation. An actor would clearly drop the voice inside the parenthesis to signal "this is off to the side," then lift it again at the close. Synthetic speech reads the parenthetical content on roughly the same melodic line as the rest. It marks the pause, but it does not move down into the lower register. This is not a pronunciation flaw: the text stays perfectly clear. It is a limit of meaning, because the engine does not rank what is main against what is secondary. Better to know this before promising a newsroom an actor's delivery.

Short asides, the real trap

A long parenthesis reads acceptably because the pause alone sets it apart. The short comma aside is trickier. In "que l'opposition juge, elle, insincère," the word "elle" is framed by two commas to mark emphasis. On the page the eye absorbs it. Out loud, if the engine plants two firm pauses around a single word, the sentence stutters and the emphasis turns into hesitation. If instead it swallows the commas, the contrast is lost. Most engines take the second route: they smooth a very short aside rather than overplay it. The result is fluid, but flat.

The same mechanism hits the attribution aside, the little "dit-il," "selon la mairie," "précise le rapport" dropped into the middle of a sentence. It should come out lower and quicker than the rest, so it does not carry as much weight as the point it attributes. No consumer engine makes that shift automatically today. The remedy sits in the writing: a short aside, cleanly set off by commas, reads acceptably even without modulation, as long as you do not stretch it. A fifteen-word aside wedged into the middle of a sentence tires the ear whatever the engine.

Writing for the ear without thinning the text

The good news is that you do not have to give up asides to be read well. A few habits are enough. Prefer a clean parenthesis to an endless aside when the information really is secondary: the pause will do the work the intonation does not. Keep attribution asides short, and set them at the end of the sentence where they weigh less. And reread aloud any two-level sentence, one where an aside sits inside another, because that is where even a human reader hesitates.

When a parenthesis or an aside contains a term the engine mishandles (a proper name, an initialism, a foreign word), the move is not to touch the visible text, which must stay exact, but to go through the pronunciation lexicon. You declare the intended reading once, and it applies everywhere, including inside the parentheses. The text stays what the reader sees, the correction lives beside it.

What to take away

Text to speech handles the mechanics of asides well in French: it does not voice the parentheses, it respects the pauses that punctuation announces, and it cleanly detaches a long parenthesis from the main clause. What it does not yet do is perform the aside, drop into the lower register to say "this is off to the side" and then climb back. Knowing where that line falls avoids two mirror mistakes: thinking an engine gives you an actor's relief, and thinking it stumbles on difficulties it in fact handles well. If you want to check for yourself, our checklist for evaluating a neural voice includes a passage with parentheses and asides, and you can run it against any tool, ours included. That standard, sentence by sentence, is what drives our work on reading French aloud, described on the French text to speech page.

Read next

• Clickable chapters and links to the second: navigating an audio article
• Hyphenated compounds: the quiet trap for French text to speech
• Cognitive accessibility, Easy Read and audio: what the voice fixes, and what it doesn't