i18n: extract support page strings#17694
Merged
Merged
Conversation
Create page-community-support.json namespace and replace hardcoded strings with getTranslations() calls. Register namespace in translations.ts. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
content 🖋️
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
…T03-22-37-crowdin-translations
Fix 10 critical issues across 7 languages: - ar: remove extraneous prefix, fix ecosystem term - de: fix du/Sie register inconsistency - hi: standardize Ethereum transliteration - mr: fix brand misspelling, fix token mistranslation - pt-br: fix broken double verb in bridge-tokens - sw: remove extraneous "namba" in layer 2 - ur: fix transliteration typo in meta-description Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
…T04-59-13-crowdin-translations
Sanitizer: 58 files cleaned (frontmatter quoting, inline block components, blank line cleanup). Review fixes across 8 languages: - ja, ko: unescape bold markers on ethereum.org link - ko: fix pooled/liquid staking mistranslation - de: fix du/Sie register in scams contentPreview - es: fix tu/usted register in scams contentPreview - es: fix apostar -> hacer staking de - it: remove duplicate heading in faq - bn: standardize Ethereum transliteration - cs: clean garbled dual-term staking heading Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
…-crowdin-translations
…-crowdin-translations
warnExposedMdxTags now treats any PascalCase tag as a safe MDX component instead of maintaining a hardcoded list. Eliminates 384 false-positive DocLink warnings. Also expands safe HTML element list with b, mark, cite, and other standard tags. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
…13-crowdin-translations i18n: automated translations - support page MD (all languages)
…37-crowdin-translations i18n: automated translations - support page JSON (all languages)
wackerow
requested review from
minimalsm,
pettinarip and
wackerow
as code owners
wackerow
approved these changes
Mar 4, 2026
Contributor
|
tracking - Keep them as hardcoded English strings. |
Contributor
|
as always though im looking at english only |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extends branch
Summary
page-community-support.jsonnamespace with 39 translation keys for the/community/support/pagepage.tsxwithgetTranslations()calls usingnext-intl/community/support/prefix intranslations.tsnamespace mapping (before the/community/catch-all)TODO
Question for @konopkja
The
customEventOptionsvalues (eventCategory,eventAction,eventName) are currently hardcoded English strings used as analytics identifiers. Should these remain as-is (since they're tracking keys, not user-facing text), or would you prefer them extracted to the i18n namespace as well?Test plan
generateMetadatapulls title/description from namespace/community/support/resolves topage-community-supportnamespace🤖 Generated with Claude Code