Winter-service software in Klingon

Wintertrace now speaks Klingon. No one asked for this. I built it anyway.

Before I explain myself, the sober part — because there is one. This release is really three language packs, and two of them are completely ordinary.

The boring news first

Wintertrace now ships with a French language pack and a Czech language pack. Both are complete translations of the whole interface — every screen and the in-app help, not a thin layer of menu labels over an English core. French uses formal address throughout, Czech uses vykání, and both keep winter-service terminology consistent from one screen to the next, so the wording reads the way the people using it actually talk to their customers.

This is the unglamorous work that good software quietly does. A crew in Lyon or Brno should be able to run the same documentation tool a crew in Manchester runs, in their own language, without anyone shrugging and saying “the menus are in English, you’ll get used to it.” Each pack installs as an ordinary module with zero changes to the core, and you can switch it on per user or set it as the default for the whole installation. Nothing changes language on its own.

That is the part I would put on a quote. Now the part I would not.

Then the part nobody asked for

There is also a Klingon language pack.

The entire Wintertrace interface — tlhIngan Hol, the language Marc Okrand built for Star Trek III back in 1984, with the dictionary following a year later. Every screen. The help pages. The buttons. Delete is Qaw', which means “destroy”, because Klingon does not really do polite. Success is Qapla'. A PDF export is nav De' — “paper-data”.

Does any winter-service company on Earth need its documentation software in Klingon? No. Not one. I want to be completely honest about that, because the rest of this site is careful not to overpromise, and I am not about to start now with a constructed language from a 1980s science-fiction film.

But here is the thing about open source, and about building software the way I build this one. Most products live on a single track. There is a roadmap, there is a budget, and a feature only ships if someone can draw a straight line from it to revenue. A Klingon translation never survives that meeting. It is the first thing cut and the last thing proposed.

Wintertrace does not have that meeting. It is free, open-source software, and a chunk of it gets built the way you actually want to build things — by following a thread because it is interesting, and because the tooling makes it cheap to try. A language pack is, structurally, just another set of strings. Once the French and Czech packs proved the pattern, “what else could we translate into” stopped being a budget question and became an afternoon. So one of the answers was Klingon.

How you translate “snow” into a language with no snow

This is the genuinely interesting bit, and it is where the pack stops being a gag and starts being a small piece of craft.

Klingon has only a few thousand canonical words, and exactly none of them are about winter service. There is no native word for snow, for grit, for GPS, for a service report. So you cannot simply look words up. You have to decide what to do when the word does not exist — and “borrow the English word” is the lazy answer that every joke translation reaches for.

This pack does the harder thing, which also happens to be the correct thing. Klingon, by tradition, coins new words as descriptive compounds rather than loanwords — the word for “planetarium”, for instance, is built to mean roughly “space-showing building”. So the pack follows the same instinct. Where a real Okrand word exists, it is used. Where one does not, the translation builds a compound that explains what the thing does:

• Snow is Doch bIr — “cold substance”.
• Grit is Doch chIS — “white substance”.
• GPS is Daq ‘angwI’ — “place-shower”.
• A PDF is nav De’ — “paper-data”.

It is described, not borrowed. There is a field glossary on the module page if you want more of them. And the whole thing uses the standard Latin romanisation rather than the pIqaD script, for a deeply unromantic reason: it renders correctly everywhere, with no special font and no change to the core. Capitalisation carries meaning in Klingon, so the capitals and the apostrophes are preserved exactly — Q is not q, and getting that wrong changes the word.

Is there a market for Klingon software?

Short answer: no. Longer answer: that was never the right question, and the people who have done this before me knew it.

Let me give you the honest numbers, with the caveat that they are estimates and not a census. The linguist Arika Okrent has put the number of people who can hold an unscripted conversation in Klingon at maybe twenty or thirty. Twenty or thirty, on the entire planet. And yet, when Duolingo launched its Klingon course in March 2018, hundreds of thousands of people signed up; the course still lists around 291,000 learners today. The gap between “people who speak it” and “people who love that it exists” is enormous — and that gap is the entire point.

Because the interesting fact is that serious companies keep building this. Microsoft added Klingon to Bing Translator in May 2013 — in both the Latin script and the native pIqaD — and described it, in their own words, as “a labor of love”, built with the Klingon Language Institute and Okrand himself. Minecraft ships Klingon as one of its constructed languages. Debian carries a Klingon locale that is gloriously, honestly incomplete — somewhere around 120 strings translated out of more than a million. Telegram, listing examples of community language packs anyone can build, name-checks “Transliterated Klingon” right alongside Māori and Scottish Gaelic.

And it is not only Klingon. Esperanto has genuine, maintained localisation in KDE, Mozilla and Debian. Facebook shipped “English (Pirate)” on Talk Like a Pirate Day in 2008. WordPress added a Pirate locale of its own. This is a real open-source tradition, not a one-off. It exists because open localisation platforms treat a language as just another set of keys, so the marginal cost of adding one is close to nothing and volunteer enthusiasm does the rest.

There is even a patron saint for the useless-but-joyful feature: HTTP status code 418, “I’m a teapot”, a 1998 April Fools’ joke baked into the web. When people tried to remove it in 2017, the community launched a “Save 418” campaign and got it formally reserved in the official HTTP specification. Joy, it turns out, is worth defending.

So: not a market. A culture. The value of a Klingon pack is not licence revenue — there is no licence and there is no revenue. The value is that it tells you something true about the software. Software that bothers to do this is software built by people who enjoy building it, on a model that lets them. That is worth more than a slogan.

A quick note for the lawyers in the room, since this is the internet: there is a well-known story that a Star Trek studio once claimed copyright over the Klingon language itself, during the 2016 Axanar fan-film case, and that the Language Creation Society fired back with a legal brief partly written in Klingon. That much is true. The part people get wrong is the ending: no court ever ruled on whether the language is copyrightable. The case settled, the studio quietly dropped the claim, and the question was left undecided. Translating your own software’s interface into Klingon was never the legally interesting part anyway — that work is your own.

The one reader I’m actually writing this for

Somewhere out there is exactly one person I have in mind.

They do winter service for a living. They are out at four in the morning with a plough and a bag of grit. And — for reasons entirely their own — they speak Klingon, or they are 290,000-and-first on that Duolingo course. Statistically this person barely exists. But the internet is large, and I am fairly confident they are real, and I would like them to find this page.

Here is what I want to happen. They install the Klingon pack — one click, and the whole interface they stare at every shift is suddenly in tlhIngan Hol. They are delighted. They show their boss.

And the boss, who does not care about Star Trek even slightly, looks a little closer at the thing on the screen — and discovers that underneath the Klingon is free, open-source software for documenting winter-service operations. GPS tracks, weather data, photos, a service-proof PDF. The boring, important stuff. Quite possibly the exact thing the company already pays a subscription for somewhere else.

The employee gets a winter-service tool in Klingon and will not stop grinning about it. The boss gets documentation software that runs on the company’s own hosting, with no subscription and no cloud lock-in. Everyone wins, for completely different reasons. That is the whole plan, and yes, I know how it sounds.

Do you need this?

ghobe'. No. You do not need your winter-service software in Klingon.

Is it cool? HISlaH. Yes.

Both of those can be true, and the fact that they are is, I think, the most honest advert this software has. If you want the useful packs, French and Czech are right here. If you want the ridiculous one, it is right next to them. And if you speak Klingon and run a winter-service crew, I genuinely want to hear from you — the feedback form is this way.

Qapla’.