Translate Java .properties files with Hyperlocalise

​

Source file

# Home screen
home.title=Welcome
home.greeting=Hello, {name}!

​

Configure your files

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

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

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

​

Translate

hyperlocalise run --dry-run
hyperlocalise run

​

Behavior and limitations

• Supports =, :, or unescaped whitespace separators, escaped characters, Unicode escapes, and continued lines.
• Leading comments provide context. Writeback preserves keys, ordering, comments, separators, and spacing.
• Translated values become single-line escaped strings. New keys are appended in sorted order.
• Duplicate keys, malformed Unicode escapes, invalid UTF-8, and dangling continuations are rejected.

​

Next steps

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

​

Related formats

• YAML localization
• gettext PO
• .NET RESX resource