# VidSEO French translation assets

English remains the source language. `fr-translations.json` contains the maintained Canadian French translations shared by `fr_CA` and `fr_FR`; WordPress core and the Freemius SDK retain their own language packs.

`vidseo-fr_CA-vidseo__editor.json` and `vidseo-fr_FR-vidseo__editor.json` are Jed catalogues loaded by `wp_set_script_translations('vidseo__editor', 'vidseo', VIDSEO_PLUGIN_ROOT . 'languages')`. The corresponding `vidseo-fr_CA-vidseo__block_editor.json` and `vidseo-fr_FR-vidseo__block_editor.json` catalogues cover the Gutenberg block and are attached to `vidseo__block_editor`. PHP gettext uses the matching `.mo` files; editable `.po` files and the source `.pot` are included.

From the isolated plugin directory in PowerShell:

```powershell
& .\scripts\extract-translations.ps1
python .\scripts\build-translations.py --check
```

The extraction command uses the existing local WordPress CLI container solely to inspect source files. The builder has no network dependency, validates interpolation placeholders, compiles MO files compatible with both tested WordPress runtimes, and derives editor and block messages directly from the final JavaScript source. Missing current editor, block or active PHP translations fail generation; `translation-coverage.json` lists any untranslated inactive legacy strings explicitly.

`tests/data-i18n.php` verifies gettext, plurals, user locale isolation and WordPress's actual script translation loader on WordPress 7.1/PHP 8.3 and WordPress 5.6.2/PHP 7.4. It does not substitute for mobile, RTL or keyboard visual checks. Final WordPress fixture executions are serialized by the root agent because some qualification suites change global fixture options temporarily.