Skip to content

Add "pt" locale for newsletter #23278

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 4 commits into from
May 12, 2025
Merged

Conversation

filipesmedeiros
Copy link
Contributor

@filipesmedeiros filipesmedeiros commented May 10, 2025

Just European Portuguese translations :)

Copy link
Contributor

coderabbitai bot commented May 10, 2025

Walkthrough

The change updates the Portuguese translation file for newsletters by populating all previously empty translation strings with their appropriate Portuguese equivalents. No new keys were introduced or removed; the update solely fills in the existing keys with localized Portuguese text for various newsletter and membership-related messages.

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 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 77e1aac and 9378255.

📒 Files selected for processing (1)
  • ghost/i18n/locales/pt/newsletter.json (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • ghost/i18n/locales/pt/newsletter.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: 0

🧹 Nitpick comments (7)
ghost/i18n/locales/pt/newsletter.json (7)

4-4: Update translation for "By {authors}".
The preposition “by” in this context is more naturally rendered as “Por {authors}” rather than “De {authors}”.


6-6: Incorrect translation of "complimentary".
Here “complimentary” means “cortesia” or “grátis”, not “complementar”. Consider using "cortesia" or "grátis" to convey the intended meaning.


10-10: Adjust translation of "Less like this".
The UI action “Less like this” is not “I didn’t like it” but a filtering command. A better translation would be "Menos assim" or "Mostrar menos como este".


17-17: Refine translation of "trialing".
The English key “trialing” refers to an active trial period. For clarity, consider "em período de teste" or "em avaliação".


19-20: Consistent translation for "Upgrade" action.

  • The key "Upgrade" is currently "Fazer upgrade", retaining the English term; consider "Atualizar" or "Atualização".
  • For "Upgrade to continue reading.", the translation is missing a trailing period—please add . to match the source punctuation.

21-21: Translate "browser" to Portuguese.
The translation "Ver no browser" preserves the English word “browser”. For full localization, use "Ver no navegador".


22-22: Fix typo in email term.
The text uses "e-email" but the correct Portuguese term is "e-mail". Please update accordingly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3270d20 and 5e5b0e6.

📒 Files selected for processing (1)
  • ghost/i18n/locales/pt/newsletter.json (1 hunks)
🔇 Additional comments (2)
ghost/i18n/locales/pt/newsletter.json (2)

3-6: Placeholders and HTML tags preserved correctly.
The translations maintain the variable placeholders ({site}, {authors}, {date}) and HTML <strong> tags exactly as in the source, ensuring template integrity.

Also applies to: 22-27


6-9: General translations look accurate.
Static phrases such as "Comentar", "E-mail", "grátis", "Continuar a ler", "Gerir subscrição", "Membro desde", "Gostei", "Nome", "pago", "Detalhes da subscrição", and "Cancelar subscrição" correctly reflect their English originals.

Also applies to: 11-16, 18-19

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.

Thanks for this contribution. Your commit message about AI overloads has me laughing.

Because I do not speak Portuguese, I've used AI tools to review your contribution and left a few notes on it. As the EXPERT HUMAN, you are welcome and encouraged to overrule the AI at any point, but please do take look, because sometimes the AI does catch an error.

Please request a re-review or leave a comment and @ me when ready for me to look at it again. Thanks!

"Name": "Nome",
"paid": "pago",
"Subscription details": "Detalhes da subscrição",
"trialing": "em període de avaliação",
Copy link
Member

Choose a reason for hiding this comment

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

Is this supposed to be período ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes!

"Upgrade": "Fazer upgrade",
"Upgrade to continue reading.": "Faça upgrade para continuar a ler.",
"View in browser": "Ver no navegador",
"You are receiving this because you are a <strong>%%{status}%% subscriber</strong> to {site}.": "Está a receber este e-mail porque é <strong>subscritor/a %%{status}%%</strong> de {site}.",
Copy link
Member

Choose a reason for hiding this comment

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

The 'status' variable will be substituted with the strings for free, paid, complimentary, and trialing. Could you please review these for grammar? This is an area that has been troublesome for many translators. AI suggests 'com oferta' instead of 'oferta'.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I changed the phrasing. It's more verbose, but I think clearer and a but more natural.

@cathysarisky cathysarisky merged commit ecb6c53 into TryGhost:main May 12, 2025
26 checks passed
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