VMark speaks your language
VMark now ships in 10 languages out of the box — and on a fresh install, it picks the right one for you automatically. No setup, no menu-diving on first launch: open VMark on a Japanese Mac and it greets you in 日本語; open it on a French desktop and it speaks Français.
Localization is not a single language pack you download. Every build is one multilingual binary — every locale is always present. What changed in this release is that the app now chooses the right locale on its own, and the parts that used to leak English no longer do.
Ten languages, one binary
| Language | Code |
|---|---|
| English | en |
| 简体中文 (Simplified Chinese) | zh-CN |
| 繁體中文 (Traditional Chinese) | zh-TW |
| 日本語 (Japanese) | ja |
| 한국어 (Korean) | ko |
| Deutsch (German) | de |
| Español (Spanish) | es |
| Français (French) | fr |
| Italiano (Italian) | it |
| Português do Brasil (Brazilian Portuguese) | pt-BR |
The interface, the menus, the guide pages on this site, and — new in this release — the error messages are all translated across every one of these.
Auto-detects your OS language on first launch
On a brand-new install, VMark reads your operating system's language preferences and matches them to the closest supported locale, using a sensible fallback chain:
- Simplified-Chinese variants (
zh-CN,zh-SG,zh-Hans-*) → 简体中文 - Traditional-Chinese variants (
zh-TW,zh-HK,zh-MO,zh-Hant-*) → 繁體中文 - Any Portuguese (
pt-BR,pt-PT,pt) → Português do Brasil - A base-language match for
ja,ko,de,es,fr,it - Anything we don't ship → English
This only happens on first launch. If you have used VMark before, your saved language choice is untouched — upgrading never overrides what you already picked.
Change it any time
Auto-detection is just the starting point. To switch languages at any moment, open Settings → General → Language and choose from the list. The change applies live — no restart required.
Errors speak your language too
Previously, the interface was translated but failure paths still surfaced raw English. A failed Pandoc export, a hot-exit storage problem, or a workflow-validation error would break the spell of a fully localized app.
That gap is closed. The Rust backend now routes user-facing error messages through the same translation system as the UI. Trigger an export failure in a Japanese session and the toast reads in Japanese — placeholders like file names and exit codes preserved, the surrounding sentence translated.
Developer-only diagnostics — log files, debug output, internal plumbing — stay in English on purpose. Those are for us, not for you, and keeping them in one language makes support and bug reports easier to reason about.
Help us get it right
Machine-assisted translation gets us most of the way, and a human polish pass smooths the rest — but native speakers always catch what we miss. If a string reads awkwardly, a date or number looks wrong for your locale, or you spot any English leaking into a non-English session, open an issue and tell us. We would rather hear about one clumsy sentence than ship a hundred.
Try it
Download VMark, launch it, and watch it meet you in your own language. If it doesn't — that's a bug, and we want to know.