i18n Senkronizasyon

To keep Turkish and English bash localization messages in sync, you need to diff `lang/tr.sh` and `lang/en.sh` to ensure identical `MSG_` keys, counts, and category prefixes. This prevents missing labels and formatting mismatches during execution.

Validating printf format strings across multilingual bash scripts involves verifying that `%s` and `%d` format specifiers match for every corresponding `MSG_` variable. This ensures runtime placeholders stay compatible across both language files.

Missing labels occur when new translation strings cause message definitions to drift out of sync. Running a message count validation ensures both `lang/tr.sh` and `lang/en.sh` define the exact same total number of `MSG_` entries.

To check bash syntax before trusting UI translation updates, run `bash -n` against both `lang/tr.sh` and `lang/en.sh`. This validates the shell syntax without executing the scripts, ensuring your localization updates are safe.

Yes, message synchronization verifies category consistency by checking that message prefixes like `MSG_HEADER_*` and `MSG_WARN_*` align perfectly across both languages. This ensures your translation categories match correctly.

You need to run a diff-based key parity check for bash localization whenever new UI strings are added or edited. This detects any `MSG_` variables present in one file but missing in the other, maintaining translation consistency.