localization

Apply English and Thai localization to MotoRent UI components and dialogs.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/erymuzuan/motorent --skill localization-erymuzuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization
Source: https://github.com/erymuzuan/motorent/tree/main/.copilot/skills/localization
Command: npx skills add https://github.com/erymuzuan/motorent --skill localization-erymuzuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides localization patterns for MotoRent to support English and Thai using localized base classes and resource files, enabling consistent UI translations and streamlined internationalization.

Core Features & Use Cases

  • Inherit from LocalizedComponentBase/LocalizedDialogBase to apply component-level localization
  • Use shared Localizers (Localizer and CommonLocalizer) to translate UI strings, messages, and controls
  • Structure resources under Resources and implement culture switching for English and Thai

Quick Start

Instantiate localization-enabled pages using the LocalizedComponentBase and LocalizedDialogBase wrappers and ensure Resources paths are configured in Startup.

Frequently Asked Questions about localization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add multi-language support to a Blazor Razor application?

Multi-language support in Blazor is achieved by integrating localized base classes with language resource files. You inherit from LocalizedComponentBase and configure resource paths in Startup to enable consistent UI translations.

What is the best way to structure resource files for English and Thai translations?

Structure resources under a dedicated Resources directory and implement clear key naming conventions. This ensures proper resource loading and enables safe fallbacks for missing translations during English and Thai culture switching.

How do I apply component-level localization to Blazor dialogs?

Component-level localization for dialogs is applied by inheriting from LocalizedDialogBase. This wrapper integrates shared Localizers to translate UI strings, messages, and controls consistently across the application.

Does Blazor localization handle missing translation keys safely?

Blazor localization patterns ensure safe fallbacks for missing translations by relying on structured resource loading and clear key naming conventions. This prevents application crashes when specific localized strings are absent.

Can I use shared localizers for translating UI strings and control messages?

Yes, you can use shared Localizers like CommonLocalizer to translate UI strings, messages, and controls. This approach ensures consistent internationalization across front-end components and dialogs without duplicating translation logic.

Why do I need to configure resource paths in Startup for Blazor internationalization?

Configuring resource paths in Startup is required for proper resource loading during culture switching. It enables the localization framework to locate English and Thai resource files and apply translations across components.