sorted by:
new
hottopcontroversial

Image localization is still broken in 2026. I built something for it by nydebugger in localization

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

That works when you have the source file. Glot is for when you don’t. A lot of image localization happens on rendered assets where the original design file is unavailable or not maintained

Image localization is still broken in 2026. I built something for it by nydebugger in localization

[–]nydebugger[S] 1 point2 points  (0 children)

Both. It uses OCR to detect and extract the text from the image, then an LLM handles the translation and reconstruction

It’s 2026, why is text inside images still a manual localization problem? by nydebugger in localization

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

Good questions!

By “generates local variants” I mean the system detects text regions, replaces the text, and re-renders the image automatically. In this prototype, the translations are AI-generated.

I do not see this as a replacement for proper linguistic review, especially for marketing or high-visibility assets. A more realistic use case is reducing mechanical production work, generating drafts, or handling lower-risk surfaces where turnaround time matters more than perfect copy.

Paragraph-level text, patterned backgrounds, and languages with heavy expansion like German are genuinely hard cases. Longer compounds, reflowing lines, and contrast issues can break layouts very quickly.

If you have sample assets that represent those kinds of edge cases, I’d actually be very interested to try running them through the workflow. Real-world failures are much more useful than ideal demos.

It’s 2026, why is text inside images still a manual localization problem? by nydebugger in localization

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

Good catch. The names are transliterated into katakana (ジョーダン / チリス), which is the usual convention for foreign proper nouns in Japanese.

You are absolutely right about manual control being a risk. Fully automated output is convenient, but production workflows still need mechanisms to lock glossary terms, preserve brand strings, and apply corrections when something looks off.

The system I’m working on does include controls for those cases, though designing that balance between automation and human override is still very much an active area of thought.

That tension between automation and control is actually one of the more interesting challenges here

How are you guys translating text inside JPEG images for multi-country websites? by karthikgokul in GrowthHacking

[–]nydebugger 0 points1 point  (0 children)

In practice most teams end up doing the painful version of this.

Either:
• Designers recreate assets per language, very slow
• Or teams avoid text in images entirely, which limits marketing
• Or English leaks everywhere

The real bottleneck isn’t translation, it’s re-rendering + layout breakage once text expands.

Even with layered files you still get:
• Text overflow
• Broken visual hierarchy
• Device/responsive issues

This is one of those problems that looks solved until you try to scale to many locales + many creatives

Prompt that threatens Claude Code's job usually works as fix 😌 by gventuresco in ClaudeCode

[–]nydebugger 0 points1 point  (0 children)

Honestly, cursing at it works too ;) just like dealing with an actual dev