Newsroom OS — gettext files (text domain: newsroom-ai-assistant)

Shipped in this folder (regenerate with `node tools/build-po.mjs` after editing `tools/machine-translations.json`):

- `newsroom-ai-assistant.pot` — template of extracted UI strings
- `newsroom-ai-assistant-el.po` / `.mo` — Greek (locale `el`)
- `newsroom-ai-assistant-en_US.po` / `.mo` — English (msgstr equals msgid)
- `newsroom-ai-assistant-de_DE.po` / `.mo` — German
- `newsroom-ai-assistant-es_ES.po` / `.mo` — Spanish

Source of truth for el/de/es strings: `tools/machine-translations.json` (built with `node tools/fetch-translations.mjs` using the public gtx translate endpoint; review in Poedit if needed).

**JavaScript (`newsai-script`)** — shipped JSON files in this folder:

- `newsroom-ai-assistant-el-newsai-script.json`
- `newsroom-ai-assistant-de_DE-newsai-script.json`
- `newsroom-ai-assistant-es_ES-newsai-script.json`
- `newsroom-ai-assistant-en_US-newsai-script.json`

They are wired via the `load_script_translation_file` filter (`newsai_resolve_script_translation_file()` in the main plugin file) so WordPress finds them by name instead of the default md5-of-relative-path. Regenerate with `node tools/build-script-json.mjs` after editing strings in `assets/script.js`. WP-CLI alternative: `wp i18n make-json languages --no-purge`.

Official UI language codes in Settings: el, en, de, es (see `newsai_supported_languages()` in the main plugin file).

Or use Loco Translate and point it at this `/languages` directory.
