• 1 Post
  • 9 Comments
Joined 1 day ago
cake
Cake day: April 27th, 2026

help-circle
  • 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.




  • 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?