How file detection works
The CLI selects a parser from the file extension. Android XML also requires an Android resource path, Lottie animations are detected from.json content, and
Qt Linguist catalogs are detected from .ts content that has a <TS> root. You do not need to declare a format for each bucket.
Use matching source and target formats unless a workflow explicitly documents a
conversion.
File support describes local translation with run. Platform uploads, TMS entry sync,
and provider-specific file commands have their own contracts; check the relevant
integration guide before syncing.
Before you translate
- Install the CLI and configure provider credentials.
- Choose a format below and map its source and target paths in
i18n.yml. - Preview with
hyperlocalise run --dry-run, then generate withhyperlocalise run. - Review the output diff and run translation checks.
Choose a format
Application resources
Translation exchange
Content and documentation
Subtitles and captions
Are placeholders, plurals, and comments preserved?
Behavior depends on the parser and selected source or target template. For example, ARB keeps message metadata, SRT retains timestamps, and JSONC writeback does not retain comments. gettext.po files treat Unreal Engine rich-text tags as
placeholders and restore the original markup on writeback. Read each format’s
limitations and run translation checks.
Use the ICU and placeholder guide for
validation failures. Review plural variants in the consuming application.

