6/3/2026 at 4:24:46 PM
by llovan
6/3/2026 at 6:04:29 PM
Is there a way to set the default unit? I'd prefer to see the information per 100g by default (instead using random units).by laurentlb
6/3/2026 at 6:18:37 PM
thanks for the feedback. That's a good suggestion. I will be adding some tweaks soon for improved unit handling. Also another idea I had that I want to implement is being able to compare several foods side by side in a split view (on desktop or tablet landscape modes).by llovan
6/3/2026 at 5:14:07 PM
I can't enter a serving size that's not a whole number on mobile because it automatically closes the keyboard when the text field is clearedby cd4plus
6/3/2026 at 5:25:00 PM
Thanks for catching that. Will fix soon.by llovan
6/3/2026 at 5:52:44 PM
Very nice, what is the source of the data?by olarm
6/3/2026 at 6:01:02 PM
The only source currently for all data is the USDA's Food Data Central. I'm planning on adding more nutrient data sources in the near future.by llovan
6/3/2026 at 6:32:42 PM
The search seems a bit weird. A search for salmon includes almonds in the results, and a search for spinach includes Tahitian taro.by Finnucane
6/3/2026 at 6:36:52 PM
Thanks for the feedback. Currently in addition to fuzzy matching the search system will match against synonyms broadly, so some unintended leafy greens would match Spinach as in your example results. I'll have to tweak the fuzzy matching a bit.by llovan
6/3/2026 at 5:17:08 PM
Nice great job, how do you handle multi languages?by razorson
6/3/2026 at 5:52:07 PM
Thank you! Each locale has its own route terms, UI strings, portion terms, localized food names, synonyms, slugs, and search behavior.The app uses ICU MessageFormat for pluralization/units and locale-aware number/unit formatting. Search varies by script: Latin languages use pg_trgm/unaccent, CJK and other non-Latin scripts use PGroonga, and romanized aliases are indexed separately so Latin-keyboard queries can still find native-script foods.
For localization I do use multiple LLM passes, but mostly as a structured localization pipeline rather than a one-shot translator: generate localized names/aliases/slugs/content from canonical food and nutrient data, then run separate review/evaluation passes and human spot checks.
The hard part is regional naming and portions, not basic translation. For example, in Spanish, "Potato" as papa vs patata is the simple version of the problem.
by llovan
6/3/2026 at 5:01:55 PM
awesome, very good looking and simple, useful functionalityby recursivedoubts
6/3/2026 at 5:49:35 PM
cool! i see at least two reasons in the title to upvote thisby setnone
6/3/2026 at 5:54:52 PM
lol, ty, Clojure + HTMX have been an amazing combo for this project. and postgres too, for the DB.by llovan
6/3/2026 at 5:00:09 PM
Simple and beautiful, I love it.by Kuyawa
6/3/2026 at 5:29:39 PM
Hi HN, I'm Jovan. I've been building Nutrepedia part-time from Monterrey, Mexico.It's a multilingual nutrition reference site: 1,635 foods rendered into 47,415 localized pages across 29 regional locales. Each page has nutrition facts, localized names, portion terms, regional routing, imagery, and short food context.
The stack is Clojure, HTTP-Kit, Compojure, Hiccup, HTMX, and Postgres. Postgres handles the food data, localized content, admin workflow, task queues, search, and evaluation records.
The search piece has been the most interesting technically. Latin-script fuzzy search uses pg_trgm and unaccent. CJK and other non-Latin scripts use PGroonga. Romanized aliases are indexed separately, so a query like "rasbhari" can find a Hindi food name like "rasbhari" / "रसभरी".
I built this because most nutrition tools feel calorie-first, signup-first, and English focused. I wanted the reference layer to be free and useful before asking anyone to track meals or create an account.
I'd especially appreciate feedback on search, localization mistakes, whether the pages are useful before tracking exists, and any obvious technical blind spots.
by llovan
6/3/2026 at 6:23:55 PM
cool projects. bear in mind some languages like Spanish are spoken across different countries. German for example is spoken in Germany, Austria and Switzerland. Using the Germany flag is misleading.by snowpid
6/3/2026 at 6:33:43 PM
[flagged]by llovan