fix(locales): correct placeholder syntax in Turkish translations for liquidation and bonus messages

[PatrykLucka]

Description

Turkish copy used %{{variable}} so a literal percent could sit before the interpolated value. i18n-js (used by react-native-i18n) treats % followed by { as the start of a %{name} placeholder, so %{{...}} was parsed as one invalid token and users saw messages like [missing %{{apy}} value] instead of the real value.

All affected tr.json strings were updated to %%{variable}: a literal % plus the supported %{variable} interpolation, preserving “percent before number” wording while matching the same interpolation keys the app already passes (apy, percentage, fee, distance, etc.). No application code changes.

Changelog

CHANGELOG entry: Fixed Turkish strings that showed broken i18n placeholders when a percent sign appeared before an interpolated value.

Related issues

Fixes:

Manual testing steps

Feature: Turkish locale i18n placeholders

  Scenario: APY and bonus copy interpolate with a leading percent
    Given the app language is set to Türkçe (tr)
    And the user opens a surface that shows Money APY label, MetaMask Card APY bullet, earn/mUSD bonus copy, bridge fee disclaimer, swap slippage errors, or perps liquidation distance strings

    When those screens render

    Then no string should contain a substring like "[missing" or "value]"
    And percent-prefixed values should show as "%" immediately followed by the numeric or formatted value (e.g. "%4" for APY), not a raw placeholder token

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Low Risk
Low risk translation-only change that adjusts placeholder formatting; main risk is minor copy/interpolation regressions if any key names are mismatched.

Overview
Fixes broken Turkish (tr.json) interpolations where a leading percent sign caused i18n placeholders like %{{percentage}} to be parsed incorrectly.

Updates affected strings (perps liquidation/fees, swap/bridge fee and slippage messages, earn/mUSD bonus and APY/cashback labels) to use %%{...} so the UI shows a literal % followed by the interpolated value.

^{Reviewed by Cursor Bugbot for commit 4a6b57e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 49cb281. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud