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

Update ghost.json #22364

Merged
merged 3 commits into from
Mar 8, 2025
Merged

Update ghost.json #22364

merged 3 commits into from
Mar 8, 2025

Conversation

Nasnl
Copy link
Contributor

@Nasnl Nasnl commented Mar 4, 2025

Small improvements in Dutch (switched from Flemish expressions to formal Dutch).

Small improvements in Dutch (switched from Flemish expressions to formal Dutch).
Copy link
Contributor

coderabbitai bot commented Mar 4, 2025

Walkthrough

The changes update the Dutch translations within the ghost/i18n/locales/nl/ghost.json file. Specifically, the modifications include revisions to five phrases to enhance clarity and formality. These changes involve rephrasing certain expressions and substituting informal verb forms with more formal alternatives. The updates do not affect the overall functionality of the application. There are no changes to the declarations of exported or public entities.

Suggested labels

affects:i18n


📜 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 20906e3 and e916bc3.

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

🪧 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.
  • @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.

@cathysarisky
Copy link
Contributor

Hello and thank you! @Nasnl !

@VirtualRoy or @dvdwinden , do you have a moment to review this small Dutch PR? When we get to tweaking words, I always like to have a native speaker look it over, instead of me and the AI! :) Thanks!

ChatGPT is flagging the comma removal as incorrect, but I trust your Dutch more than it, for sure! :)

@VirtualRoy
Copy link
Contributor

Hello and thank you! @Nasnl !

@VirtualRoy or @dvdwinden , do you have a moment to review this small Dutch PR? When we get to tweaking words, I always like to have a native speaker look it over, instead of me and the AI! :) Thanks!

ChatGPT is flagging the comma removal as incorrect, but I trust your Dutch more than it, for sure! :)

Hi @cathysarisky!

Regarding the switch from "kan" → "kunt" and "zal" → "zult", both forms are correct, but the updated version feels slightly more formal. It’s more a matter of preference rather than correctness.

As for the removed comma, I don’t think it was necessary to remove it. In Dutch, commas are often used to make sentences easier to read and avoid ambiguity. While Nasnl’s version isn’t incorrect, I personally prefer the original structure as it flows better.

Hope this helps!

@Nasnl
Copy link
Contributor Author

Nasnl commented Mar 5, 2025

Hi @VirtualRoy and @cathysarisky,

@VirtualRoy is right that all forms mentioned of the verb are possible in Dutch, and the original was not wrong, so it's more a subtle change than a correction. Yet, I plead for this small improvement for the following reason (I asked ChatGPT to formulate it short and powerful for me; you can check this independently from my opinion).


In transactional emails the standard, grammatically correct form is "je kunt". This is because:

Standard Conjugation:
In Dutch, the second person singular of "kunnen" in a normal subject–verb order should include the -t ending. Thus, when “je” is the subject preceding the verb, “je kunt” is correct.

Context and Formality:
Transactional emails, even if written in a relatively informal tone by using “je” instead of “u”, benefit from adhering to standard grammar rules. “Je kunt” conveys professionalism and clarity.

Colloquial Usage:
While “je kan” is often heard in informal speech or certain dialects, it is not considered the standard form in written communications. For transactional emails aimed at a broad audience, using the standard form is advisable.


So, while even me would sometimes say 'je kan', I would never write it because it doesn't seem professional. For Ghost, even in informal settings, you would not want to run the risk that the owner looks less professional.

The commas in the translations are used as they would be used in English writing, but not as in Dutch writing. In Dutch, commas are used less than English because the grammatic construction of sentences requires them to be used less, and the used translations are an example of that. Having said that, this is an even more subtle twist, so I'm not going to try to convince you, for running the risk of being seen as a 'taal-nazi' (that's Dutch for someone who goes too far in being right on language topics). ;-)

Thanks for considering guys! Either way, it's good.

@VirtualRoy
Copy link
Contributor

These PR's should be so fun to audit, respect to you @cathysarisky!

I should clarify that I agree with @Nasnl on "kan" → "kunt", "zal" → "zult". It's an improvement.

@cathysarisky
Copy link
Contributor

Sometimes it is a little tedious, but I love that we can have Ghost in all the languages! :)

So it sounds like there's good agreement on the verb changes. What shall we do about the commas?

@dvdwinden
Copy link
Contributor

dvdwinden commented Mar 6, 2025

Hiya! Thank you for your work on this. Much appreciated.

I agree with the changes regarding "kan" → "kunt", "zal" → "zult". I also agree that removing the commas is an improvement. (I work at Ghost full-time, and I think the removal of the commas makes for a slightly more to-the-point reading that matches our tone of voice more accurately).

One thing I'm unsure about, though, is the following:

Als deze aanvraag niet van jou is kun je deze e-mail negeren.

This technically says "If this request isn't yours, you can ignore this email", whereas the original says "If you did not make this request, you can safely ignore this email". The translation here seems a little off, and makes the request come across as a more passive occurrence (someone holding up a piece of paper they found on the floor, "is this yours?"), while in English the wording is quite active, implying an action has been taken.

My suggestion would be to align it a little closer to the original by saying:

Als jij deze aanvraag niet hebt gedaan kun je deze e-mail negeren.

This makes it more active and more personal, reflecting the fact that this request was made by a person.

@Nasnl
Copy link
Contributor Author

Nasnl commented Mar 6, 2025

@dvdwinden Yup, completely agree; that is a better translation and it delivers a better intent of the original message!

@dvdwinden
Copy link
Contributor

@Nasnl Great! Feel free to make the change, and then it can be merged 👏

Thank you all for contributing with this level of detail.

@VirtualRoy
Copy link
Contributor

Sounds good!

Nasnl added 2 commits March 6, 2025 14:08
Small improvements in Dutch translations
@Nasnl
Copy link
Contributor Author

Nasnl commented Mar 6, 2025

@dvdwinden Thanks! Done. Making things better step by step.

@ronaldlangeveld ronaldlangeveld merged commit b137818 into TryGhost:main Mar 8, 2025
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants