Translating the UI & help
On first run the packaged app seeds editable copies of the UI strings and the help pages into the per-user data dir; edit them there and relaunch. The bundled copies stay as a fallback, so a missing or incomplete file never loses the built-in text. After an app upgrade, delete the dir to re-seed the new version.
| OS | UI strings (i18n) | Help pages |
|---|---|---|
| Windows | %APPDATA%\Phonalyser\i18n\ | %APPDATA%\Phonalyser\help\ |
| macOS | ~/Library/Application Support/Phonalyser/i18n/ | ~/Library/Application Support/Phonalyser/help/ |
| Linux | $XDG_CONFIG_HOME/Phonalyser/i18n | $XDG_CONFIG_HOME/Phonalyser/help |
UI strings are messages_<lang>.properties (e.g.
messages_de.properties); help pages live under
help/<lang>/.
Contributing a language. A new translation is a
copy of
messages.properties (and, optionally, the
help/<lang>/ pages) with the values translated —
pull requests welcome on
GitHub.