Languages and ICU compatibility

Check the authenticated provider catalog before choosing a connection for your branch. Its reviewed mappings are versioned and may cover fewer locales than a provider’s whole product. A language variant is never silently reduced to a generic language.

Content	OpenAI / Gemini	Google Translate / DeepL
Plain text	Supported	Supported for an exact mapped source/target pair
Simple named ICU arguments	Supported	Protected placeholders; identities and counts checked on return
Cardinal/ordinal plural, select	Validated against the existing contract	Rejected with an explanation
Offset, exact-number cases, nested expressions	Structure checked; target plural categories validated	Rejected
Rich markup or advanced date/number ICU formatting	Outside Localisync’s current ICU contract	Outside scope

For model providers, argument names/types, select branches, offsets and exact-number conditions must remain compatible. Target-language cardinal/ordinal categories and the required other branch are validated. Unsupported expressions are never flattened into Plain text.

Native translation adapters protect supported simple ICU arguments with temporary markers. Missing, duplicated or altered markers invalidate the result. Plain text is not silently interpreted as ICU.

Existing limits apply to every saved suggestion: 16 KiB UTF-8 per value, 32 parameters, 10 nested expressions and 1,000 AST nodes. Empty results, duplicate IDs, unknown IDs, incomplete responses and invalid JSON are rejected. Manual proposal edits pass the same validators.

The catalog records exact provider identifiers. Model access and native language availability can still differ by account or change at the provider; a failed request is shown instead of silently substituting a different model or language.

Read ICU messages for the underlying content contract and the workflow for review and Apply.