Voice to Text for Regional Variants
Wrong spelling looks like wrong translation. Pick the variant once—Voiskey keeps colour, Strasse, and 简体 consistent. Free to start.

Readers forgive a slightly awkward sentence. They do not forgive colour spelled color in a UK contract email, or 繁體 slipping into a Mainland launch note.
Translation quality is more than glossary swaps. Orthography tells the reader you are writing for their market on purpose.
Dictation that ignores variants forces a second cleanup pass—the same tax you were trying to remove by speaking.
Set the regional variant once. Across 100+ languages, that small choice is what makes voice output feel localized instead of generically translated.
English – British keeps UK spelling such as colour and centre. English – Canadian covers Canadian norms on desktop. American English stays the default for many US workflows.
German – Swiss replaces ß with ss. Standard German keeps ß. Saying the same street name produces different trustworthy text depending on the variant.
Chinese – Simplified and Chinese – Traditional are separate. Cantonese is its own option, not a switch inside Mandarin Chinese.
Hinglish sits apart from Hindi when you want romanized bilingual speech rather than Devanagari output. Naming the blend correctly is a translation decision.
Mutually exclusive pairs to remember:

Formal writing where a single Americanism undercuts an otherwise careful translation.

Board notes that should match the market spelling your investors already use.

Audience-facing prose where localization is visible in every paragraph.

First-pass docs in the script your region ships, before deeper localization.

Shared agendas that should not mix regional conventions inside one company.

Quotes and terms kept in the orthography of the source language.
More languages in the shortlist is fine. More conflicting variants for the same language is not.
If translation output keeps oscillating between scripts or spellings, check whether two cousins are both enabled.
Onboarding can pre-fill from system region—Switzerland toward Swiss German, UK toward British English, China or Singapore toward Simplified Chinese. Confirm it matches the audience you write for, not only where your laptop thinks you live.
With 100+ languages available, discipline is selecting less: the markets you serve this quarter, each with one spelling contract.
Some languages bring punctuation rules with them. French narrow spaces before certain marks are a localization feature, not noise to strip out.
Times, ratios, and URLs are handled so you do not get odd gaps in 12:30 or https links. Code editors can skip the rule entirely.
That attention is the same idea as regional spelling: written translation quality includes how the page looks, not only which lemma was chosen.
Dictate for the reader’s conventions. Let Voiskey carry the orthography; you carry the meaning.
Workflows when orthography matters:
Voiskey supports 100+ languages including regional options such as British English, Canadian English, Swiss German, Simplified Chinese, Traditional Chinese, and Cantonese as its own language choice. Exact availability follows your app settings list.
Treat them as mutually exclusive for clean output. Selecting one regional English variant typically deselects the others so spelling stays consistent inside a session.
No. Swiss orthography changes writing—ß becomes ss, so Strasse not Straße. That is localization inside dictation, not just pronunciation handling.
They are separate language options. Pick the script your reader uses. Mixing them in settings is a common source of “almost right” translation that still feels off.
French typographic spacing is intentional—narrow spaces before ; : ? ! and guillemets. It is standard French writing, not a bug in the translation layer.

Speak naturally, write effortlessly, and move faster. Turn your voice into polished, ready-to-use text wherever you work.
Use it across macOS, Windows, iOS, and Android