Other language available

Thanks, really glad you like it!

Quick honest answer: we've got Swedish and English today. French is absolutely something we want to add, but the annoying part is that nobody on our team actually speaks French, so we can't just sit down and do a proper translation ourselves.

What we're leaning towards is generating a first version with AI, and then building in some way for users to report bad/weird translations and suggest corrections. That way native speakers can help clean it up instead of us shipping robot-French that reads terribly. The AI part is the easy bit, getting it to actually sound right is what takes some thinking.

No fixed timeline yet, but it's on the list and I'll post here when there's something to test. Thanks a lot for trying it out!

Follow-up, and this time with something to actually try.

Since that post we've moved translations onto Weblate, a browser-based

translation tool — no Git, no build setup, you get each English string with its

context and type the French next to it:

👉 https://hosted.weblate.org/projects/cellarion/

And I'm changing how languages get released, because the old rule was unfair to

the person doing the work. Landing in the next release:

- Every language that anyone has started shows up in Settings straight away —

no waiting for it to be "finished". Below 90% it's labelled, e.g.

"Français (beta · 62%)", so you know what you're getting: the translated parts

in French, the rest still in English.

- Beta languages are opt-in only. Nobody gets dropped into a half-translated UI

just because their browser is set to French — you have to pick it yourself.

- Completeness is now measured over the screens users actually see. The admin

back-office is ~14% of all text, and counting it meant a French translator had

to translate a bunch of admin panels they'll never open before their language

could ship. That's out of the calculation now: finish what users see, and

you're at 100%.

Practically, that means you can start French today, switch the app to it while

you work, and see your own strings in place — which is where you catch the

things that look fine in a translation list and wrong in the actual app.

There's a glossary in Weblate for the wine terms (drink window, maturity, rack,

vintage, appellation) — worth a look first, it's where machine translations

usually go astray. Tone we aim for: informal, direct, tutoiement. Cellarion is a

hobbyist's tool, not enterprise software. The rest is here:

https://github.com/jagduvi1/Cellarion/blob/main/TRANSLATING.md

Thanks again for asking — this is the nudge that got the rule changed. 🍷

The preview function will soon be shipped to live...