Localisation

messages: {
  ...GRID_MESSAGES['fr'],
  empty:     'Aucun employé ne correspond',
  gridLabel: 'Répertoire du personnel',
}

config = {
  dir:      'rtl',
  messages: { ...GRID_MESSAGES['ar'], gridLabel: 'دليل الموظفين' },
};

messages: { gridLabel: 'Employee directory' }

Twelve languages ship with the library

GRID_MESSAGES is exported alongside the grid and carries en, ar, fr, de, es, pt, fa, ur, tr, zh, ja and ru. Localising is an import, not a translation project:

import { GRID_MESSAGES, RTL_LOCALES, GridDirectionService } from '@gridcraft/angular';

const locale = inject(GridDirectionService);

locale.setMessages(GRID_MESSAGES[lang] ?? GRID_MESSAGES['en']);
locale.setDir(RTL_LOCALES.has(lang) ? 'rtl' : 'ltr');

en and ar are complete, at eighty-three strings each. The other ten carry thirteen — the overlays, the pager, the retry button — and anything they omit falls back to English key by key, so a partial set is a working set rather than a half-broken one. The first two examples above are those two cases side by side.

Overriding a shipped set

Spread it, then change what your product words differently. What you do not mention keeps the shipped translation:

const FR = {
  ...GRID_MESSAGES['fr'],
  empty:     'Aucun employé ne correspond',
  gridLabel: 'Répertoire du personnel',
};

gridLabel is the reason to do this per screen rather than per language: it is the grid's own accessible name, so it should say what this grid holds, not what every grid in the app holds. The French example sets exactly those two on top of the bundled set.

Column names are yours, not the grid's

messages covers the strings the grid produces. The column headers are strings you wrote, declared on the columns, so they go through whatever i18n your app already uses — $localize, a JSON bundle, or your translation service. Each grid above declares its own; a real language switch has to move both halves at once.

The strings nobody sees

A translated grid that still announces "sorted ascending" in English is only half translated, and it is the half that fails the readers who depend on it most. These keys never appear on screen, so they are the ones that get forgotten:

• gridLabel — the grid's own accessible name, announced on entering it.
• selectAllRows, selectRow — the checkbox labels.
• filterFor, editorFor, rowDetailsToggle — the labels on the filter inputs, the inline editors and the row-detail toggle.
• announceSortAsc, announceSortDesc, announceSortCleared, announceResults, announceLoaded — what is read out after an action.

See Accessibility for what each announcement is used for.

Placeholders

A few strings are templates rather than fixed text. Keep the placeholder in your translation and the grid fills it in. Drop one and the value it carried is simply gone from the sentence:

• {col} — a column's name. filterFor, editorFor, announceSortAsc, announceSortDesc, announceEditDone, validationRequired.
• {n} — a count. announceResults, announceLoaded, announceSelectedAll, quickFilterResults.
• {page} and {pages} — the current page and the total, in announcePage.
• {total} — a second count beside {n}, in announceLoadedMore.
• {min} and {max} — the bound that was broken, in validationMin and validationMax.

They can sit anywhere in the string, which is what makes a language with a different word order translatable rather than merely re-worded. Every other message is plain text — pageOf included: the pager prints the two numbers around it, so a translation is the word alone.

Three places to set them

The same object is accepted at three levels, and they combine key by key — a grid that overrides one string keeps every other one from the level above.

• App-wide, once — provideGridDefaults({ messages }) in your application config. Every grid inherits it, including grids you add later.
• At runtime — GridDirectionService.setMessages(). Call it when the reader changes language and every grid on screen updates; nothing is re-created. patchMessages() merges a few keys instead of replacing the set.
• Per grid — config.messages, which wins over both. Use it for the strings that belong to one screen, such as gridLabel. Each grid on this page uses it, which is why three languages sit on one screen at once.

Direction is a separate switch

Translating the strings does not move the layout, and moving the layout does not translate the strings — deliberately independent, because plenty of apps need one without the other. config.dir is per grid, so the Arabic example above reads right to left while the rest of this page, and the two grids around it, stay left to right. See RTL Support for what direction changes on its own.