Skip to content

Russian translation #4487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Russian translation #4487

wants to merge 1 commit into from

Conversation

sergius02
Copy link
Contributor

References

Description

First version of a russian translatrion for DSpace

Instructions for Reviewers

Change the language using the dropdown

List of changes in this PR:

  • ru.json5. The main file of the translation.
  • config.example.yml. Added the option to the language list

Checklist

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

@tdonohue tdonohue requested a review from ybnd June 23, 2025 15:25
@tdonohue tdonohue added i18n / l10n Internationalisation and localisation, related to message catalogs port to dspace-9_x This PR needs to be ported to `dspace-9_x` branch for next bug-fix release labels Jun 23, 2025
@tdonohue tdonohue moved this to 🙋 Needs Reviewers Assigned in DSpace 10.0 Release Jun 23, 2025
@tdonohue tdonohue added the 1 APPROVAL pull request only requires a single approval to merge label Jun 23, 2025
@tdonohue
Copy link
Member

@sergius02 : This PR is failing because the new ru.json5 file is failing lint checks. You should be able to see these failures locally by running npm run lint and then fixing the issues it has found. Once those lint checks pass, we can try to find a reviewer to test/review this.

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

@ybnd ybnd Awaiting requested review from ybnd

At least 1 approving review is required to merge this pull request.

Assignees

@sergius02 sergius02

Labels
1 APPROVAL pull request only requires a single approval to merge i18n / l10n Internationalisation and localisation, related to message catalogs port to dspace-9_x This PR needs to be ported to `dspace-9_x` branch for next bug-fix release
Projects
DSpace 10.0 Release
Status: 🙋 Needs Reviewers Assigned
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Russian translation
2 participants
@sergius02 @tdonohue