Skip to content

Feature/add es us language#7520

Merged
mfbrown merged 6 commits intomainfrom
feature/add-es-us-language
Mar 12, 2026
Merged

Feature/add es us language#7520
mfbrown merged 6 commits intomainfrom
feature/add-es-us-language

Conversation

@mfbrown
Copy link
Contributor

@mfbrown mfbrown commented Feb 27, 2026

Ticket ENG-2843

Description Of Changes

Code Changes

Steps to Confirm

Pre-Merge Checklist

  • Issue requirements met
  • All CI pipelines succeeded
  • CHANGELOG.md updated
    • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
    • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
    • Updates unreleased work already in Changelog, no new entry necessary
  • UX feedback:
    • All UX related changes have been reviewed by a designer
    • No UX review needed
  • Followup issues:
    • Followup issues created
    • No followup issues
  • Database migrations:
    • Ensure that your downrev is up to date with the latest revision on main
    • Ensure that your downgrade() migration is correct and works
      • If a downgrade migration is not possible for this change, please call this out in the PR description!
    • No migrations
  • Documentation:
    • Documentation complete, PR opened in fidesdocs
    • Documentation issue created in fidesdocs
    • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
    • No documentation updates required

@vercel
Copy link
Contributor

vercel bot commented Feb 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
fides-plus-nightly Ready Ready Preview, Comment Mar 12, 2026 5:24pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
fides-privacy-center Ignored Ignored Mar 12, 2026 5:24pm

Request Review

@gilluminate
Copy link
Contributor

@mfbrown all of the problems here are stemming from work done 4 months ago on clients/admin-ui/src/features/assessments/AssessmentChatModal.tsx. Did you mean to include that in this PR?

@mfbrown mfbrown marked this pull request as ready for review March 12, 2026 17:20
@mfbrown mfbrown requested review from a team as code owners March 12, 2026 17:20
@mfbrown mfbrown requested review from erosselli, gilluminate and lucanovera and removed request for a team March 12, 2026 17:20
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 12, 2026

Greptile Summary

This PR adds es-US (Spanish — United States) as a new supported language, using the existing es-MX translations as the default starting point. All necessary files are updated consistently: the SupportedLanguage enums in both admin-ui and privacy-center, the backend languages.yml, the fides-js locale message files and their index registrations, and the i18n test locale count.

Key observations:

  • The es-US translations in both messages.json and messages-tcf.json are intentionally identical to es-MX, as documented in the changelog.
  • A minor typo (también una → should be también usa) is inherited from es-MX into the new es-US TCF messages file, and is worth correcting opportunistically.
  • The static.tcf.iab key present in the English TCF reference locale is absent from both es-MX and es-US — also worth adding since the value requires no translation.
  • All locale index files, test assertions, and enum definitions are updated correctly and follow established patterns.

Confidence Score: 4/5

  • This PR is safe to merge — it is purely additive, follows all established locale-addition patterns, and carries no risk of breaking existing behavior.
  • All 9 changed files are updated consistently and correctly. The only findings are two minor, pre-existing translation quality issues inherited from es-MX: a typo and a missing key. Neither affects functionality.
  • clients/fides-js/src/lib/tcf/i18n/locales/es-US/messages-tcf.json — minor inherited typo and missing key worth addressing before merge.

Important Files Changed

Filename Overview
clients/fides-js/src/lib/tcf/i18n/locales/es-US/messages-tcf.json New TCF locale file for es-US, identical to es-MX as documented. Contains a minor inherited typo ("también una" should be "también usa") and is missing the static.tcf.iab key present in the English reference — both issues pre-exist in es-MX.
clients/fides-js/src/lib/i18n/locales/es-US/messages.json New non-TCF locale file for es-US. Identical to es-MX messages.json as intended; all 11 keys match the English reference exactly.
clients/fides-js/src/lib/i18n/locales/index.ts Correctly adds esUS import, STATIC_MESSAGES entry, and LOCALE_LANGUAGE_MAP entry for es-US, following the established pattern.
clients/fides-js/src/lib/tcf/i18n/locales/index.ts Correctly adds esUS import and STATIC_MESSAGES_TCF entry for es-US. No LOCALE_LANGUAGE_MAP in this module — consistent with other TCF locale entries.
clients/fides-js/tests/lib/i18n/i18n-utils.test.ts Test locale count correctly updated from 41 to 42 for both loadMessagesFromFiles and loadTcfMessagesFromFiles.
clients/admin-ui/src/types/api/models/SupportedLanguage.ts ES_US enum value added correctly in alphabetical order after ES_MX.
clients/privacy-center/types/api/models/SupportedLanguage.ts ES_US enum value added correctly, consistent with admin-ui SupportedLanguage update.
src/fides/data/language/languages.yml es-US language entry added correctly in alphabetical order between es-MX and et.
changelog/7520-add-es-us-language.yaml Changelog entry added correctly describing the new es-US language code.

Last reviewed commit: 8848a46

@@ -0,0 +1,26 @@
{
"static.tcf.consent": "Consentimiento",
"static.tcf.cookie_disclosure.also_non_cookie": "Este proveedor también una otros métodos como “almacenamiento local” para almacenar y acceder a información en su dispositivo.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Inherited typo in translation

The phrase "también una otros métodos" contains a typo — "una" should be "usa" (meaning "uses"). The same issue exists in the es-MX source file this was copied from. Since this PR explicitly creates es-US from es-MX, this is a good opportunity to fix it here (and optionally in es-MX too).

Suggested change
"static.tcf.cookie_disclosure.also_non_cookie": "Este proveedor también una otros métodos como “almacenamiento local para almacenar y acceder a información en su dispositivo.",
"static.tcf.cookie_disclosure.also_non_cookie": "Este proveedor también usa otros métodos como \u201calmacenamiento local\u201d para almacenar y acceder a información en su dispositivo.",

Comment on lines +1 to +26
{
"static.tcf.consent": "Consentimiento",
"static.tcf.cookie_disclosure.also_non_cookie": "Este proveedor también una otros métodos como “almacenamiento local” para almacenar y acceder a información en su dispositivo.",
"static.tcf.cookie_disclosure.intro": "almacena cookies con una duración máxima de alrededor de estos días.",
"static.tcf.cookie_disclosure.non_cookie": "usa métodos como “almacenamiento local” para almacenar y acceder a información en su dispositivo.",
"static.tcf.cookie_disclosure.refresh": "Estas cookies se pueden actualizar.",
"static.tcf.data_categories": "Categorías de datos",
"static.tcf.features": "Características",
"static.tcf.features.description": "A continuación, encontrará una lista de las características para las que se están procesando sus datos. Puede ejercer sus derechos para las características especiales usando los botones a continuación.",
"static.tcf.legint": "Interés legítimo",
"static.tcf.legint_disclosure": "Divulgación de interés legítimo",
"static.tcf.privacy_policy": "Política de privacidad",
"static.tcf.purposes": "Propósitos",
"static.tcf.purposes.description": "A continuación, encontrará una lista de los propósitos y características especiales para los que se están procesando sus datos. Puede ejercer sus derechos para propósitos específicos, basándose en el consentimiento o interés legítimo, usando los botones a continuación.",
"static.tcf.retention": "Retención",
"static.tcf.retention_period_days": "día(s)",
"static.tcf.special_features": "Características especiales",
"static.tcf.special_purposes": "Propósitos especiales",
"static.tcf.vendors": "Proveedores",
"static.tcf.vendors.description": "A continuación, encontrará una lista de los proveedores que procesan sus datos y los propósitos o características de procesamiento que ellos declaran. Puede ejercer sus derechos para cada proveedor basándose en la base legal que afirman.",
"static.tcf.vendors.iab": "Proveedores IAB TCF",
"static.tcf.vendors.other": "Otros proveedores",
"static.tcf.vendors_count": "proveedor(es)",
"static.tcf.vendors_using_consent": "Proveedores que usan consentimiento",
"static.tcf.vendors_using_legint": "Proveedores que usan interés legítimo"
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Missing translation key static.tcf.iab

The English reference locale (en/messages-tcf.json) includes the key "static.tcf.iab": "IAB TCF", which is absent from both es-MX and this new es-US file. This is a pre-existing gap inherited from es-MX. Since es-US is being created fresh here, it would be a good opportunity to add it:

"static.tcf.iab": "IAB TCF",

(The value is an acronym so no translation is needed.)

Copy link
Contributor

@gilluminate gilluminate left a comment

Choose a reason for hiding this comment

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

LGTM!

@mfbrown mfbrown added this pull request to the merge queue Mar 12, 2026
Merged via the queue into main with commit 27e3492 Mar 12, 2026
46 checks passed
@mfbrown mfbrown deleted the feature/add-es-us-language branch March 12, 2026 19:02
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.

2 participants