Thanks for the offers to help with translations. Wanted to share the plan.

I’m wiring up the translation infrastructure now: svelte-i18n with one JSON file per locale in the repo. The workflow once it’s ready is straightforward. There’ll be a single English source file at src/i18n/en.json, contributors copy it to their locale (fr.json, nl.json, de.json, etc.), translate the values, and open a pull request. Keys stay untouched, only values change.

Nothing to do right now. I’ll open a GitHub tracking issue once the source file is stable enough to translate against. A short contributor guide will land with it covering workflow and conventions.

One thing worth flagging early: for nutrition labels specifically, please plan to use the regulatory terms that appear on food packaging in your country rather than the literal English equivalents. So Glucides / Lipides / Protéines for French, Koolhydraten / Vetten / Eiwitten for Dutch, Eiweiß rather than Protein for German, and so on.

More soon.

Quick update on this. Translation infrastructure is live as of v1.0.0-rc.6 (released today). The source file is src/i18n/en.json — about 210 keys covering navigation, page titles, the full auth flow, the onboarding wizard, primary actions in Diary / Foods / Goals / Profile, the AI assistant FAB, and common toasts. Server-side strings (email subjects, push notification bodies) are out of scope for now.

Full workflow is documented in CONTRIBUTING.md → Translations.

About 30% of the client-side surface is extracted in this batch — the screens every user touches every session. Wellness sync messages, deep Settings sub-section labels, and Statistics chart internals are the main gaps. If you hit a screen you use heavily that’s still English while translating, open an issue listing the screen and I’ll pull it forward in the next extraction batch.

Tag me on the PR when you’re ready.

Thanks for the offers to help with translations. Wanted to share the plan.

I’m wiring up the translation infrastructure now: svelte-i18n with one JSON file per locale in the repo. The workflow once it’s ready is straightforward. There’ll be a single English source file at src/i18n/en.json, contributors copy it to their locale (fr.json, nl.json, de.json, etc.), translate the values, and open a pull request. Keys stay untouched, only values change.

Nothing to do right now. I’ll open a GitHub tracking issue once the source file is stable enough to translate against. A short contributor guide will land with it covering workflow and conventions.

One thing worth flagging early: for nutrition labels specifically, please plan to use the regulatory terms that appear on food packaging in your country rather than the literal English equivalents. So Glucides / Lipides / Protéines for French, Koolhydraten / Vetten / Eiwitten for Dutch, Eiweiß rather than Protein for German, and so on.

More soon.

Yes, vibe coded and proud of it. This is a labor of love that I genuinely don’t think I could have completed without Claude Code. The first commit is large because I was working out of a private dev repo and synced everything to the public repo just before the 1.0 RC release. Hope you give it a chance and that it suits your needs. Thanks!

PR tested and merged! Thank you!

Is there a place where we could help with translation ?

I know a few people that would want an app like that but English is not their primary language and won’t bother checking it out at all without some kind of translation.

Great question, and not yet. NutriTrace is English-only right now, and the UI strings are hardcoded throughout the Svelte components. To accept translations I’d first need to wire up an i18n layer (svelte-i18n is the obvious pick) and extract strings to per-locale JSON files. Then translation contributions become straightforward via PRs or something like Weblate/Crowdin. I will add this to my roadmap. Any languages in particular we should prioritize?

Mealie integration allows you to pull in your Meal/Recipe from your self hosted instance of Mealie via api. If you have nutrition facts set there by the recipes total weight, it will pull in that data and then you can set your serving size accordingly so it calculates properly. It also pulls in the recipe pic if set in Mealie.

Barcodes work internationally. i can confirm because i have used in both europe (italy) and africa (south africa). Only difference between nutrition facts i see is that the US uses Sodium and i want to say that at least Europe uses Salt. I have a built in conversion where when one is used the other is automatically calculated.

Yes indeed! On my future to do!

Is the docker image public? I’m getting an “unauthorized” error when attempting to pull it. I’m not getting that error for other ghcr.io images. But I’m not docker expert, so I may be doing something wrong.

Should be fixed now, package was set to private by default on first push. Just flipped it. docker pull ghcr.io/traceapps/nutritrace:latest works without auth now. Thanks for flagging it.

Thanks all, really appreciate the kind words. Feedback is welcome on anything: bug reports, missing features, things that feel rough, or just “this works for my setup.” A few features are flagged Experimental right now and I’d like to harden them enough to drop the badge.

Native Android app is in active development. There’s also a sister project in the works called LiftTrace under the same TraceApps umbrella, same self-hosted Docker setup but for workout tracking (sets, reps, programs, PRs). Not public yet but close.