Viewing profile — maxpr

1. I do speak more than one language. I agree with your point that perfect localization requires seeing a element in the broader context of the parent component, parent page, the p…

Historically, there are a couple of reasons why developers prefer to i18n their app instead of letting users do that. 1. PostHog has a great tool that lets developers "watch the vi…

Thanks! =) > localization is far from just translating the text For sure, that's spot on. What I'm excited about the most is that linguistic/cultural aspects are close to being sol…

Good point. There are JavaScript tools that do that for js devs, but since oftentimes you end up having links and nested elements in the code, wrapping becomes problematic and hard…

Yep, Cursor indeed helps! (Here's a battle tested prompt example we found working pretty nicely with claude o3 + claude 3.7: https://lingo.dev/cli/extract-keys ) > Then, you simply…

I think modern Japanese is LTR, but besides that - I believe the project you worked in the past solves an important problem. Besides pluralization (and e.g. Arabic having 6 forms z…

Perhaps I could've communicated this better, but we've built Lingo.dev Compiler for web apps and user interfaces, not for technical/professional content. And since we had to exclud…

we've added support for both these cases actually! :) 1. `data-lingo-skip` - excludes a jsx node from i18n 2. `data-lingo-override- ` - overrides version in language with a custom …

Exactly, this is a great direction! We believe automatic discovery + i18n processing is the most natural next step for i18n on the web, since LLMs now exist. And we feel that not o…

I believe tRPC could be a great solution to separate logic, generally speaking. However it also depends on what type of logic - some logic, like state/behaviour of the sidebar/moda…

With the community support we hope to support more platforms soon vs now, but I can confidently say that adding support for techs stacks using one of the following: Vite Rollup web…

Genuinely excited to read comments like yours. We started the project scratching our own itch, and are touched it resonated! It will remain 100% free and open-source. We're already…

Thanks for the perspective! We support larger org workflows with the Lingo.dev Engine product, but that's not the point: Lingo.dev Compiler is unrelated to that, 100% free and open…

woah, i like this domain name! I bet it cost you a fortune :)

Sure Jjani, perhaps our docs could be slightly better! :) Typically quality changes significantly with the right setup of translation fine-tuning settings, so send me a DM with you…

Hey lukol, that's an exciting problem to solve. The best solution right now is prompt engineering: turns out, AI can be tuned to provide top quality results with the correct system…

Interesting perspective. Unsure if I communicated it well, but unlike auto-translators such as Google Translate, this project leverages a context-aware LLM to recreate the meaning …

> half-assed translation that was obviously made by a machine That's exactly what we want to solve. Here's the thing: It turned out, AI translates better than humans when provided …

Yep, localization is the best term here, but sometimes folks confuse it with other things, for example geo localization or localization of errors. So we usually try to use both ter…

Thanks! To make it work predictably, we actually tested quite a few different algorithms before landing on one that produces outputs LLMs can reliably understand. Conceptually, we'…

Hi HN! We've just released an open-source React bundler plugin that makes apps multilingual—at build time, without modifying the code. React app localization typically requires imp…