Update language file's

[AstaRom]

Summary

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

Other information:

• Update language file's

[awawa-dev]

Hi
I’m not sure if we should keep running the entire translation over and over with a low change threshold, especially when using AI or external services. Further iterations don't seem to add much value, as it's very easy to lose context, and it's unlikely to catch actual bugs.

From my testing, it helps to break it down into smaller fragments and provide the English version as a reference along with one matching translation (e.g., German, Polish, or French). This helps the tool pick up better context for translating or verifying the third (target) language. Also, you really have to push the automation to look for "deal-breaker" errors or things taken out of context; otherwise, it just obsesses over punctuation or risky style changes.

In the meantime, I found two more errors in the existing resources: one in English and one in Russian in PR: #1467

[AstaRom]

Updating files for the latest changes:

• 15b8972

[AstaRom]

Hi, dear @awawa-dev.

especially when using AI or external services

Regarding the use of AI, I translated the changes I previously submitted manually each time, simply in the browser window using Google Translate.

This helps the tool pick up better context for translating or verifying the third (target) language.

Yes, I can only fully and accurately translate my localization (ru).
I translate the other localizations as best I can using a translator, although it's certainly not 100% accurate.

Other users, whose native language is theirs, could correct the translations as needed, as they are more competent.
But, judging by the statistics, I see that in reality no one does this; everyone uses the ready made option without offering any improvements on their part.

I’m not sure if we should keep running the entire translation over and over with a low change threshold

In any case, minor changes are inevitable. For example, several commits have been made adding a few English translation strings, and I'm adding missing strings for other language files. In the process, I notice, for example, some errors in the French translation file that were made long ago during the translation process.

I'm making changes simultaneously.
Is it worth creating a separate query to, say, change a couple of characters in a string? I think that's unnecessary.
But this is just my opinion.

---

When I started working on this (making changes like this) after discovering such a great project as HyperHDR, only the "en.json" file was constantly updated. In most cases, no one was eager to make changes to other files, even though I'm sure the project has a large audience. Somewhere there were outdated strings—more precisely, there was a translation key, but its contents weren't entirely up-to-date, and the files were inconsistent. I tried to fix this and somehow bring them into a more consistent format.

If my previous commits to the translation files are unnecessary or not entirely grammatically correct, I won't bother with them going forward. I'll only update the "ru.json" file as needed, and leave the rest to someone else.

[awawa-dev]

I agree that we should focus on English and our native languages, as others are hard to verify - especially the niche ones where we’ve had zero user feedback. To streamline the project (saving time and reducing app resource size), we should consider removing them and adding languages like Portuguese (BR) or Hindi instead, which I could likely handle.

Off-topic: Since using Google Translate for tasks outside of HyperHDR, I've noticed a significant drop in quality. They are likely shifting resources to Gemini.

[AstaRom]

Everyone is trying to optimize, reduce server capacity, and dedicate some resources to AI. But unfortunately, as you've noticed, quality is declining.