Framework-neutral localization
Globalization Core
Keep globalization policy independent from any one UI framework.
Explore source ↗Capability
Translation lookup, culture switching, fallback, formatting, regions, measurements, and flow direction live in a portable service layer.
- 01
Runtime culture switching
- 02
Fallback chains
- 03
Formatting and plural-ready values
- 04
Region, measurement, and flow direction
How it composes
From intent
to working system.
Catalog
Providers expose keys and localized values.
Resolve
Culture and fallback policy choose the best match.
Format
Arguments, numbers, dates, and regional rules materialize text.
Notify
Applications react to culture and direction changes.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package ProTranslate.Core<PackageReference Include="ProTranslate.Abstractions" Version="VERSION" /><PackageVersion Include="ProTranslate.Abstractions" Version="VERSION" />var translations = new TranslationService(provider);translations.SetCulture(CultureInfo.GetCultureInfo("pl-PL"));
var title = translations["Shell.Title"];Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.