Skip to content
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

🌐 Updated German translations #22241

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

JTBrinkmann
Copy link

Added missing german translations.

I couldn't get unit tests and the linter running, but this shouldn't be related to the PR itself.

Copy link
Contributor

coderabbitai bot commented Feb 19, 2025

Walkthrough

This pull request updates German localization files by providing complete translations for various interface strings in Ghost. The changes span three JSON files: comments.json, newsletter.json, and portal.json. Previously empty strings are replaced with German text covering actions, notifications, subscription details, and error messages. The updates ensure that elements such as confirmation prompts, subscription management options, and notification messages are properly localized. There are no changes to the exported or public entity declarations; the modifications are strictly limited to localization content.

Possibly related PRs

  • Update comments.json #22237: The changes involve modifications to the comments.json file with updates to German translations for user interface strings.
  • Update newsletter.json #22235: This PR also updates localization strings in JSON files, enhancing German translations for user interface elements, though it targets different files.
  • 🌐 Updated Bulgarian translations #21932: This PR updates Bulgarian localization strings for comments, relating to the same phrases modified in the German localization updates.

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 bcfffcf and 4854e8c.

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

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.

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. (Beta)
  • @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

@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 a few minor comments, but generally LGTM!

"trialing": "Probe-",
"Unsubscribe": "Abbestellen",
"View in browser": "Im Browser ansehen",
"You are receiving this because you are a <strong>%%{status}%% subscriber</strong> to {site}.": "Du erhälst diese Nachricht weil du <strong>%%{status}%% Mitglied</strong> von {site} bist.",
Copy link
Contributor

Choose a reason for hiding this comment

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

AI says this should be erhältst ? Correct?

Copy link

Choose a reason for hiding this comment

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

Yes, seems to be a typo "erhältst" is correct.

"Name": "Name",
"paid": "zahlendes",
"Subscription details": "Abo Details",
"trialing": "Probe-",
Copy link
Contributor

Choose a reason for hiding this comment

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

The present set of translation strings for free/paid/trialing/complimentary get substituted in for %%status%%. That's going to result in a space after the hyphen for trialing. Adequate, or do you want to pull the word Mitglied into the free/trialing/etc phrases and remove it from the full-sentence translation?

Copy link
Author

Choose a reason for hiding this comment

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

You are right, that is suboptimal. The issue is that "trialing subscriber" would be translated as a compound noun in German. I could not come up with an adjective that would fit as a separate word.

Ideally, instead of inserting an adjective as placeholder, it would be changed to "free_subscriber", "paid_subscriber", etc, would should also work with other languages.

Here's an alternative, though hacky solution:

        "complimentary": "kostenfreies Mitglied",
        "free": "kostenfreies Mitglied",
        "paid": "zahlendes Mitglied",
        "trialing": "Probemitglied",
        "You are receiving this because you are a <strong>%%{status}%% subscriber</strong> to {site}.": "Du erhälst diese Nachricht weil du <strong>%%{status}%%</strong> von {site} bist.",

But I worried that that's not future proof, as "free" etc would be used in other contexts.

Copy link
Author

Choose a reason for hiding this comment

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

I changed it to "Probeabo Mitglied" which still isn't perfect, but should look less weird than "Probe- Mitglied".

This was referenced Feb 19, 2025
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.

4 participants