FastGrid 3.3 adds full UI translations in 35 languages. Toolbars, menus, filters, dialogs and the AI prompt bar now appear in your users' language without you translating a single component string. One grid, one codebase, users in Berlin, São Paulo and Tokyo.
When you embed a grid into an international application, rendering millions of rows is rarely the last problem you solve. The next one is language.
A production grid exposes about a thousand UI strings: toolbar tooltips, context menus, filter options, pivot labels, validation messages, print and export dialogs. Each one has to be translated, reviewed and kept in sync with every component upgrade. In practice, that means maintaining an i18n pipeline for text you did not write and re-checking it after every release.
FastGrid 1.0 localized date and number formats, but its UI texts were English only. Version 3.3 closes that gap.
FastGrid 3.3 ships predefined translations of the grid's UI in 35 languages, in addition to default English.
Translations cover the whole user-facing surface of FastGrid and FastSheet:
The AI prompt bar interface is translated, and users can write prompts in any language. The AI replies in the language of the question, not the language of the grid. A controller in Munich can ask in German and get the answer in German, whatever language the grid UI is set to.
FastSheet adds a localized formulas setting: keep English function names, offer localized names, or offer both. Localized names are available in the languages where Excel localizes its functions, so users can keep writing formulas the way they are used to.
FastGrid identifies each language by a two-letter code. Most codes match ISO 639-1. Regional variants use the region code: BR for Brazilian Portuguese, CN and TW for Simplified and Traditional Chinese, JP for Japanese and KR for Korean. Note that UK stands for Ukrainian.
You can also pass a full locale in the xx-YY form. FastGrid first looks for a translation matching the region part YY, then for the language part xx. Standard locales such as pt-BR, zh-TW, ja-JP or uk-UA therefore resolve to the right translation without any mapping on your side.
From build 3.3.2, if no language is set, FastGrid selects one based on the browser's preferred languages.
For production apps, we recommend setting the language explicitly from your application, so the grid always matches the rest of the page. The browser's preferred languages are not always the language a user actually works in, and most multilingual applications choose the language at the application level.
FastGrid keeps all default English texts in Texts.js. The 35 translations ship in FGridText.js as one Languages object, keyed by language code.
Languages are applied in a predictable order: the default texts from Texts.js, then the Base language with your application-wide defaults, then fallback languages listed in the chosen language's D attribute, and finally the chosen language itself. This lets you build a regional variant on top of an existing language and override only the strings that differ.
If your app switches language at runtime, put shared defaults into Base so they are reset correctly on every switch:
{
Languages: {
Base: { Format: { DecimalSeparator: "," } }
}
}
Customers with Partial sources receive the individual translation files. They can build their own FGridText.js with only the languages they need, or distribute translations separately.
Full reference: FastGrid Languages documentation.
Compatibility and scope: FastGrid 3.3 is fully backward compatible, so existing configurations keep working without changes. English remains the default language, and licensing is unchanged. The new translations apply to FastGrid and FastSheet; TreeGrid is not affected by this release.
35 languages in addition to English, from German, French and Spanish to Japanese, Korean, Chinese (Simplified and Traditional), Vietnamese and Brazilian Portuguese. See the full list above.
From build 3.3.2, yes, if no language is set. For production apps we recommend setting the language explicitly so the grid matches the rest of your application.
Yes. FastGrid first looks for the region part, then for the language part, so standard locales resolve to the right translation.
In the language of the question. The grid UI language does not affect it.
No. With Partial sources you get the individual translation files and can include only the languages you need.
Yes. Any text or format can be overridden in your configuration, and you can define a language that is not included.
No. FastGrid 3.3 is fully backward compatible.
See FastGrid in your users' language
The Sets (FastGrid) and Excel (FastSheet) live examples are fully translated and include a language selector in the toolbar.
Open FastGrid →