Streamlined localization

Batch imports (via Site Initializer or the Batch Engine API) can now use a single wildcard placeholder to populate a localized field across every active locale, instead of requiring every language’s translation to be hardcoded individually into the batch file. A localized value can be expressed once, referencing a language key, and resolved automatically into each active locale’s translation at import time.

Key Benefits:

Cuts the manual effort of preparing translated batch files, since one language key reference replaces a full per-locale map
Reduces the risk of incomplete translations shipping to production, since locales are resolved consistently at import time rather than relying on someone manually adding each one
Works consistently whether the import runs directly through the Batch Engine API or through a Site Initializer, so implementers get the same behavior either way
Re-importing an already-resolved batch file is safe: once real strings are persisted, a second import passes through without re-processing placeholders

Status: Generally Available (aka OOTB)