Skip to content

chore(localizations): Update es-MX translations #5663

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
Jul 18, 2025

Conversation

LFCisneros
Copy link
Contributor

@LFCisneros LFCisneros commented Apr 17, 2025

Update the undefined values in order to have an entire translation for spanish (es-MX) tranlations This version will have an entire ortography review and update some words in order to be more friendly with the people using this spanish version

Description

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • New Features

    • Expanded and improved Spanish (Mexico) localization with many new and updated translations across badges, commerce, forms, UI elements, error messages, and page titles.
  • Bug Fixes

    • Corrected grammar, spelling, accents, and phrasing for greater clarity and accuracy in Mexican Spanish.
    • Standardized terminology and improved consistency in date, time, and error message formats.

Update the undefined values in order to have an entire translation for spanish (es-MX) tranlations
This version will have an entire ortography review and update some words in order to be more friendly with the people using this spanish version
Copy link

changeset-bot bot commented Apr 17, 2025

🦋 Changeset detected

Latest commit: 05f15a1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@clerk/localizations Patch
@clerk/clerk-js Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Apr 17, 2025

@LFCisneros is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

@clerk-cookie
Copy link
Collaborator

Hello 👋

We currently close PRs after 60 days of inactivity. It's been 50 days since the last update here. If we missed this PR, please reply here. Otherwise, we'll close this PR in 10 days.

Thanks for being a part of the Clerk community! 🙏

@clerk-cookie clerk-cookie added Stale and removed Stale labels Jun 8, 2025
@tmilewski tmilewski self-assigned this Jul 18, 2025
Copy link
Contributor

coderabbitai bot commented Jul 18, 2025

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The Spanish (Mexico) localization resource was comprehensively updated with many new translations and corrections. Numerous previously untranslated keys were assigned Spanish strings covering badges, commerce, forms, labels, error messages, UI buttons, and page titles. Existing translations were refined for grammar, spelling, punctuation, and idiomatic usage, including adjustments to date and time formats. Terminology was standardized across authentication, billing, organization management, and user profile sections. These changes improved coverage and linguistic accuracy without modifying any exported or public entity declarations. Additionally, a new changeset file was added to record this patch update for the @clerk/localizations package.


📜 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 dc3e78d and 05f15a1.

📒 Files selected for processing (1)
  • .changeset/stale-signs-cheer.md (1 hunks)

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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 110a74d and dc3e78d.

📒 Files selected for processing (1)
  • packages/localizations/src/es-MX.ts (33 hunks)
🧰 Additional context used
📓 Path-based instructions (9)
**/*.{js,jsx,ts,tsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
packages/**/*.{ts,tsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
packages/**/*.{ts,tsx,d.ts}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
**/*.{ts,tsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/development.mdc
  • .cursor/rules/typescript.mdc
packages/localizations/**/*

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/monorepo.mdc
**/*.{js,ts,tsx,jsx}

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • .cursor/rules/monorepo.mdc
**/*

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

**/localizations/**/*.ts

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

🔇 Additional comments (10)
packages/localizations/src/es-MX.ts (10)

53-64: LGTM! Badge translations are accurate and appropriate.

The Spanish translations for badges are well-chosen and appropriate for Mexican Spanish users. The terminology is consistent and user-friendly.


73-142: Excellent commerce translations for Mexican Spanish users.

The commerce-related translations are accurate, professional, and appropriate for Mexican Spanish. The terminology is consistent with standard Spanish business language and maintains the appropriate tone for billing and subscription contexts.


177-216: Well-translated form field labels and placeholders.

The form field labels and placeholders are accurately translated and appropriate for Mexican Spanish users. The terminology is consistent and maintains clarity for user interaction.


233-456: Excellent organization management translations.

The organization-related translations are comprehensive, accurate, and appropriate for Mexican Spanish users. The terminology is consistent and maintains the professional tone needed for organization management features.


474-532: Comprehensive and accurate reverification translations.

The reverification section translations are well-executed, maintaining consistency with established terminology and providing clear explanations appropriate for Mexican Spanish users.


554-690: Comprehensive sign-in translations with consistent terminology.

The sign-in section translations are accurate, comprehensive, and maintain consistency with established terminology. The language is appropriate and user-friendly for Mexican Spanish users.


701-781: Well-translated sign-up process with consistent terminology.

The sign-up translations are accurate and maintain consistency with established terminology. The language is appropriate and user-friendly for Mexican Spanish users.


783-877: Comprehensive and accurate error message translations.

The error messages are well-translated and appropriate for Mexican Spanish users. The language maintains the necessary clarity for error communication while being user-friendly.


885-1227: Comprehensive user profile translations with consistent terminology.

The user profile section translations are extensive, accurate, and maintain consistency with established terminology. The language is appropriate for Mexican Spanish users and covers all aspects of user account management effectively.


1230-1240: Well-translated waitlist functionality.

The waitlist translations are accurate and maintain an appropriate welcoming tone. The language is clear and user-friendly for Mexican Spanish users.

@tmilewski
Copy link
Member

Thanks, @LFCisneros!

@tmilewski tmilewski merged commit 305e5e4 into clerk:main Jul 18, 2025
4 of 6 checks passed
Copy link

pkg-pr-new bot commented Jul 18, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@5663

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@5663

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@5663

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@5663

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@5663

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@5663

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@5663

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@5663

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@5663

@clerk/express

npm i https://pkg.pr.new/@clerk/express@5663

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@5663

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@5663

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@5663

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@5663

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@5663

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@5663

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@5663

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@5663

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@5663

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@5663

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@5663

@clerk/types

npm i https://pkg.pr.new/@clerk/types@5663

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@5663

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@5663

commit: 05f15a1

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.

3 participants