Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

GameTranslate

In-game translator at your disposal · By Godnoken

[🧱 Blocked by: Better Capital Letters Recognition] Preserve case

A topic by IDLT created Jun 05, 2025 Views: 110 Replies: 4
Viewing posts 1 to 3
(11 edits)

Issue Description

Game Translate’s OCR currently converts all recognized text to title case, which negatively affects the readability and accuracy of acronyms and all-caps text. For example:

• CUDA → Cuda

• OCR → Ocr

This behavior introduces two key issues:

  1. Reduced Readability: Acronyms become less recognizable when not in uppercase, which can confuse users (e.g., “Cuda” vs “CUDA”).

  2. Loss of Visual Hierarchy: Many games use all caps to differentiate titles or UI elements from body text. Changing the case undermines this formatting.

 

Examples

Original Image:

Note how the all-caps formatting indicates a title.

Current OCR Output:

Game Translate correctly identifies the text content but converts it to title case.

 

Proposed solution

Please preserve the original case of recognized text, especially for:

• Acronyms (e.g., keep CUDA, not Cuda)

• Fully capitalized words (used for emphasis or formatting)

This change would maintain the integrity and readability of the translated content.

Thank you! 🙏

Developer

Hiya mate, thank you once again for an A+ way to present your feedback!

The reason this was done initially was that the original translation models that were in use with GameTranslate struggled with capital letters. I believe that this likely isn't the case anymore - hence I will make some quick tests & remove this preprocessing step if everything looks good.

Developer

Heyo,

Sorry to be the bearer of bad news, but this is unfortunately still the case..

Uppercase words sometimes don't translate and sometimes mess up the translation. I am not entirely sure if this is an issue with the training data or the engine pipeline itself, but I believe it is the former. Nothing I can do about it at the moment :/

However, I will still disable this for DeepL. I could add this as an option too I suppose, but there's value in not letting the user change settings that (unknowingly) will affect translations. A tooltip would help, but from my experience, a lot of people don't bother reading.

It’s okay, not everything can be fixed immediately. I will update the tag of this issue so that we remember that it is being blocked by better character recognition.

Developer

Cheers mate!