Framework-neutral localization

Globalization Core

Keep globalization policy independent from any one UI framework.

Explore source
Parent systemProTranslate
StatusActive
Modules2
RepositoryProTranslate/ProTranslate.Core

Translation lookup, culture switching, fallback, formatting, regions, measurements, and flow direction live in a portable service layer.

  1. 01

    Runtime culture switching

  2. 02

    Fallback chains

  3. 03

    Formatting and plural-ready values

  4. 04

    Region, measurement, and flow direction

From intent
to working system.

01

Catalog

Providers expose keys and localized values.

02

Resolve

Culture and fallback policy choose the best match.

03

Format

Arguments, numbers, dates, and regional rules materialize text.

04

Notify

Applications react to culture and direction changes.

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.

01 · Install
Terminal
dotnet add package ProTranslate.Core
02 · Use · csharp
QuickStart.cs
var translations = new TranslationService(provider);
translations.SetCulture(CultureInfo.GetCultureInfo("pl-PL"));
var title = translations["Shell.Title"];

Use one layer.
Compose the rest.

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.

ProTranslate

Search everything.

Loading the index…

move open esc close

Preparing metadata and full-text search…