Skip to content

Update language file's#1396

Merged
awawa-dev merged 3 commits intoawawa-dev:masterfrom
AstaRom:master
Jan 5, 2026
Merged

Update language file's#1396
awawa-dev merged 3 commits intoawawa-dev:masterfrom
AstaRom:master

Conversation

@AstaRom
Copy link
Copy Markdown
Contributor

@AstaRom AstaRom commented Jan 2, 2026

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:
1

Other information:

  • Update language file's

@AstaRom
Copy link
Copy Markdown
Contributor Author

AstaRom commented Jan 3, 2026

@awawa-dev , Good evening and Happy New Year !!!!

Updated the translation files.
I've been wanting to standardize some of the strings in the files for a while, and I finally had a free minute.
To be precise, a couple of lines:

"..._title": "..."
"..._expl": "..."

Now they follow each other in the same order; before, they followed each other in one part of the file, but changed places in another. Just tried ChatGPT for this)) But even after running the search and replace code he suggested, I still saw with my own eyes that nothing was broken.

@awawa-dev
Copy link
Copy Markdown
Owner

Hi,
Thank you very much for the PR 🚀 I have a question: since I want to release a new test version v22beta1 soon and the current PR is quite large, can we focus on translations in it? I will probably update the license year in individual files as needed if any changes appear in them.

@AstaRom
Copy link
Copy Markdown
Contributor Author

AstaRom commented Jan 4, 2026

and the current PR is quite large

If necessary, I can remove the year-specific changes from the query. But in my opinion, this isn't such a big change; if half the code is rewritten, that's certainly a significant change, whereas here, for the most part, only one number changes, and not in all files.

I think it would be logical to merge the changes and release a test version so that don't have to go back to the year every time I edit a file.

You're the repository owner, and only you can decide whether a change is significant. Most users aren't interested in the development process, and not just in HyperHDR. They simply download a new version when it's released, and not everyone even checks the release changelog)))

@AstaRom
Copy link
Copy Markdown
Contributor Author

AstaRom commented Jan 4, 2026

You could file the changes separately, in two requests, to avoid confusion. I think that would be more appropriate. At the very least, it would be easier to view the change history, although only a very small percentage of the project's users will be doing this))

@AstaRom AstaRom changed the title Update language file's + Update development time Update language file's Jan 5, 2026
@awawa-dev awawa-dev merged commit 7ed356c into awawa-dev:master Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants