Blazor Globalization Overview
Internationalization (I18N) is the process of making an app support different languages and regions. In the Telerik UI for Blazor suite, this will consist of the following features:
Localization (L10N) - the ability to show texts and UI elements in the components in different languages (such as button texts and ARIA attributes).
Globalization (G11N) - the ability to react to the chosen culture where format strings are involved (such as number and date formats).
Right-to-Left Support - the ability to render the components in a right-to-left direction instead of the default left-to-right direction. This feature will become available in an upcoming release.
Date And Number Formats
The Telerik Components use the current thread culture to render the appropriate culture-specific format for dates, numbers and currency:
Calendar - the names of the months and days of the week are taken from the current culture, and the
FirstDayOfWeekof the culture is honored when ordering the days of the week. The Calendar uses theShortestDayNamesarray to get the short names for the days of the week and it expects them in the default order coming from the framework - Sunday to Saturday.Chart - the Label Format Strings and Tooltip are culture aware (e.g., currency, dates). You can find examples in the How to localize numeric labels in the Chart knowledge base article.
DateInput - the
Formatis culture-specific and the same format may produce different results depending on the culture. You can find more information and examples in the Supported Date Formats article.DatePicker - the
Formatis culture-specific and the same format may produce different results depending on the culture. You can find more information and examples in the Supported Date Formats article.DateRangePicker - the
Formatis culture-specific and the same format may produce different results depending on the culture. You can find more information and examples in the Supported Date Formats article.DateTimePicker - the
Formatis culture-specific and the same format may produce different results depending on the culture. You can find more information and examples in the Supported Date Formats article.Grid - the various inputs and editors are Telerik components and respond to the culture. Custom code and format strings in the templates will also default to using the current culture unless you explicitly use a certain culture in them.
NumericTextBox - the
Format(for example, currency), decimal separator, group separator and default number ofDecimalsare taken from the current culture.RangeSlider - The labels on the large ticks are formatted according to the current culture and its default decimals.
Scheduler - Date formats are taken from the culture, in the week view the first day of the week is also taken from the culture even if it does not match the
Date. The various inputs and editors in the edit form are Telerik components and respond to the culture.Slider - The labels on the large ticks are formatted according to the current culture and its default decimals.
TimePicker - the
Formatis culture-specific and the same format may produce different results depending on the culture. You can find more information and examples in the Supported Date Formats article.TreeList - the various inputs and editors are Telerik components and respond to the culture. Custom code and format strings in the templates will also default to using the current culture unless you explicitly use a certain culture in them.