Speak your punctuation while dictating

Coii VoiceInput does not interrupt your speech to ask for punctuation. Say "period" or "comma" while you are dictating, and the punctuation lands in your text. The app does not stop listening, and you do not have to release the key. Continue speaking and the next sentence capitalizes automatically.

How spoken punctuation works

When you dictate, every word goes through the same text filters. Those filters recognize punctuation commands — words like "period", "comma", "question mark" — and replace them with actual punctuation marks.

• You say: "This is my thought period I will continue"
• You get: "This is my thought. I will continue"

The period appears and the next letter capitalizes. This happens in real time as you speak. You do not have to stop or release the key. The same system works whether you are dictating into a terminal, writing code comments, or composing long documents.

Built-in punctuation commands

The default commands are what you would say aloud if you were dictating to a human:

These commands apply throughout your dictation. You can use them in the middle of a sentence, between words, at the beginning, or at the end. They are recognized the same way whether you are dictating an email, a code comment, or a terminal command.

When punctuation is automatic

Some punctuation is applied by the text filters without you having to say it:

• Spacing after periods, question marks, and exclamation marks: After you say "period", the next word is automatically preceded by a space and capitalized.
• Comma spacing: A comma followed by a space.
• Apostrophes in contractions: Words like "don't", "it's", "we're" are recognized as single words by the engine, not as multiple words with an apostrophe between them.

You do not have to dictate the space or capitalization after punctuation — they happen automatically.

Building a custom punctuation dictionary

The built-in commands are fine for most people, but if you prefer different names for punctuation, build a dictionary. This is especially useful if:

• You speak another language and want punctuation commands in that language
• A punctuation command conflicts with a word you use frequently
• You want shorter commands: period could become just p, or "full stop"
• You want multi-character commands: newline for Enter, tab for Tab

Examples:

Every entry you add overrides the built-in command. If you add fin → ., then saying "fin" produces a period and "period" is no longer recognized as a punctuation command — it becomes ordinary text to dictate.

Dictionary entries apply everywhere: to your terminal commands, your code comments, your emails, your documents. If you set up a punctuation command, it works the same way across all your dictation.

Dictating with multiple punctuation marks

Some writing styles use multiple punctuation marks in sequence: ellipses, dashes with spaces, combinations like "?!". Speak them individually or add them to your dictionary as a single command:

Individual commands (what you say aloud):

• word period period period → word...
• thought dash dash thought → thought -- thought

Dictionary entries (for frequently-used combinations):

• ellipsis → ...
• emdash → —
• question exclamation → ?!

Ellipses are common enough that you might add one. Question-exclamation combinations are rare, so dictating them individually is probably fine.

Punctuation in code and technical writing

Terminal commands, code comments, and technical documentation often use punctuation differently than prose:

• Commenting: # this is a comment period easy to read → # this is a comment. easy to read
• URLs: Speaking a URL requires dictating slashes, which is why developers often use a dictionary entry for full paths
• Inline code: If you are dictating prose with code examples, you need to signal where code starts and ends. Add dictionary entries like backtick or code start to mark them

When dictating code comments, punctuation follows the same rules as any other dictation. The difference is that code comments often have specific formatting conventions — a hash, a space, then the comment. Building dictionary entries for your code style (like comment → # ) saves time and ensures consistency.

For screenwriters and authors, stage directions and character names often have their own punctuation rules:

INT. COFFEE SHOP dash DAY period
ALICE period
You always order the same thing dot dot dot

This dictates as:

INT. COFFEE SHOP - DAY.
ALICE.
You always order the same thing...

Add dictionary entries to make your formatting commands shorter: scene → INT. for a scene heading. Screenwriters benefit from building punctuation and formatting commands that match their writing format, so each session becomes faster and more automatic.

When not to say punctuation commands

Some situations are clearer if you let the app handle punctuation:

Dialogue and quotation: If you are dictating dialogue, you usually want a double quote at the start and end. Rather than say "open quote, then speak the line, then close quote", add a dictionary entry:

• dialogue → "
• Then dictate: dialogue my character's dialogue close quote
• Result: "my character's dialogue"

Or build a full dialogue entry: dialogue start alice → ALICE: " and dialogue end → "

Lists: If you are making a bulleted or numbered list, punctuation is often implied by the list format. Rather than saying "period" after each item, focus on the content and format the list afterward.

Prose in flow: When you are in full prose flow — writing an article or an email — focus on words and meaning. Punctuation commands interrupt the rhythm. Dictate more naturally, like dictating to a transcriber, and touch up punctuation afterward in the places where it matters most.

Handling abbreviations and special cases

Some writing uses punctuation in unusual ways:

Abbreviations: U.S., Ph.D., etc. These are abbreviations where each letter might have a period. You can:

• Add dictionary entries: us → U.S., phd → Ph.D.
• Or say the abbreviation aloud and add periods: U S period

Possessives: The apostrophe in "Alice's" is usually recognized by the engine without you having to speak it. If it is not, add an entry: apostrophe s → 's

Contractions: Most contractions ("don't", "can't", "it's") are recognized as single words. The engine adds the apostrophe automatically. If one is not recognized, add a dictionary entry.

Ellipses: Three periods (...) can be said as period period period or added as a single entry: ellipsis → ...

Punctuation in different languages

If you are dictating in multiple languages, punctuation commands work across both:

• An English speaker can say "period" and get a period, whether they are dictating in English or Spanish
• A Spanish speaker might prefer to say "punto" for a period in either language
• The dictionary entries you create apply to every language you dictate

For some punctuation marks, different languages have different conventions:

If you are writing in Spanish and need Spanish dialogue marks, add a dictionary entry: dialogue → «. The same principle applies to any punctuation convention that differs from English.

When dictating in multiple languages, the punctuation filters understand both. An English period and a Spanish punto are identical marks; the text filters handle them the same way regardless of which language command you use. However, some typographic conventions are language-specific. If you are writing Spanish and need an inverted question mark at the beginning of a sentence, add that to your dictionary: spanish question start → ¿. This ensures your punctuation matches the target language's conventions.

Punctuation speed and accuracy

Spoken punctuation commands are recognized with high accuracy — they are short, distinctive words that the engine has been trained to identify. The rare failures are:

• You accidentally say "period" when you meant the word "period" (use dictionary entries to avoid this)
• Unclear speech: saying punctuation marks while you are tired or in a noisy environment

If you are concerned about accuracy, check the history after your dictation session. Every punctuation command appears as itself in the raw transcript before filtering: if the raw transcript says "period", the filter converted it correctly to .. If the raw transcript does not show "period", the engine misheard you.

The role of punctuation in readability

Punctuation shapes how readers understand your writing. A sentence without periods runs together and becomes hard to follow. Commas signal pauses and grouping. Semicolons connect related ideas. When you dictate, adding punctuation as you speak — rather than dictating a wall of words and punctuating later — produces clearer text immediately.

This is different from the old transcription workflow, where you dictated everything and then edited. Modern dictation works better when you punctuate live, because it forces you to think about sentence structure as you speak. Your words are fewer, your ideas are clearer, and your first draft is closer to final.

Some writers find that real-time punctuation improves their thinking. Saying "period" is a deliberate checkpoint: "Did I finish this thought? Am I ready to start a new one?" This makes your dictation more intentional and produces better prose.

Building a punctuation habit

Dictating with spoken punctuation takes practice. The first few dictations feel awkward: stopping to say "comma" interrupts your flow. But within a session or two, it becomes automatic. You stop thinking about the mechanics and focus on what you are trying to say.

Tips for building the habit:

• Start with simple sentences: Dictate a few simple statements with period punctuation, then add commas. Do not try to dictate a complex paragraph with embedded clauses and multiple punctuation marks on your first attempt.
• Punctuate as you speak: Do not dictate a whole paragraph without punctuation and then try to add it all at once. Speak naturally, adding punctuation commands as you would if you were speaking to a human transcriber.
• Adjust your dictionary: If a default punctuation command conflicts with something you say frequently, change it immediately. You will spend a lot of time dictating; making the commands match how you actually speak saves frustration.
• Write differently than you think: The words you dictate are usually fewer than the thoughts you are trying to express. You might think in long sentences, but when you dictate, you say shorter bursts. This makes punctuation simpler and the output clearer.
• Practice with familiar documents: Start with documents where you know the shape — emails, blog posts, notes. These are forgiving. As you build confidence, move to more structured writing.

Advanced punctuation patterns

Some complex punctuation patterns worth learning as you build your skills:

Nested quotations: If you need a quotation within a quotation, use distinct commands:

• open quote dialogue start → "
• dialogue end close quote → "
• Build entries for nested levels if you use them frequently

Abbreviations with periods: U.S.A., Ph.D., Mr., Mrs. These are often recognized by the engine without you speaking periods. If they are not, add dictionary entries for the ones you use most.

Ellipses and dashes: An ellipsis (...) is three periods in sequence. An em dash (—) is a long dash. Instead of saying the marks three or once, add dictionary entries:

• ellipsis → ...
• emdash → —

This is much faster than speaking each component.

Parenthetical remarks: You might need both regular parentheses and parenthetical remarks in brackets for footnotes or asides. Build separate entries:

• note start → [
• note end → ]
• paren start → (
• paren end → )

This way you can use the shorter form when you are in flow and let the dictionary handle the conversion.

Punctuation and formatting

Spoken punctuation handles marks, not formatting. A period makes the next letter capital and adds spacing, but it does not make the text bold or italic. Those formatting marks (if your app supports them) would be:

• Handled by separate dictionary entries (bold start → **)
• Or applied afterward in your editor

This is intentional: the point of dictation is to get your words captured, not to spend the session issuing formatting commands. The fastest workflow is to dictate the content, then format in the app where you are writing.

Punctuation in different writing genres

Different types of writing have different punctuation needs. Understanding these helps you build a dictionary that matches your workflow:

Academic writing: Extensive use of citations, footnotes, and parenthetical references. You might use square brackets for citations ([1]) and parentheses for asides. Build entries for your citation format.

Technical documentation: Often uses lists, code blocks, and structured formatting. You might need commands for starting and ending code examples, or for list items with specific formatting.

Fiction and narrative: Dialogue, italics for emphasis, and varied punctuation. Build entries for dialogue markers and scene breaks if you dictate fiction.

Email and messaging: Short sentences, fewer complex punctuation marks. This is often the easiest domain to dictate in because punctuation is minimal.

The same principle applies to all of them: build your dictionary to match the punctuation and formatting conventions of the genre you write in most. Start there, then expand to other genres as your dictation skills grow.

Punctuation while dictating is optional. Some people punctuate as they go, building it into their rhythm. Others dictate a paragraph and add punctuation from a second pass. Experiment to find what fits your speed and accuracy.

Spoken punctuation is one feature that makes dictation feel natural. To start dictating with punctuation, download Coii VoiceInput and try it with a simple document. Test out the default punctuation commands and build a dictionary that feels right for you.