Translation files (.pot/.po/.mo, and the .json ones for the JS) live here.

The interface is written in English; every string goes through the `aipb` text domain, on both
sides: `__()` and friends in PHP, `wp.i18n.__()` in the JS (see the wrapper at the top of
assets/studio.js and assets/brand.js).

Regenerating the catalogue
--------------------------

    php bin/make-pot.php

That script has no dependencies and reads the sources directly — it is the one to use when WP-CLI
is not installed on the machine building the zip. With WP-CLI available, this is equivalent:

    wp i18n make-pot . languages/aipb.pot

Adding a language
-----------------

Translate aipb.pot into languages/aipb-<locale>.po (e.g. aipb-it_IT.po), then:

    wp i18n make-mo languages/                # the .mo that PHP reads
    wp i18n make-json languages/ --no-purge   # the .json files the Studio's JS reads

The .json files are what `wp_set_script_translations()` looks for: without them PHP is translated
and the Studio stays in English.
