feat(web): Add complete Spanish UI translation catalogs - #996
Conversation
Register es alongside en and fr with a full matching message inventory, keeping institutional crypto terms like Token short and stable for layout. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@tomiet is attempting to deploy a commit to the Solana Foundation Team on Vercel. A member of the Team first needs to authorize it. |
Bring the PR branch up to date without rebasing.
Catch the es catalogs up to the lock-supply, max-supply, overview, and dashboard error strings added on main, keeping full key parity with English. Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve i18n wiring conflicts by keeping Spanish registered with the new English-fallback merge path. Co-authored-by: Cursor <cursoragent@cursor.com>
Greptile SummaryAdds Spanish as a supported dashboard locale.
Confidence Score: 4/5The PR is not yet safe to merge because Spanish users can still receive the entire Private Channels interface in English. The registered Spanish catalog omits DashboardPrivateChannels, and the recursive merge consequently supplies that namespace from the English source catalog, leaving the previously reported completeness defect unresolved. Files Needing Attention: apps/sdp-web/src/i18n/messages.ts and apps/sdp-web/messages/es/ Important Files Changed
Reviews (4): Last reviewed commit: "feat(web): translate tokenization-engine..." | Re-trigger Greptile |
|
|
||
| const esCatalog = { | ||
| ...es, | ||
| ...esDashboardApprovals, |
There was a problem hiding this comment.
Spanish catalog remains incomplete
Several current English source keys are absent from the registered Spanish catalogs, so the fallback merge displays English text such as “Unnamed member,” “Rows per page,” and policy empty states inside the Spanish UI. Add the missing Spanish leaves so this dedicated translation catalog provides the complete inventory described by the PR.
File Used: apps/sdp-web/src/i18n/README.md (source)
Knowledge Base Used: sdp-web dashboard app
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Bring the PR branch up to date without rebasing.
Translate new shared shell, approvals, and policies strings, and drop obsolete keys removed from English. Co-authored-by: Cursor <cursoragent@cursor.com>
Bring the PR branch up to date without rebasing.
Catch Spanish issuance catalogs up with the Mosaic / Vulcan Forge deploy-step copy added on main. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Closing this in favour of #1047 to avoid duplicate work💁🏻♀️ |
What
Add Spanish language
esalongside Englishenand Frenchfrwith full matching message inventory, keeping institutional crypto terms like Token short and stable for the layout.Related PRs
#685
#1047