Translate XML localization files with Hyperlocalise

​

Source file

<?xml version="1.0" encoding="UTF-8"?>
<messages xml:lang="en-US">
    <message key="home.title">Welcome</message>
</messages>

​

Configure your files

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

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

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

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Text-only leaves use key, id, or name attributes as keys. Unkeyed nested leaves use dotted element paths.
• Comments, attributes, and metadata elements are retained. Matching root locale attributes are updated for the target locale.
• Mixed-content values and Android, XLIFF, or plist roots are rejected by this parser. Use their dedicated formats.
• CDATA is readable, but changed values are written as escaped XML text. Whitespace inside values may change with translated text.

​

Next steps

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

​

Related formats

• Android XML string resources
• XLIFF translation
• .NET RESX resource