What problem does it solve?
ABP localization configuration is hard to get right when you need multi-language UI text, localized permissions, and consistent culture fallback behavior across an application.
Core Features & Use Cases
- Localization Resources & JSON files: Define translation groups and store culture-specific strings in embedded JSON resource files.
- Culture fallback & virtual file system: Ensure ABP can serve the right translations via assembly-embedded resources with automatic fallback to the default culture.
- L[] helper and IStringLocalizer usage: Retrieve localized strings in application/services/controllers/Razor views, including nested keys and array-based structures.
- Best practices for large modules: Use key prefixes, split large JSON resources per feature, and include required
culture metadata in every JSON file.
Quick Start
Create a localization resource class, register the resource with ABP localization options using embedded virtual JSON files, and then retrieve strings using L["YourKey"] in your services or views.