🌐 Updated Bulgarian translations

[yovko]

Changes:

Updated the Bulgarian translation of comments.json and portal.json to include recently added strings.
Refined some existing translations for better clarity, conciseness, and improved UI consistency.

---

Note

Low Risk
Pure i18n string updates in comments.json and portal.json with no functional logic changes; risk is limited to potential wording/consistency regressions.

Overview
Updates Bulgarian (bg) locale strings for comments and Portal to fill in previously missing translations for newly added UI labels and error/help messaging.

Also refines several existing Bulgarian phrases for consistency and clarity (e.g., wording around “updated/обновен”, billing-related labels, and various mail-provider action labels).

^{Written by Cursor Bugbot for commit 4d5509b. This will update automatically on new commits. Configure here.}

[coderabbitai]

Walkthrough

This pull request fills in previously empty Bulgarian translations in Ghost i18n locale files. In ghost/i18n/locales/bg/comments.json five comment-related keys receive Bulgarian strings. In ghost/i18n/locales/bg/portal.json multiple portal-related keys (billing, payments, subscription, email links, podcasts, and success/failure messages) are populated or refined, adding ~21 translations and minor punctuation/tag placement adjustments.

Possibly related PRs

• 🌐 Updated Bulgarian translations #26033 — Modifies the same ghost/i18n/locales/bg/portal.json, filling Bulgarian portal translation strings that overlap with this PR.

Suggested reviewers

• cathysarisky

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and directly describes the main change: Bulgarian translation updates for locale files.
Description check	✅ Passed	The description is well-related to the changeset, explaining the Bulgarian translation updates and refinements made to comments.json and portal.json.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@ghost/i18n/locales/bg/portal.json`:
- Line 26: The translation for the JSON key "Billing info & receipts" currently
omits "receipts" (value is "Платежна информация"); update the value in
portal.json so it mirrors the full English phrase, e.g. replace "Платежна
информация" with a complete Bulgarian translation such as "Платежна информация и
разписки" (or another accurate equivalent), ensuring the JSON key "Billing info
& receipts" maps to the full translated phrase.
- Line 85: The Bulgarian translation for the key "Failed to update billing
information, please try again" ends with a trailing period while the source and
sibling translations do not; remove the final period from the value "Неуспешно
обновяване на данните за плащане, опитайте отново." so it becomes "Неуспешно
обновяване на данните за плащане, опитайте отново" to match the other "Failed to
..." messages.

🧹 Nitpick comments (1)

ghost/i18n/locales/bg/comments.json (1)

22-22: Minor: inconsistent translation of "Contact support" across namespaces.

In comments.json (line 22) this is translated as "Свържете се с поддръжката" (imperative), while in portal.json (line 49) the same English key is "Връзка с поддръжката" (noun phrase). Consider aligning them for UI consistency, though this is not blocking.