Skip to content

🌐 Updated Spanish translations #23524

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

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

Conversation

eduardopuente
Copy link

Translation of some missing strings, improve translations by changing some anglicisms and fix some grammar mistakes (and typos)

Copy link
Contributor

coderabbitai bot commented May 26, 2025

Walkthrough

The update modifies the Spanish translation file for the portal, focusing on improving the accuracy, fluency, and consistency of the text. Changes include rephrasing discount-related strings, adding missing translations, correcting typos and grammar, updating terminology, and refining technical terms. Some example names and emails were changed to more appropriate Spanish versions. The update also addresses previously untranslated keys related to membership and sign-up attempts, and makes stylistic adjustments for clarity and readability. No changes were made to code structure or exported entities; only translation string values were updated.

Possibly related PRs

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 32587ea and 7ca6d45.

📒 Files selected for processing (1)
  • ghost/i18n/locales/es/portal.json (7 hunks)
✅ Files skipped from review due to trivial changes (1)
  • ghost/i18n/locales/es/portal.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.
    • 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.

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: 10

🧹 Nitpick comments (3)
ghost/i18n/locales/es/portal.json (3)

41-41: Falta punto final en la traducción

La clave original termina con un punto. Añade “.” al final:

-"Preferencias de los comentarios actualizadas"
+"Preferencias de los comentarios actualizadas."

97-98: Corrección de acento y typo en “deshabilitados”

  • Línea 97: “aun así” → “aún así”
  • Línea 98: “desabilitados” → “deshabilitados”
-    "If you've completed all these checks and you're still not receiving emails, you can reach out to get support by contacting {supportAddress}.": "Si has comprobado todo y aun así no estás recibiendo los correos electrónicos, puedes comunicarte con soporte técnico contactando con {supportAddress}.",
+    "If you've completed all these checks and you're still not receiving emails, you can reach out to get support by contacting {supportAddress}.": "Si has comprobado todo y aún así no estás recibiendo los correos electrónicos, puedes contactar con soporte técnico en {supportAddress}.",

-    "In the event a permanent failure is received when attempting to send a newsletter, emails will be disabled on the account.": "En el caso de que haya un problema al intentar enviar el boletín, los correos electrónicos serán desabilitados en su cuenta.",
+    "In the event a permanent failure is received when attempting to send a newsletter, emails will be disabled on the account.": "En caso de recibir un fallo permanente al enviar un boletín, los correos electrónicos se deshabilitarán en tu cuenta.",

174-174: Inconsistencia en acento de “solo/sólo”

Aquí se usa “sólo” con tilde, mientras que en líneas previas queda sin ella. Recomiendo uniformar según la guía de estilo (sin tilde para adverbio).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4963f54 and 32587ea.

📒 Files selected for processing (1)
  • ghost/i18n/locales/es/portal.json (7 hunks)
🔇 Additional comments (20)
ghost/i18n/locales/es/portal.json (20)

5-6: Discount string translations are accurate

Las dos cadenas de descuento han sido traducidas correctamente: se usa “durante los primeros” y se conservan los marcadores {number}/{period} y la puntuación.


18-19: Personal note and trial-end messages look good

“Add a personal note” y la explicación del fin del periodo de prueba gratuito están correctamente traducidas y fluyen bien en español.


22-22: Unexpected error message is clear

La frase “Ha ocurrido un error inesperado. Por favor inténtalo de nuevo o contacta a soporte técnico…” traduce fielmente el original y mantiene el enlace correctamente.


27-27: “Cancel anytime.” traducido correctamente

La traducción “Cancela en cualquier momento.” está en imperativo como el original y es clara.


36-36: “Choose a different plan” en imperativo

“Elige otro plan” es consistente con el estilo de imperativos del resto de la interfaz.


43-43: “Complimentary” → “Gratis” es apropiado

Traducción directa y comprensible para indicar algo sin coste.


51-52: Mensajes de sesión y enlace vencido correctos

“No se pudo iniciar sesión. El enlace de inicio de sesión ha expirado.” y “¡No se pudo actualizar el correo electrónico! Enlace no válido.” traducen fielmente ambos orígenes.


56-56: Gestión de preferencias vía botón

“¿No quisiste hacer esto? Puedes gestionar tus preferencias aquí.” es claro y mantiene el marcado.


61-62: Configuración de boletín y preferencias de correo electrónico

Ambas cadenas están correctamente traducidas y utilizan terminología consistente.


100-102: Ejemplos y dirección de email actualizados correctamente

Los ejemplos se han adaptado al castellano y las cadenas de validación están bien.


113-114: Ayuda y deshabilitación de boletines

Ambas cadenas (“Need more help?” y “Newsletters can be disabled…”) se han traducido correctamente.


123-124: Mensajes de cancelación de pago y actualización de plan

Las traducciones de “Plan checkout was cancelled.” y “Plan upgrade was cancelled.” son claras y correctas.


127-127: “Please fill in required fields” está bien

La frase en infinitivo se ajusta al estilo imperativo del resto del portal.


131-131: “Renews at {price}.” traducido correctamente

La estructura y marcador de posición se mantienen adecuadamente.


155-158: Mensajes de éxito consistentes y comprensibles

Las cuatro cadenas “Success…” usan “¡Funcionó!” de forma coherente y clara.


171-172: Modo solo/invitación y donaciones

Las traducciones de “invite-only” y “not accepting donations” son correctas y claras.


179-183: Mensajes de límite de intentos correctos

Las cinco cadenas de “Too many…” se han traducido de forma coherente y mantienen los marcadores de posición.


187-187: “Unsubscribe from all emails” en infinitivo

La traducción “Darse de baja de todos los correos electrónicos” es clara y se ajusta al estilo de comandos/invitación.


189-190: Mensajes de baja de correo precisos

Tanto “Unsubscribed from all emails.” como la aclaración sobre la suscripción de pago están correctamente traducidos.


204-204: Mensaje de actualización de membresía gratuita

“La membresía gratuita… actualiza a una suscripción de pago…” refleja bien el original y es fluido.

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