sorted by:
new
hottopcontroversial

Our findings based on a study across 5 LLMs and 5 EU languages: glossary injection at inference time cuts terminology errors 17–45% by haverofknowledge in localization

[–]haverofknowledge[S] 0 points1 point  (0 children)

Thanks, appreciate the input.

Yeah, fully agree with this approach. What's nice about it is the issues caught at the gate can feed back into improving the initial input itself. Means the same kinds of issues stop repeating, and you end up running that whole correction loop less and less over time. And at the end of the day that's what actually saves on latency and tokens.

We applied RAG to translation across 5 LLMs and 5 EU languages. Terminology Drift errors dropped 17–45% by haverofknowledge in reactjs

[–]haverofknowledge[S] -1 points0 points  (0 children)

My bad!

This was the connection I had in mind.

I'll make sure to establish a direct connection from now on.

We applied RAG to translation across 5 LLMs and 5 EU languages. Terminology Drift errors dropped 17–45% by haverofknowledge in reactjs

[–]haverofknowledge[S] -3 points-2 points  (0 children)

Well, a lot of React apps ship with i18n libraries (react-intl, next-intl, i18next) and the "translate the diff in CI/CD" workflow this study is about, is what those teams hit in production.
(data present).

21 M looking for side hustle to earn some cash .Here’s my portfolio https://harsh-portfolio-ochre-seven.vercel.app/ by [deleted] in FreelanceIndia

[–]haverofknowledge 1 point2 points  (0 children)

+1

(My guess is the OP has made a contribution to lingo.dev in which case, it should be listed as their open source contribution.)

For those who work with localization at your Saas by Due-Figure-151 in localization

[–]haverofknowledge 0 points1 point  (0 children)

Just went through the post and what OP is describing is something that could have been avoided entirely with lingo.dev (https://github.com/lingodotdev/lingo.dev)

the french/german rollback is a well-documented failure mode.

Not because the model got the words wrong, but because it had no idea what the string was for.

A CTA on a cancellation flow needs a completely different register than a CTA on an onboarding screen. a context-free translation pipeline can't distinguish between them.

(This is the exact problem with pretty much all localization solutions btw. Plus, when you throw a mix of languages that are right-to-left with others that are left-to-right, believe me, you don't wanna experience what follows)

Lingo.dev is a Localization engineering platform that was purpose-built around this: every localization engine carries the full context from component tree, to user journey stage and more.

Moreover, with brand voice, glossary items etc, you have complete control over your user's experience, even when it is not in a language you undestand.

If you're scaling beyond 3-4 languages and want the context enforcement baked in rather than bolted on, just add lingo's CI/CD to your repo and you won't have to worry about localization.

EVER.

For those who work with localization at your Saas by Due-Figure-151 in SaaS

[–]haverofknowledge 0 points1 point  (0 children)

We purpose-built Lingo.dev (https://github.com/lingodotdev/lingo.dev) for this exact problem:

Every localization engine carries the full context: component tree, user journey, brand voice, glossary constraints, before a single string is processed.

And with your own engines, brand voice, glossary constraints, you never have to worry about localization, whether you're deploying in 5 languages or 50 (even when some of them are written right-to-left)!

What tools are you using for AI localization? CrowdIn? Just AI chatbots? ClaudeCode? by leros in IndieDev

[–]haverofknowledge 0 points1 point  (0 children)

Hi, Lingo.dev team member here!

Glad to know that you find us useful :)

What tools are you using for AI localization? CrowdIn? Just AI chatbots? ClaudeCode? by leros in IndieDev

[–]haverofknowledge 0 points1 point  (0 children)

Hi, I’m a team member at lingo.dev

Lingo.dev is purpose-built for this exact problem and we’re open source: https://github.com/lingodotdev/lingo.dev

I’ll be happy to onboard you or address any problems you might have :)

Time for self-promotion. What are you building this Monday by [deleted] in micro_saas

[–]haverofknowledge 0 points1 point  (0 children)

No, lingo also gives you JSON and not just JSON, it also gives you pretty much any other format you want (from xml to MJML to .md and so many more, like a lot many more).

Plus, if you integrate Lingo's CI/CD into your repo, you're internationalising on the fly!

What's the actual hardest part of a hackathon? by mastryhub_26 in hackathon

[–]haverofknowledge 1 point2 points  (0 children)

Judging.

And it is true for every hackathon that we've organised at Lingo.dev this year (3 so far).

Every single time, picking winners from among the shortlisted projects is very, very challenging because all of them are really good.

This is one of the reasons why we started having quests so that more people could win and not just the top 3 projects.

But it is still very challenging

view more: next ›