Translate Windows RESW resource files with Hyperlocalise

​

Source file

<?xml version="1.0" encoding="utf-8"?>
<root>
    <data name="AppTitle" xml:space="preserve">
        <value>Contoso</value>
    </data>
    <data name="Welcome.Text" xml:space="preserve">
        <value>Welcome back</value>
        <comment>Home screen heading</comment>
    </data>
</root>

​

Configure your files

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

buckets:
    messages:
        files:
            - from: Strings/en-US/Resources.resw
              to: Strings/{{target}}/Resources.resw

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

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Uses the generic XML parser. Each data name identifies its value text, including dotted names such as Welcome.Text.
• Comments, attributes, and metadata elements are preserved when run writes into an existing target whose key set still matches the source.
• If the source gains keys, run uses the source file as the template. Target-only resources and target-only comments are not merged back. This matches other generic XML catalogs, including .resx.
• Use text-only resources. Mixed-content XML is unsupported.
• Changed CDATA values are written as escaped text. See XML for shared behavior.

​

Next steps

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

​

Related formats

• .NET RESX resource
• XML localization