Five UI stacks
XAML Framework Adapters
Share translation policy while keeping framework-native markup.
Explore source ↗Capability
Avalonia, WPF, WinUI, Uno Platform, and .NET MAUI packages map dynamic translation and culture state into each framework’s binding and XAML model.
- 01
Avalonia and WPF
- 02
WinUI and Uno Platform
- 03
.NET MAUI
- 04
Live culture and flow-direction updates
How it composes
From intent
to working system.
Core
One service resolves cultures, keys, and formatted values.
Adapter
Each package maps notifications into its property and binding system.
Markup
Framework-native markup extensions or helpers keep XAML concise.
View
Visible content and flow direction update without rebuilding the application.
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.Avalonia<PackageReference Include="ProTranslate.Avalonia" Version="VERSION" /><PackageVersion Include="ProTranslate.Avalonia" Version="VERSION" /><TextBlock Text="{pt:Translate 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.