Skip to content

docs: internationalization (i18n)#238

Open
marcelo-maciel wants to merge 1 commit into
fullstackhero:mainfrom
marcelo-maciel:docs/i18n
Open

docs: internationalization (i18n)#238
marcelo-maciel wants to merge 1 commit into
fullstackhero:mainfrom
marcelo-maciel:docs/i18n

Conversation

@marcelo-maciel

Copy link
Copy Markdown
Contributor

Documents the internationalization (i18n) feature and adds the changelog entry. Companion to the code PR fullstackhero/dotnet-starter-kit#1344.

  • New cross-cutting concerns page covering the request culture resolution chain, resource catalogs (SharedResources plus per-module {Module}Resources), localized ProblemDetails and FluentValidation messages, the User.Locale field and fallback, and the front-end react-i18next setup with enforced en-US / pt-BR key parity.
  • Links the new page from the cross-cutting concerns index.
  • Adds a changelog entry for the feature.

Add a cross-cutting-concerns page covering end-to-end localization:
backend IStringLocalizer with neutral-culture resx and RequestLocalization,
the five-step culture-resolution chain, per-user User.Locale on the JWT
locale claim, and both React apps on react-i18next with a language switcher.
Includes an "adding a language" guide and a changelog entry.
@iammukeshm

Copy link
Copy Markdown
Member

Reviewed - thorough page, and the culture-resolution chain + neutral-resx-name gotchas are exactly the right level of detail. Holding until upstream #1344 merges (still open). When it does: rebase over main's em-dash -> hyphen conversion, re-date the changelog section to the actual merge date, and double-check the final shipped config keys (LocalizationOptions:DefaultCulture, SupportedCultures, defaultLanguage) against the merged code before we publish.

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