Updated Hungarian locale json files

[ibalosh]

Added more translations to Hungarian locale, based on ref #23361

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

[coderabbitai]

"""

Walkthrough

This change updates the Hungarian localization files for comments, portal, and general Ghost interface text by filling in previously empty translation strings with appropriate Hungarian translations. Existing translations were also refined for clarity and completeness. The updates affect user-facing messages related to commenting, membership, account management, email preferences, membership restrictions, and site status notices. No changes were made to the structure of the JSON files, nor were any logic or control flow elements modified; only the translation values were added or updated.

Possibly related PRs

• 🌐 Added missing i18n for expertise link in comments #23159: Adds the "Add your expertise" key and related comment interface localization, directly related to Hungarian comment translations updated here.
• 🌐 Updated Bulgarian translations #23431: Adds translations for previously untranslated keys in the comments section for Bulgarian, mirroring the Hungarian updates in this PR.
• Update ghost.json #22869: Updates missing translation strings in the ghost.json localization file for Turkish, similar in scope and purpose to this PR for Hungarian.

Suggested labels

affects:i18n

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 c7a9f25 and 9690611.

📒 Files selected for processing (2)

• ghost/i18n/locales/hu/ghost.json (3 hunks)
• ghost/i18n/locales/hu/portal.json (8 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• ghost/i18n/locales/hu/ghost.json
• ghost/i18n/locales/hu/portal.json

⏰ Context from checks skipped due to timeout of 90000ms (9)

• GitHub Check: Regression tests (Node 20.11.1, sqlite3)
• GitHub Check: Regression tests (Node 20.11.1, mysql8)
• GitHub Check: Ghost-CLI tests
• GitHub Check: Database tests (Node 20.11.1, sqlite3)
• GitHub Check: Database tests (Node 20.11.1, mysql8)
• GitHub Check: Database tests (Node 22.13.1, mysql8)
• GitHub Check: Unit tests (Node 20.11.1)
• GitHub Check: Unit tests (Node 22.13.1)
• GitHub Check: Lint

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

[ibalosh]

Hi @cathysarisky

as promised, added Hungarian translations