Skip to content

Conversation

@Dvurechensky
Copy link

@Dvurechensky Dvurechensky commented Aug 15, 2025

Hello, I am unaware of your overall stance on Russia, but I am solely representing my own interests in this communication. I would like to assist in the development of the project. Based on your project, I am creating my own customized Russian-language portal, which would offer a personalized programmer's portfolio, with sections that are not included in your official version.

I have accumulated changes to the language files and decided to send some of my work from a separate project to your project. Unfortunately, filling out Crowdin takes quite a long time, and many keys for translations were simply missing from the Russian translation file: locale_ru-RU.ini, as well as from many other language files.

In connection with this, I conducted an analysis and regeneration of them, and I present the following:

  • Generated 31,526+ translation keys with English values (by default)
locales_add
  • All keys of Russian localization have been worked out, 668 translations and keys that were not created in the file with translations at all have been added.
add_ru_translates
  • Added the following commands:
    • make generate-locale - generates missing keys from en-US to the rest of the translation files in the options/locale folder
    • make search-not-exist-keys-locale - searches through all translation files for those keys that happened to be not added to the en-US version

Log generate:
generate_locales_first_step.log

Please check the following:

  1. Make sure you are targeting the main branch, pull requests on release branches are only allowed for backports.
  2. Make sure you have read contributing guidelines: https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md .
  3. For documentations contribution, please go to https://gitea.com/gitea/docs
  4. Describe what your pull request does and which issue you're targeting (if any).
  5. It is recommended to enable "Allow edits by maintainers", so maintainers can help more easily.
  6. Your input here will be included in the commit message when this PR has been merged. If you don't want some content to be included, please separate them with a line like ---.
  7. Delete all these tips before posting.

- Generated 31,000+ translation keys with English values
- All keys of `Russian` localization have been worked out, `668` translations and keys that were not created in the file with translations at all have been added.
- Added the following commands:
- 'make generate-locale' - generates missing keys from `en-US' to the rest of the translation files in the `options/locale`
folder
- `make search-not-exist-keys-locale` - searches through all translation files for those keys that happened to be not added to the `en-US` version
@GiteaBot
Copy link
Collaborator

@Dvurechensky I noticed you've updated the locales for non-English languages. These will be overwritten during the sync from our translation tool Crowdin. If you'd like to contribute your translations, please visit https://crowdin.com/project/gitea. Please revert the changes done on these files. 🍵

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Aug 15, 2025
@lunny
Copy link
Member

lunny commented Aug 15, 2025

Hi @Dvurechensky, thank you for your contributions. However, we can’t accept changes to other languages through a pull request to the main branch. Please let me know if you’d like to be added as a proofreader in Crowdin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. modifies/internal modifies/translation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants