From 4f2c2b773a8aaf3b838d8fc43a9de8408239a35c Mon Sep 17 00:00:00 2001 From: Jenna Vassar Date: Tue, 9 Jun 2026 15:07:47 -0700 Subject: [PATCH] Move custom recovery passphrase strings to FOSS for iOS parity Add the pro_screen_recovery_key_mode_* and a11y_recovery_key_* strings to the securebackup module's temporary.xml so they flow through Localazy for translation, matching element-x-ios#5684, and bump the enterprise submodule to the commit that references these FOSS strings and drops its own copy. Co-Authored-By: Claude Opus 4.8 (1M context) --- enterprise | 2 +- .../impl/src/main/res/values/temporary.xml | 37 +++++++++++++++++++ 2 files changed, 38 insertions(+), 1 deletion(-) create mode 100644 features/securebackup/impl/src/main/res/values/temporary.xml diff --git a/enterprise b/enterprise index 6781da90aa..b5faab58b9 160000 --- a/enterprise +++ b/enterprise @@ -1 +1 @@ -Subproject commit 6781da90aae61cf77dcdbc543e18d76411d578b4 +Subproject commit b5faab58b90f46a7c3000f216da91a558b65980e diff --git a/features/securebackup/impl/src/main/res/values/temporary.xml b/features/securebackup/impl/src/main/res/values/temporary.xml new file mode 100644 index 0000000000..272343aa99 --- /dev/null +++ b/features/securebackup/impl/src/main/res/values/temporary.xml @@ -0,0 +1,37 @@ + + + Enter a recovery key + Choose a recovery key that you can memorize. + Confirm your recovery key + Enter your recovery key again. + Minimum %1$s characters + Finish setup + Your backup is now fully set up + You can use your recovery key to confirm new devices or restore your encrypted chats if you lose access to all your devices. + To change your recovery key, go to Settings → Encryption → Backup + Strength + Garbage + Weak + Moderate + Okay + Strong + Very Strong + Super Strong + Ideal + Cracking would take roughly milliseconds. + Cracking would take roughly minutes to months. + Cracking would take roughly years. + Cracking would take roughly hundreds of years. + Cracking would take roughly billions of years. + Cracking would take roughly trillions of years. + Cracking would take roughly quadrillions of years. + Cracking would take roughly quintillions of years. + The recovery key you entered doesn\'t match + Passphrase strength: %1$s + Loading recovery key requirements +