Translate Apple String Catalogs with Hyperlocalise

​

Source file

{
    "sourceLanguage": "en-US",
    "strings": {
        "welcome": {
            "localizations": {
                "en-US": {
                    "stringUnit": { "state": "translated", "value": "Welcome" }
                }
            }
        }
    },
    "version": "1.0"
}

​

Configure your files

locales:
    source: en-US
    targets:
        - es-ES

buckets:
    messages:
        files:
            - from: locales/en-US/messages.xcstrings
              to: locales/{{target}}/messages.xcstrings

llm:
    profiles:
        default:
            provider: openai
            model: gpt-5.2

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Reads source text from the source-language localization. Simple entries without one fall back to the catalog key.
• Plural, device, and substitution variants use stable :: paths. Variants require a source localization.
• Writes translations under localizations[targetLocale], preserving catalog metadata and other localizations. JSON whitespace and ordering are normalized.
• The example writes a separate catalog per target locale. The catalog format itself can contain multiple locales.

​

Next steps

• Check translations before committing generated files.
• Local translation workflow explains repeat runs.
• Browse all file formats.

​

Related formats

• Apple .strings
• Apple .stringsdict
• JSON localization