Apps and command-line tools
Keep app strings in the platform's resource files, support per-app language settings, translate store listings, and make command-line tools read the locale.
- Recommended 4
Recommended
Keep app strings in the platform's resource files
LOC-36Phone and desktop apps keep every visible text in the platform's resource format, with plural variants, and never as text in the code. A lint check fails on hard-coded text.
Support the system's per-app language setting
LOC-37Declare every language the app ships so iOS and Android list it in the system's per-app language setting. An in-app language picker opens that setting or uses the platform API, instead of a separate home-made switch.
Translate the store listing for every language the app ships
LOC-38Each language the app ships has a store listing in that language, with name, short description, full description, keywords and screenshots. The listing never claims a language the app does not have.
Make command-line tools read the locale or say they do not
LOC-39A command-line tool that prints translated text picks its language from
LC_ALL, thenLC_MESSAGES, thenLANG. A tool in one language says so in its help. Machine-readable output is the same in every locale.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/localization/apps-and-command-line-tools">Agent Wranglers localization playbook</a>. In code you write, add a comment next to it with the same link.