Skip to content

Added transtation into Russian for new lines. #23144

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.

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

Merged
merged 5 commits into from
May 6, 2025
Merged

Conversation

hide-me
Copy link
Contributor

@hide-me hide-me commented May 1, 2025

  • Why are you making it?
    Because I'm russian translator for Ghost. Previous translation also made by me.
  • What does it do?
    Added transtation into Russian for new lines in lang files.
  • Why is this something Ghost users or developers need?
    It's awesome when users have completely translated UI, right?

Please check your PR against these items:

  • I've read and followed the Contributor Guide
  • I've explained my change
  • I've written an automated test to prove my change works

We appreciate your contribution! 🙏 --Thanks

Copy link
Contributor

coderabbitai bot commented May 1, 2025

"""

Walkthrough

This pull request updates the Russian localization files for several user-facing components: comments, core platform, newsletter, and portal. The changes consist of filling in previously empty translation strings with appropriate Russian text, refining existing translations for clarity and consistency, and shortening certain time-related phrases by using abbreviations (e.g., "ч." for hours and "мин." for minutes). Adjustments also include minor wording changes, such as refining prepositions and possessive pronouns, and updating terminology (e.g., "Членство" to "Подписки" in the portal). No changes were made to any control flow, logic, or exported/public code entities; all modifications are limited to the content of JSON localization files.

Possibly related PRs

Suggested reviewers

  • cathysarisky
    """

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db56816 and b5e3846.

📒 Files selected for processing (1)
  • ghost/i18n/locales/ru/comments.json (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • ghost/i18n/locales/ru/comments.json

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (5)
ghost/i18n/locales/ru/newsletter.json (1)

19-19: Inconsistent translation of “Upgrade”
To maintain consistency across locale files, consider using “Обновить подписку” or simply “Обновить” instead of “Улучшить подписку.”

ghost/i18n/locales/ru/comments.json (2)

16-16: Consider plural form for “Best”
Suggest using “Лучшие” instead of “Лучший” to match the plural context of sorting.


70-70: Inconsistent translation of “Upgrade now”
Align this with other “Upgrade” translations (e.g., “Обновить подписку сейчас” or “Обновить”).

ghost/i18n/locales/ru/ghost.json (1)

18-18: Sentence clarity could be improved
The phrase “чтобы отказать в доступе” may imply refusing access; consider “чтобы никто не получил доступ” for clearer intent.

ghost/i18n/locales/ru/portal.json (1)

107-107: Consider refining the wording
The translation mentions a limit on the number of subscribers; to reflect restriction of memberships, consider “В настоящее время подписка с этого домена электронной почты ограничена.”

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ef8c76f and 3e33d6d.

📒 Files selected for processing (4)
  • ghost/i18n/locales/ru/comments.json (4 hunks)
  • ghost/i18n/locales/ru/ghost.json (2 hunks)
  • ghost/i18n/locales/ru/newsletter.json (2 hunks)
  • ghost/i18n/locales/ru/portal.json (3 hunks)
🔇 Additional comments (21)
ghost/i18n/locales/ru/newsletter.json (2)

3-3: Translation looks accurate and contextually appropriate.


20-20: Translation of full sentence is well-formed and clear.

ghost/i18n/locales/ru/comments.json (4)

4-4: Clear and consistent abbreviation for hours.


5-5: Clear and consistent abbreviation for minutes.


44-44: Translation for “Newest” is concise and consistent.


45-45: Translation for “Oldest” is concise and consistent.

ghost/i18n/locales/ru/ghost.json (7)

8-8: Translation correctly fills the previously missing key.


11-11: Translation is accurate and preserves placeholders.


13-13: Translation is correct and natural.


20-20: Translation accurately reflects the source.


25-25: Translation is clear and idiomatic.


37-37: Translation is clear and contextually appropriate.


42-42: Translation preserves meaning and placeholders correctly.

ghost/i18n/locales/ru/portal.json (8)

18-18: Translation correctly covers the new key.


108-108: Translation accurately reflects the source.


176-176: Translation for retry message (days) is clear and consistent.


177-177: Translation for retry message (hours) is clear and consistent.


178-178: Translation for retry message (minutes) is clear and consistent.


179-179: Translation for sign-in retry (days) is clear and consistent.


180-180: Translation for sign-in retry (hours) is clear and consistent.


181-181: Translation for sign-in retry (minutes) is clear and consistent.

@cathysarisky
Copy link
Member

Hey @hide-me ! Thanks for the contribution. Could you please have a quick look at the issues identified by coderabbitai above?

Added colons according to the recommendations
@hide-me
Copy link
Contributor Author

hide-me commented May 1, 2025

@cathysarisky sure! Fixed by adding colons according to coderabbitai recommendations

Copy link
Member

@cathysarisky cathysarisky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just two questions and then I think this will be ready to go! :)

@hide-me
Copy link
Contributor Author

hide-me commented May 4, 2025

@cathysarisky thank you for detailed review! I hope for now users will have 100% complete and consistent translation. If you have any other questions fell free to ask!

Have a nice day 🤍

@cathysarisky cathysarisky merged commit 91843a0 into TryGhost:main May 6, 2025
26 checks passed
@cathysarisky
Copy link
Member

And away we go! Thanks for the contribution! I've merged it, so it should appear in the next release! (5.119.2 or 5.120)

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

Successfully merging this pull request may close these issues.

2 participants