@iyulab/flex-table 0.35.0 → 0.37.0

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # Changelog
 
+## [0.37.0] - 2026-09-20
+
+### Fixed
+
+- **The column menu and the cell context menu stayed in English on a translated page.** 0.36.0 moved
+  the table's chrome text into a locale namespace, but the menus added in 0.35.0 were not part of
+  that move: their items, and the accessible name of the column-menu button, were written inline. On
+  a Korean page the same button therefore announced one language in its `title` and another in its
+  `aria-label`, and a screen-reader user heard English item names in the middle of a translated
+  grid — with no way to correct it, since the strings had no keys to register over. Every one of
+  those strings now goes through the namespace, including the cell context menu, the two menu
+  accessible names and the import drop target. Three keys name a column and carry a `{header}`
+  placeholder, so word order stays the translator's choice instead of being fixed by concatenation.
+  The built-in English wording is unchanged.
+
+### Documentation
+
+- **The README no longer lists every message key by hand.** That paragraph had gone stale once
+  already, and a hand-copied list is the only part of this documentation that can: the exported
+  `FlexTableMessageKey` cannot. It now names the groups and points at the type, which your editor
+  completes and the compiler checks.
+
+### Added
+
+- **The boolean filter's two options are translatable** (`booleanTrue` / `booleanFalse`). They read
+  `True` and `False` in every locale before this; the check and cross glyphs stay in the template,
+  since a symbol means the same thing in every language.
+- **`t()` and the exported namespace now interpolate.** `FlexTableMessageKey` gains the menu keys
+  above; registering a partial table still merges, so existing registrations keep working untouched.
+
+## [0.36.0] - 2026-09-17
+
+### Added
+
+- **The table's own chrome text now goes through a locale namespace.** The filter menus, the
+  find-and-replace panel, the column menu and the empty-state message were written in English in the
+  source, so an application translated into another language showed thirty-one English strings in
+  the middle of its own UI — "Contains", "Starts with", "Match case", "Replace all" and the rest.
+  `flexTableLocale` is exported for consumers to register further languages or reword the built-in
+  ones:
+
+  ```ts
+  import { flexTableLocale } from '@iyulab/flex-table';
+  flexTableLocale.register('ja', { contains: '含む', startsWith: '前方一致' });
+  ```
+
+  English and Korean ship with the package; other languages are added the same way. The filter
+  operators `AND` and `OR`, and the glyphs standing in for icons, are deliberately left alone —
+  they read the same in every language and translating them makes them harder to recognise.
+
+### Changed
+
+- The package compiles against `ESNext` rather than `ES2021`, matching every sibling package in the
+  same family.
 ## [0.35.0] - 2026-09-15
 
 ### Changed

package/README.md

@@ -409,6 +409,57 @@ package dependency; CSS custom properties are resolved at render time, not impor
 | ArrowUp / ArrowDown / Home / End (column menu) | Move between menu items |
 | Escape (column menu) | Close the menu and return focus to its button |
 
+## Localization
+
+The text the table draws itself — filter menus, the find-and-replace panel, the column menu, the
+empty-state message — resolves through a locale namespace. English and Korean ship with the package
+and follow whatever locale `@iyulab/components` has active:
+
+```ts
+import { Locale } from '@iyulab/components';
+
+Locale.set('ko');   // the table's own chrome follows
+```
+
+Register another language, or reword the built-in strings, through the exported namespace. Partial
+tables are merged, so you only pass the keys you want to change:
+
+```ts
+import { flexTableLocale, type FlexTableMessageKey } from '@iyulab/flex-table';
+
+flexTableLocale.register('ja', {
+  contains: '含む',
+  startsWith: '前方一致',
+  matchCase: '大文字と小文字を区別',
+});
+
+flexTableLocale.register('en', { replaceAll: 'Replace everything' });  // reword one string
+```
+
+The keys are grouped by where they appear: the column header and its menu, the items inside that
+menu, the cell context menu, cell comments, the filter panel, find-and-replace, and the import drop
+target. **`FlexTableMessageKey` is the list** — it is exported, so your editor completes it and a
+misspelled key is a type error rather than a string that silently falls back to its own name.
+
+> This paragraph used to enumerate every key by hand. It went stale once, and a hand-copied list is
+> the only thing here that can: the type cannot. If you want the full set, hover `FlexTableMessageKey`
+> or open `src/locale.ts`.
+
+Three of those keys name a column, and word order differs between languages, so they carry a
+`{header}` placeholder rather than being assembled by concatenation:
+
+```ts
+flexTableLocale.register('ja', {
+  columnMenuFor: '{header} の列メニュー',  // the column menu button's accessible name
+  columnMenuRegion: '{header} 列',                    // the open menu's accessible name
+  showColumn: '{header} を表示',                  // "show this hidden neighbour again"
+});
+```
+
+The filter operators `AND` and `OR` are not in the table, and neither are the glyphs that stand in
+for icons. They read the same in every language, and translating them makes them harder to
+recognise rather than easier.
+
 ## Accessibility
 
 The baseline is **WCAG 2.2**. The table lists what this package **measures in tests** — it is not a