Virtaal 1.0.0¶
Virtaal is back. After being dormant since 2020, it’s been rebuilt from the ground up on Python 3 and GTK 3, and is once again a maintained, actively-developed translation tool.
Getting it¶
Windows installer, macOS .dmg (Intel and Apple Silicon, macOS 15
Sequoia or later), and a Linux Flatpak (x86_64 and aarch64) - see
Installation.
Each release also has a Linux AppImage (x86_64 and aarch64), as a beta: it isn’t a supported way to install Virtaal yet. It runs from wherever you save it, adds itself to your applications menu, and checks spelling with the dictionaries installed on your system.
Note
The macOS builds are signed and notarized by Apple, and the Windows installer is signed by Translate House Ltd. Windows may still show a blue “Windows protected your PC” screen for a while, until SmartScreen recognises the new certificate: click More info, then Run anyway.
What we set out to do¶
A handful of things drove this release, in order of priority:
Don’t break the translating experience translators already know. Virtaal’s appeal has always been that it gets out of the way and lets you translate - a rewrite of its internals was never licence to also rewrite its workflow.
Port to a modern windowing system before the old one disappears from under us entirely, and use that as the moment to bring the rest of the engine (Python itself included) up to date too.
First-class builds on every platform - Windows, macOS and Linux should each get a real, native-feeling installer, not one platform treated as primary and the others as an afterthought.
Seamless download of resources when you need them - dictionaries, autocorrect rules and similar data shouldn’t have to be bundled upfront or hunted down by hand; Virtaal should fetch what a given language needs, on demand, and stay out of your way while doing it.
Make it feel like it belongs on your computer, not like a cross-platform app that merely runs there.
Make it something you can trust with your work - it shouldn’t lose translations, corrupt files, or leave you guessing why it froze.
How we met them¶
Same Virtaal, modern engine¶
The move from Python 2/GTK 2 to Python 3/GTK 3 touched almost every file in the codebase, but day-to-day translating - opening a file, moving between units, matching against translation memory, running quality checks, spell-checking - works the same way it always has. If you used Virtaal before 2020, you don’t need to relearn anything; the windowing system underneath changed, the tool you sit down to use didn’t.
First-class on every platform¶
All three platforms now get a real, proper build: a Windows installer
with correct file associations and icons, native macOS .app/.dmg
builds for both Apple Silicon and Intel, and a Flatpak for Linux - all
built, tested and shipped from the same CI pipeline rather than one
platform being the “real” build and the others best-effort ports.
Resources arrive when you need them¶
Dictionaries, autocorrect rules and similar per-language data are fetched automatically the first time you need them for a given language, rather than needing to be bundled for every language upfront or tracked down and installed by hand. Once fetched, they’re cached, so you only pay that download cost once per language.
Feels native on your platform¶
Rather than a single cross-platform look, Virtaal now leans into each OS’s own conventions: real native Open/Save dialogs instead of GTK’s own file picker, macOS keyboard shortcuts (Cmd instead of Ctrl) throughout, a title bar that follows each platform’s own naming and “unsaved changes” conventions, a populated macOS Dock menu with recent files, light/dark theme switching that follows your system live instead of only at startup, and file-manager integration (icons, double-click to open, “Open With”) for every format Virtaal handles on Windows and Linux alike. Numbers, counts and percentages throughout the interface now follow your UI language’s own conventions too, instead of always being shown the English way.
Built to be trusted¶
A sustained focus on correctness and crash-hardening runs through this release: fixes for several ways Virtaal could previously crash outright (corrupt settings files, certain file formats, specific edit sequences), a more careful undo/redo model so navigating around no longer muddies what “undo” actually undoes, read-only files are now handled safely instead of inviting a crash on save, and network requests (translation memory, terminology, dictionary downloads) now fail cleanly with a timeout instead of hanging Virtaal indefinitely. There’s also a built-in crash dialog with a one-click bug report button for whatever we haven’t caught yet.
Easier to use in your own language¶
Virtaal’s own interface can now be switched independently of your system language, from Preferences or via a command-line flag - and a long-standing bug that silently broke interface translations in the installed build entirely is fixed. The Windows installer also now offers substantially more UI languages to choose from during setup. Behind the scenes, a new priority system focuses translators and reviewers on what actually matters most - what you see as a file opens, menus, everyday messages - ahead of rarely-seen text, and you can follow any language’s own progress live at virtaal.translatehouse.org/translate.html.
Known limitations¶
Nothing release-blocking, but worth knowing about:
No spell checking in the Apple Silicon macOS build (the Intel build has it) - the underlying spell-check library has no ready-made build for that platform yet.
Full changelog¶
This page deliberately leaves out the hundreds of smaller fixes, internal refactors, and test/CI improvements that went into getting here. For the complete, unabridged list, see the commit history and releases on GitHub.