feat: Extract all UI strings to resources #278
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Extract all UI strings to resources
Description
This PR extracts all remaining hardcoded user-facing strings to
Localizable.stringsfor localization support. The changes follow the existing key naming conventions (prefix__keyName) and maintain alphabetical ordering within sections.Key changes:
tTodo()calls with propert()calls using new localization keysbitkit-android) where applicable for Transifex sync compatibilitycommon__- Shared UI labels (coming_soon, error, on, off, show_all, etc.)other__- Miscellaneous strings (shop categories, LNURL errors, scanner errors, gift screens)wallet__- Wallet-specific strings (transfer labels, receive/send toasts, fee labels)settings__- Settings screen strings (address viewer, language change, logs)security__- Security-related strings (recovery errors, wipe failures)Excluded from localization (intentionally):
ChannelOrders,DevSettingsView,BlocktankRegtestView, etc.)Validation:
validate-translations.jspasses with 0 errors, 0 warningsLinked Issues/Tasks
Screenshot / Video
N/A - No visual changes, only string extraction for localization infrastructure.