# Translation catalogues — 3.4.2

Bundled MO and flat JavaScript catalogues cover en_US, en_GB, zh_CN, zh_TW, es_ES, es_MX, fr_FR and de_DE. New feature copy can be completed using the background interface translation tasks. Selected Vietnamese, Korean, Japanese, Brazilian Portuguese, Filipino and Arabic interfaces become selectable after the complete source catalogue has been generated; Arabic uses RTL styling.

`source-ui.json` lists interface source phrases; WordPress script handles receive Jed JSON via `pre_load_script_translations`, so no script-hash filename convention is required. Updated POT reflects the new source phrases. Source text and canonical option names are never replaced for checkout validation; translated display names are saved separately in customer order snapshots.

Machine translation is not a food-allergen guarantee. The merchant glossary fixes exact dish/ingredient terminology, and manual edits are protected from automatic overwrites. API-generated customer menus live in the restaurant database, not this ZIP. The package does not contain access keys or actual merchant menu translations.

Current category and marketing copy is included in source-ui.json and the POT. Run the existing interface translation workflow to translate these new phrases; ungenerated phrases fall back to English.