Crowdin translations update #16910
Crowdin translations update #16910
Conversation
WalkthroughThis pull request updates the localization files used throughout the application in multiple languages. The changes include additions of new translation keys and modifications of existing ones. Updates affect instructions related to destination tags (also referenced as memos), backup processes, address confirmation steps, and error or warning messages. Several translation files (e.g., cs, de, en, es, fr, it, ja, nl, pt, tr, zh) have been modified to clarify the wording of notifications and improve the consistency of text strings across the application. In addition, the support messages file ( Possibly related PRs
Suggested reviewers
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (11)
packages/suite-data/files/translations/en.json (2)
171-171: Simplify Copy Notification MessageThe translation key
TR_TOAST_COPY_TO_CLIPBOARDhas been updated from "Copied to clipboard" to a shorter "Copied". Please double-check that this revised message remains clear for users and that similar changes have been consistently applied across other languages.
681-681: Add New Entropy Check Failure MessageA new translation key
TR_DEVICE_COMPROMISED_ENTROPY_CHECK_TEXThas been added with the message "Security check (entropy verification) failed." This aligns with similar entries in other language files and improves clarity in security-related notifications. Verify that the phrasing correctly conveys the intended meaning in the overall user interface context.packages/suite-data/files/translations/tr.json (1)
359-364: Backup Recovery and Success Translations Updated
The keys"TR_BACKUP_RECOVERY_SEED"and"TR_BACKUP_SUCCESSFUL"have been updated to “Cüzdan yedekleme” and “Cüzdan yedekleme başarılı” respectively. Confirm that these phrases clearly convey the concept of a recovery seed (or wallet backup) to Turkish users. If the intended meaning is a seed phrase, you might consider whether a term such as “Kurtarma cümlesi” would be more precise.packages/suite-data/files/translations/pt.json (3)
64-64: [Image Validation Error Message Improvement]
The updated message now states: "Cor da imagem inválida. Ela deve conter apenas preto e branco, não escala de cinza." Consider if “não escala de cinza” might be clearer as “sem escala de cinza” to reinforce that grayscale is not allowed.
269-269: [Activated Coins Label Brevity]
The key"TR_ACTIVATED_COINS"now has the value "Ativado". While the brevity may be acceptable in the UI context, consider whether a slightly more descriptive label (such as "Ativado" vs. "Ativo") is consistent with labels in other languages.
555-555: [EVM Send Explanation Repetition]
The updated"TR_CONFIRM_EVM_EXPLANATION_SEND_DESCRIPTION"reads:
"Envie apenas pela rede {network}. O endereço deve estar na rede {network} para a criptomoeda enviada ser recebida."
While clear, it repeats the network specification twice. Consider whether this repetition is intentional for emphasis or if the sentence could be streamlined (for example, by omitting the second reference).packages/suite-data/files/translations/it.json (1)
269-269: Activated Coins Label Simplification
The label “TR_ACTIVATED_COINS” has been changed to “Attivato.” While the shortened form is cleaner, please confirm that the new term fully communicates the intended meaning to all users.packages/suite-data/files/translations/es.json (4)
359-359: Backup Recovery Seed Label Update
The updated key"TR_BACKUP_RECOVERY_SEED"now shows the value “copia de seguridad del monedero”.
- Observation: Notice that the value is entirely lowercase whereas similar keys elsewhere (e.g. “La copia de seguridad se ha realizado correctamente”) may use title case.
- Action: Consider standardizing the capitalization to maintain consistency across the UI unless this is an intentional stylistic choice.
1550-1554: Send Address Confirmation Instructions Update
The set of new keys for address confirmation now reads as follows:
- TR_SEND_ADDRESS_CONFIRMATION_HEADING: “Comprueba la dirección para no poner en riesgo tus fondos”
- TR_SEND_ADDRESS_CONFIRMATION_ITEM_1_HEADING: “Ve a la aplicación, el intercambio o el sitio web del que obtuviste la dirección original.”
- TR_SEND_ADDRESS_CONFIRMATION_ITEM_2_HEADING: “Compárala con la dirección que aparece en tu Trezor.”
- TR_SEND_ADDRESS_CONFIRMATION_ITEM_3_HEADING: “Si son idénticas, confírmalo en tu Trezor.”
- TR_SEND_ADDRESS_CONFIRMATION_NOTE: “Comprueba que la dirección original y la que se muestra en tu Trezor sean idénticas.”
These instructions are clear and emphasize the importance of cross-checking addresses—a critical safety measure.- Action: Please confirm that these entries fully match the source strings and that any embedded HTML (for links, etc.) is correctly rendered elsewhere.
1348-1349: Non-ASCII Characters Guidance
The keys:
"TR_PASSPHRASE_NON_ASCII_CHARS"now reads “Recomendamos usar únicamenteABC,abc,123,espaciosyestos caracteres especiales”"TR_PASSPHRASE_NON_ASCII_CHARS_WARNING"now explains “Usar caracteres especiales que no figuren en la lista puede provocar problemas de compatibilidad en el futuro.”
These updates provide helpful guidelines to users regarding passphrase content.- Action: Ensure that the code tags and any other inline HTML are rendered correctly in the UI.
2000-2002: Troubleshooting Cable and Computer Tips
The changes in the troubleshooting section for hardware connection now include:
- TR_TROUBLESHOOTING_TIP_CABLE_TITLE (line 2000): “Usa otro cable USB”
- TR_TROUBLESHOOTING_TIP_COMPUTER_DESCRIPTION (line 2001): “Conecta tu dispositivo a otro ordenador que tenga instalado Trezor Bridge.”
- TR_TROUBLESHOOTING_TIP_COMPUTER_TITLE (line 2002): “Utiliza otro ordenador”
These clear, actionable tips help users troubleshoot connectivity issues effectively.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (12)
packages/suite-data/files/translations/cs.json(40 hunks)packages/suite-data/files/translations/de.json(39 hunks)packages/suite-data/files/translations/en.json(2 hunks)packages/suite-data/files/translations/es.json(42 hunks)packages/suite-data/files/translations/fr.json(39 hunks)packages/suite-data/files/translations/it.json(39 hunks)packages/suite-data/files/translations/ja.json(6 hunks)packages/suite-data/files/translations/nl.json(7 hunks)packages/suite-data/files/translations/pt.json(44 hunks)packages/suite-data/files/translations/tr.json(42 hunks)packages/suite-data/files/translations/zh.json(2 hunks)packages/suite/src/support/messages.ts(3 hunks)
✅ Files skipped from review due to trivial changes (1)
- packages/suite/src/support/messages.ts
⏰ Context from checks skipped due to timeout of 90000ms (9)
- GitHub Check: run-desktop-tests (@group=wallet, trezor-user-env-unix bitcoin-regtest)
- GitHub Check: run-desktop-tests (@group=other, trezor-user-env-unix)
- GitHub Check: run-desktop-tests (@group=settings, trezor-user-env-unix bitcoin-regtest)
- GitHub Check: Setup and Cache Dependencies
- GitHub Check: build-web
- GitHub Check: run-desktop-tests (@group=device-management, trezor-user-env-unix)
- GitHub Check: build-web
- GitHub Check: Analyze with CodeQL (javascript)
- GitHub Check: run-desktop-tests (@group=suite, trezor-user-env-unix)
🔇 Additional comments (124)
packages/suite-data/files/translations/nl.json (6)
3-3: New Key Addition: "AMOUNT_EXCEEDS_MAX"The new key clearly communicates that the entered amount exceeds the allowed maximum. The usage of the
{maxAmount}placeholder appears correct. Please verify that this wording and placeholder format are consistent with similar messages in other language files.
13-13: New Key Addition: "AMOUNT_NOT_ENOUGH_CURRENCY_FEE_WITH_ETH_AMOUNT"This entry provides a specific error message indicating insufficient funds to cover transaction fees, using the placeholders
{networkDisplaySymbol}and{feeAmount}. Ensure that these placeholders exactly match those used in the corresponding translation updates for other platforms.
40-40: New Key Addition: "EMPTY_NFT_COLLECTIONS"The new key
"EMPTY_NFT_COLLECTIONS": "Lege collecties"is concise and clear for indicating an absence of items. This message appears appropriate for its context; just ensure that the term “collecties” aligns with the terminology used elsewhere in your translation files.
124-124: New Key Addition: "RECEIVE_UNVERIFIED_ADDRESS_REVEAL"The addition of this key delivers a clear call to action for generating an unverified address. The message
"Ongeverifieerd adres genereren"is straightforward. Confirm that the terminology matches the overall style guide and user interface language.
220-220: Modified Key: "TR_ACCOUNT_TYPE" UpdateThe key
"TR_ACCOUNT_TYPE"has been updated from its previous value (presumably"Klant type") to"Soort account". This change helps clarify the meaning in Dutch. Please double-check for consistency with similar keys in both the Dutch translation and other languages.
249-249: New Key Addition: "TR_ADD_NETWORK_ACCOUNT"This new translation key,
"TR_ADD_NETWORK_ACCOUNT": "{network} account toevoegen", integrates a placeholder to dynamically insert the network name. Verify that the placeholder{network}is also used consistently in related files and that the sentence structure is natural in Dutch.packages/suite-data/files/translations/zh.json (2)
680-681: New Device Security Check Translations AddedThe two new entries for device security provide messages for when the device authenticity and entropy security checks fail. They read as follows:
•"TR_DEVICE_COMPROMISED_DEVICE_AUTHENTICITY_TEXT": "您的 Trezor 设备验证检查已失败。"
•"TR_DEVICE_COMPROMISED_ENTROPY_CHECK_TEXT": "创建钱包时验证熵的安全检查失败。"Please verify that these translations accurately capture the intended security warnings and are consistent in tone and terminology with similar entries in other language files.
1551-1555: New Transaction Address Confirmation Translations AddedThe set of new keys for transaction address confirmation are as follows:
•"TR_SEND_ADDRESS_CONFIRMATION_HEADING": "验证地址以避免发错地址的风险"
•"TR_SEND_ADDRESS_CONFIRMATION_ITEM_1_HEADING": "访问获取原始地址的应用程序、交易所或网站。"
•"TR_SEND_ADDRESS_CONFIRMATION_ITEM_2_HEADING": "将该地址与您的 Trezor 设备上显示的地址进行核对。"
•"TR_SEND_ADDRESS_CONFIRMATION_ITEM_3_HEADING": "在您的 Trezor 设备上确认它们是否完全匹配。"
•"TR_SEND_ADDRESS_CONFIRMATION_NOTE": "确认原始地址与您的 Trezor 设备上显示的地址完全一致。"These additions provide a clear and step-by-step guideline to help users confirm transaction addresses, which is critical for preventing sending funds to an incorrect address. Ensure that the language is consistent with the rest of the suite and that the instructions match the procedural context in the user interface.
packages/suite-data/files/translations/ja.json (6)
269-269: Translation improved for better clarity and consistencyThe translation for
"TR_ACTIVATED_COINS"was changed from"有効化されたコイン"to"有効化したコイン"to use a more natural and active voice in Japanese.
680-682: Translation improved for better clarity and security contextThe translations for device security check messages were improved:
"TR_DEVICE_COMPROMISED_DEVICE_AUTHENTICITY_TEXT"- Translation added for device authentication check failure message"TR_DEVICE_COMPROMISED_ENTROPY_CHECK_TEXT"- Translation added for entropy validation failure during wallet creationThese translations help users better understand critical security-related messages.
840-841: Translation improved for better clarity on network-specific instructionsThe translations for EVM network explanations were improved:
"TR_EVM_EXPLANATION_RECEIVE_DESCRIPTION"- Added clearer explanation about network fees in {network} ETH"TR_EVM_EXPLANATION_SEND_DESCRIPTION"- Added clearer guidance about sending only through {network} networkThese changes help users better understand network-specific requirements and avoid mistakes.
1068-1068: Translation improved for better clarity and consistencyThe translation for
"TR_INACTIVE_COINS"was changed from"未有効化"to"有効化していないコイン"to be more descriptive and consistent with other coin-related translations.
1551-1555: Translation added for address confirmation security guidanceNew translations added for address confirmation security messages:
"TR_SEND_ADDRESS_CONFIRMATION_HEADING"- Added heading about address verification"TR_SEND_ADDRESS_CONFIRMATION_ITEM_1_HEADING"- Added instruction to check original address source"TR_SEND_ADDRESS_CONFIRMATION_ITEM_2_HEADING"- Added instruction to compare addresses"TR_SEND_ADDRESS_CONFIRMATION_ITEM_3_HEADING"- Added instruction to confirm match on Trezor"TR_SEND_ADDRESS_CONFIRMATION_NOTE"- Added note about verifying address matchThese translations provide important security guidance for address verification.
2061-2061: Translation improved for better clarity and consistencyThe translation for
"TR_UNSUPPORTED_COINS"was changed from"新しいTrezorsでサポートされます"to"新しいTrezorsでサポートされるコイン"to be more specific about referring to coins and maintain consistency with other coin-related translations.packages/suite-data/files/translations/cs.json (16)
34-43: Consistent Update for Destination Tag Translations
The revisions for the destination tag keys now uniformly use “Poznámka / cílová značka” across labels, banners, tooltips, and notes. This improves clarity and ensures UI consistency.
64-64: Refined Image Validation Error Message
The updated text forIMAGE_VALIDATION_ERROR_INVALID_COLOR_COMBINATION("Nesprávná barva obrázku. Může obsahovat pouze černou a bílou barvu, ne stupně šedi.") makes it explicitly clear that only strictly black and white are allowed.
148-148: Clearer Connection Error Message
The change toSETTINGS_ADV_COIN_CONN_INFO_NO_CONNECTEDnow instructs users more directly to re‑connect the device and verify both their internet connection and the correctness of the backend URL. This should help reduce support queries regarding connectivity issues.
269-269: Simplified Activated Coins Label
The update ofTR_ACTIVATED_COINSto “Aktivováno” is concise and consistent with similar labels in the application.
359-364: Standardized Backup Terminology
BothTR_BACKUP_RECOVERY_SEEDandTR_BACKUP_SUCCESSFULhave been updated to refer to the wallet backup explicitly as “Záloha peněženky.” This consistent phrasing minimizes user confusion regarding backup functionality.
390-390: Updated Buy Detail Error Message
The revised text forTR_BUY_DETAIL_ERROR_TEXTclearly communicates that the transaction failed or was rejected due to issues with the configured payment method. Verify that this message aligns with similar error feedback provided elsewhere in the UI.
474-474: Enhanced Recovery Seed Check Description
The new translation forTR_CHECK_RECOVERY_SEED_DESC_T3B1("Pomocí dvou tlačítek zadejte zálohu peněženky. Tím se vyhnete vystavení svých citlivých informací potenciálně nezabezpečenému počítači nebo webovému prohlížeči.") provides clear, step‑by‑step guidance for secure seed entry.
1342-1342: Unrecoverability Warning for Passphrase
The update toTR_PASSPHRASE_DESCRIPTION_ITEM3now unambiguously states that neither the passphrase nor the wallet backup can be recovered by anyone—including Trezor support. This precise warning is essential for user security.
1347-1347: Guidance on Allowed Characters for Passphrase
The revisedTR_PASSPHRASE_NON_ASCII_CHARSinstructs users to use only the specified characters (ABC, abc, 123, mezery a tyto speciální znaky). This clarity helps prevent future compatibility issues.
1348-1348: Non-ASCII Characters Warning Update
The updated warning inTR_PASSPHRASE_NON_ASCII_CHARS_WARNINGalerts users that using any other special characters may cause compatibility issues in the future. The message is now more direct and cautionary.
1365-1365: Stronger Passphrase Backup Warning
The change inTR_PASSPHRASE_WALLET_CONFIRMATION_STEP3_WARNINGemphasizes that the passphrase should be recorded on paper and not stored digitally, as it cannot be recovered by anyone. This enhanced warning promotes better security practices.
1414-1414: Concise Update Call-to-Action for Firmware Update
The updated label inTR_QUICK_ACTION_UPDATE_POPOVER_CLICK_TO_START_UPDATE, now simply “Aktualizovat”, is succinct and clearly conveys the intended action.
1419-1420: Clear RBF Amount Labels
The new translations forTR_RBF_NEW_AMOUNT(“Nová částka”) andTR_RBF_ORIGINAL_AMOUNT(“Původní částka”) provide clear labels for Replace-By-Fee editing. Ensure these labels are consistent with similar monetary fields in the app.
1591-1591: Improved Device Banner for Remembrance Mode
The update toTR_SETTINGS_DEVICE_BANNER_TITLE_REMEMBEREDnow instructs users to “Připojte a odemkněte Trezor, abyste mohli změnit nastavení.” This clarifies that unlocking the device is necessary before modifying settings.
2137-2137: Enhanced Wipe Confirmation Warning
The revisedTR_WIPE_DEVICE_CHECKBOX_1_TITLE(“Chápu, že tato akce odstraní všechna data v zařízení.”) provides a very clear and cautionary message about the consequences of wiping the device.
2141-2142: Precise Modal Description for Device Wipe
The updatedTR_WIPE_DEVICE_MODAL_DESCRIPTIONnow succinctly warns that resetting the device will erase all data and emphasizes the necessity of having a secure backup. This clear caution is crucial for protecting users’ assets.packages/suite-data/files/translations/tr.json (7)
34-43: Destination Tag Keys Updated
The translations for the destination tag section have been updated (e.g."DESTINATION_TAG","DESTINATION_TAG_BANNER_RECEIVE","DESTINATION_TAG_BANNER_SEND","DESTINATION_TAG_IS_NOT_NUMBER","DESTINATION_TAG_IS_NOT_VALID","DESTINATION_TAG_NOTE","DESTINATION_TAG_SHORT", and"DESTINATION_TAG_SWITCH"). Please verify that the terminology (using “Not/Hedef etiketi”) is consistent across the application and that the embedded HTML (e.g. the<a>Daha fazla bilgi edinin</a>link) is correctly formed and secure.
64-64: Clarification for Image Validation Message
The error message"IMAGE_VALIDATION_ERROR_INVALID_COLOR_COMBINATION"now explicitly states that only black and white (and not grayscale) are allowed. This improves clarity for users.
269-269: Activated Coins Translation Check
The key"TR_ACTIVATED_COINS"is now translated as “Etkinleştirildi”. Ensure that this term aligns with the project’s standard glossary for coin status indicators.
551-551: Empty Hidden Wallet Confirmation Update
The key"TR_CONFIRM_EMPTY_HIDDEN_WALLET_ON"now instructs: “"{deviceLabel}" cihazında boş Parola cüzdanını onaylayın.” This message appears clear; just double-check that it aligns with similar wallet confirmation messages across the suite.
1550-1554: Send Address Confirmation Messages Revised
The updated keys related to send address confirmation ("TR_SEND_ADDRESS_CONFIRMATION_HEADING","TR_SEND_ADDRESS_CONFIRMATION_ITEM_1_HEADING","TR_SEND_ADDRESS_CONFIRMATION_ITEM_2_HEADING","TR_SEND_ADDRESS_CONFIRMATION_ITEM_3_HEADING", and"TR_SEND_ADDRESS_CONFIRMATION_NOTE") now provide clear, step‐by‐step instructions for users to verify that the original address exactly matches the address shown on their Trezor device. Please check that the variable placeholders and HTML markup (if any) render as expected in the UI.
2000-2003: Troubleshooting Tips for Connection Issues
The troubleshooting tips regarding cable and computer choices (for example,"TR_TROUBLESHOOTING_TIP_CABLE_TITLE"and"TR_TROUBLESHOOTING_TIP_COMPUTER_DESCRIPTION") have been updated. They now advise users to try a different USB cable or connect the device to a different computer if problems persist. These instructions are clear and user friendly; please confirm that they fit within the overall troubleshooting flow in the application.
2141-2141: Wipe Device Modal Description Update
The message for"TR_WIPE_DEVICE_MODAL_DESCRIPTION"has been updated to warn users that wiping the device will erase all data and to ensure they have taken a backup beforehand. The updated language is clear and appropriately cautionary.packages/suite-data/files/translations/pt.json (10)
34-43: [Destination Tag Strings Consistency]
The new keys in this block introduce more detailed guidance for “destination tags” (or memos) when receiving and sending XRP. Please verify that the terms “Memo/tag de destino” and associated phrases are used consistently across all language files. In particular, check that the HTML markup (e.g.<a>Saiba mais</a>) is preserved verbatim across translations.
148-148: [Backend Connection Message Clarity]
The updated string reads: "Não conectado ao backend. Reconecte seu dispositivo e verifique se a conexão com a Internet ou a URL do backend personalizado está correta." This message provides clear troubleshooting direction. Verify that it aligns with similar wording in other localization files.
474-474: [Recovery Seed Instruction Update]
The updated instruction"TR_CHECK_RECOVERY_SEED_DESC_T3B1"now advises:
"Use o teclado de dois botões para inserir o backup da sua carteira. Isso evita expor suas informações confidenciais a um computador ou navegador da web potencialmente inseguro."
This is clear and provides additional security guidance. Please verify that this instruction aligns with the intended UX.
551-551: [Empty Hidden Wallet Confirmation]
The updated string"TR_CONFIRM_EMPTY_HIDDEN_WALLET_ON"now instructs users to "Confirme a carteira de frase secreta vazia no dispositivo "{deviceLabel}"." Ensure that the placeholder{deviceLabel}is correctly replaced at runtime and that the instruction is unambiguous in context.
1414-1414: [Quick Action Update Popover]
The key"TR_QUICK_ACTION_UPDATE_POPOVER_CLICK_TO_START_UPDATE"is updated to "Atualizar agora". This concise call-to-action appears clear. Confirm that it fits the design requirements and functions as intended in the UI.
1419-1420: [RBF Labels Conciseness]
The updated keys"TR_RBF_NEW_AMOUNT": "Novo valor"and"TR_RBF_ORIGINAL_AMOUNT": "Valor original"are succinct and appropriate for use as field labels.
1472-1472: [Saved Label]
The updated string for"TR_SAVED"is now "Salvo". This is straightforward and fits the UI context.
1586-1591: [Settings Banner Consistency]
Both"TR_SETTINGS_COINS_BANNER_DESCRIPTION_REMEMBERED_DISCONNECTED"and"TR_SETTINGS_DEVICE_BANNER_TITLE_REMEMBERED"have been updated to instruct: "Conecte e destrave o Trezor para alterar as configurações". The language is consistent and clear; please double-check that it meshes well with adjacent UI elements and translated content in other locales.
2009-2010: [Troubleshooting Tip Titles]
The revised troubleshooting tip titles:
•"TR_TROUBLESHOOTING_TIP_CABLE_TITLE": "Use outro cabo USB"
•"TR_TROUBLESHOOTING_TIP_COMPUTER_TITLE": "Use outro computador"
are clear and provide actionable advice. Confirm that these instructions meet the design and troubleshooting guidelines.
2140-2140: [Wipe Device Modal Description Clarity]
The updated"TR_WIPE_DEVICE_MODAL_DESCRIPTION"now reads:
"A limpeza do dispositivo apagará todos os dados. Faça o backup da carteira antes de limpá-la, para que você possa restaurar o acesso aos fundos."
This message is clear and stresses the importance of backup before proceeding. Please ensure it is consistent with other similar warnings in the application.packages/suite-data/files/translations/it.json (13)
34-43: Destination Tag Translations Update
The keys for destination tag messages now include “/memo” (e.g. “Tag di destinazione/memo”) and their related banner, error, note, short, switch, and tooltip texts have been updated accordingly. This clearly communicates the dual purpose with improved clarity. Please verify consistency with other locale files.
148-148: Backend Connection Error Message Update
The message for “SETTINGS_ADV_COIN_CONN_INFO_NO_CONNECTED” now instructs the user to verify both the Internet connection and the custom backend URL. The updated text appears clear and actionable for troubleshooting connection issues.
359-364: Backup Process Translations Update
The translations for “TR_BACKUP_RECOVERY_SEED”, “TR_BACKUP_SUBHEADING_1”, and “TR_BACKUP_SUCCESSFUL” now consistently refer to the wallet backup process as “Back-up del wallet.” This provides clearer, unified messaging for users regarding wallet recovery.
551-551: Empty Hidden Wallet Confirmation Message
The translation for “TR_CONFIRM_EMPTY_HIDDEN_WALLET_ON” instructs users to confirm an empty passphrase wallet on the device (showing the dynamic {deviceLabel}). The message is clear and user-friendly.
767-768: Device Reconnection Guidance Update
The keys “TR_DISCONNECT_YOUR_TREZOR” and “TR_DISCONNECT_YOUR_TREZOR_SUBTITLE” now advise users to “Riconnetti il dispositivo” and explain that this usually resolves the issue. The phrasing is direct and in line with troubleshooting best practices.
1342-1342: Passphrase Non-Recoverability Emphasis
The updated “TR_PASSPHRASE_DESCRIPTION_ITEM3” clearly warns that neither the passphrase nor the wallet backup can be recovered—not even by support. This critical security notice is now prominently stated.
1347-1353: Passphrase Wallet Confirmation Instructions
The multi-step instructions for confirming a passphrase wallet (including item descriptions and warnings) have been updated. They provide explicit guidance on writing down and safeguarding the passphrase. The detailed language should help prevent user errors during setup.
1419-1420: Replace-By-Fee (RBF) Labels Update
The labels “TR_RBF_NEW_AMOUNT” and “TR_RBF_ORIGINAL_AMOUNT” are now rendered as “Nuovo importo” and “Importo originale,” respectively. These concise translations effectively differentiate between the new and the original amounts in RBF transactions.
1472-1472: Saved Label Terminology
The key “TR_SAVED” is now translated as “Risparmiati.” Please verify that this term correctly reflects the context (for example, if it denotes “saved” settings or data, “Salvato” might be more standard) so that users are not confused by an unintended meaning.
1672-1672: Staking Expected Rewards Clarity
The “TR_STAKE_EXPECTED_REWARDS” update now clearly indicates that the expected rewards are calculated per epoch—with plural handling for days. This improved expression aids users in setting accurate expectations for staking reward intervals.
1690-1690: No Rewards Notification Update
The translation for “TR_STAKE_NO_REWARDS” now reads “Nessuna ricompensa disponibile,” which succinctly informs users when there are no staking rewards.
1723-1723: Unstaking Duration Notification Update
The updated “TR_STAKE_UNSTAKING_TAKES” now explains that unstaking may take up to a specified number of days and informs the user once the process completes. The ICU plural syntax is used correctly to address variable durations.
2140-2141: Wipe Device Warning Enhancements
The warnings for “TR_WIPE_DEVICE_DESCRIPTION” and “TR_WIPE_DEVICE_MODAL_DESCRIPTION” have been revised to comprehensively explain that wiping the device will permanently erase all stored data—including PIN and backup information—and stress the critical importance of having a wallet backup. These detailed descriptions align well with security best practices.packages/suite-data/files/translations/de.json (26)
34-39: New “Destination Tag” keys added
The new translation entries for destination tag functionality (including banner messages and error messages) have been introduced. The texts use the combined term “Memo/Destination-Tag” consistently and include HTML elements (e.g.<a>Mehr erfahren</a>). Please verify that these messages render correctly in the UI and align with the product’s style guidelines.
41-43: Additional Destination Tag strings
The added keys"DESTINATION_TAG_SHORT","DESTINATION_TAG_SWITCH", and"DESTINATION_TAG_TOOLTIP"continue the consistent use of “Memo/Destination-Tag.” Ensure that the shortened and switch prompt messages are clear to users and follow the translation conventions of other languages.
148-148: Backend connection message update
The updated string for"SETTINGS_ADV_COIN_CONN_INFO_NO_CONNECTED"advises users to reconnect their device and check their Internet or custom backend URL. The language is direct and clear. Please double‑check with product guidelines that this phrasing meets UX standards.
359-359: Streamlined backup terminology
The key"TR_BACKUP_RECOVERY_SEED"is now labeled simply as “Wallet-Backup.” This short form is more consistent with other backup-related keys. Confirm that all related documentation and UI elements use the updated terminology consistently.
364-364: Successful backup feedback updated
The revised translation for"TR_BACKUP_SUCCESSFUL"(“Wallet-Backup erfolgreich”) is concise and clear. Please ensure that this update is propagated in both the UI messages and any related help texts.
269-269: Activated coins text simplified
The value for"TR_ACTIVATED_COINS"has been updated to “Aktiviert.” This single‐word translation simplifies the display. Verify that the context in the UI makes it clear to the user what “Aktiviert” refers to.
314-314: Amount reduction message review
The translation"TR_AMOUNT_REDUCED_TXS"now reads “Betrag ermäßigt.” Note that “ermäßigt” can imply a discount. Please confirm that this term appropriately describes the technical operation (e.g. a reduction due to fee adjustments) and is consistent with related terminology.
474-474: Seed check instructions update
The updated text for"TR_CHECK_RECOVERY_SEED_DESC_T3B1"now instructs users to use the “Zwei-Tasten-Tastatur” for entering their backup. The clarification about enhanced security for sensitive data is useful.
737-737: View‑only mode description clarified
The new description for"TR_DEVICE_SETTINGS_ENABLE_VIEW_ONLY_DESC"(“Verbinde Trezor, um Coins zu verschieben oder Swaps durchzuführen.”) clearly instructs users on what enabling view‑only mode achieves. The language is succinct and fits the technical context.
761-761: Tooltip for switching devices updated
The revised tooltip"TR_DISABLED_SWITCH_TOOLTIP"now reads “Gerät zum Ändern verbinden und entsperren.” This message effectively reminds users to reconnect and unlock their Trezor for switching operations.
1414-1414: Quick action update label shortened
The string for"TR_QUICK_ACTION_UPDATE_POPOVER_CLICK_TO_START_UPDATE"has been changed to “Jetzt aktualisieren.” This clear call-to-action is brief and user‑friendly.
1420-1420: RBF new amount label updated
The updated text"TR_RBF_NEW_AMOUNT": "Neuer Betrag"is straightforward, indicating the new value after fee bumping.
1421-1421: RBF original amount label clarified
The translation for"TR_RBF_ORIGINAL_AMOUNT"now simply states “Ursprünglicher Betrag,” which is clear and concise.
1550-1550: Send address confirmation heading improved
The key"TR_SEND_ADDRESS_CONFIRMATION_HEADING"now instructs “Verifiziere die Adresse, um deine Assets nicht zu riskieren.” This added urgency and clarity helps emphasize the importance of address verification before transferring assets.
1551-1551: Address confirmation step 1 updated
The updated"TR_SEND_ADDRESS_CONFIRMATION_ITEM_1_HEADING"directs users to check the original source (app, exchange, or website) for the address. This clear instruction minimizes risk of errors.
1552-1552: Address confirmation step 2 updated
The text"TR_SEND_ADDRESS_CONFIRMATION_ITEM_2_HEADING"now advises comparing the address with the one on the Trezor. The message is succinct and clear.
1553-1553: Address confirmation step 3 updated
The instruction"TR_SEND_ADDRESS_CONFIRMATION_ITEM_3_HEADING"(“Überprüfe auf deinem Trezor, ob sie genau übereinstimmen.”) reinforces the need for precise verification.
1554-1554: Additional note on address confirmation added
The note via"TR_SEND_ADDRESS_CONFIRMATION_NOTE"emphasizes that the original address must exactly match the one on the Trezor. This is an important safeguard.
1586-1586: Banner message for disconnected remembered device
The updated"TR_SETTINGS_COINS_BANNER_DESCRIPTION_REMEMBERED_DISCONNECTED"now advises “Verbinde und entsperre deinen Trezor, um die Einstellungen zu ändern.” This is clear; please verify that it aligns with similar notifications in other languages.
1591-1591: Device banner title consistency
The new title"TR_SETTINGS_DEVICE_BANNER_TITLE_REMEMBERED"mirrors the banner description and instructs users to reconnect and unlock their device. Consistency across these messages is good.
2137-2137: Wipe device confirmation checkbox text updated
The updated"TR_WIPE_DEVICE_CHECKBOX_1_TITLE"clearly informs users that the action will delete all data on the device. This is a critical security notice and the text is unambiguous.
2140-2140: Wipe device modal description updated
The new"TR_WIPE_DEVICE_MODAL_DESCRIPTION"now provides detailed instructions on what happens during a wipe and emphasizes the need for a backup. The message is clear and cautionary.
1342-1342: Passphrase importance emphasized
The updated"TR_PASSPHRASE_DESCRIPTION_ITEM3"stresses that neither a passphrase nor the wallet‑backup can be recovered—even by Trezor Support. Please confirm that this tone (firm and cautionary) is consistent with overall security communication.
1348-1348: Allowed characters clarification for passphrase
The string"TR_PASSPHRASE_NON_ASCII_CHARS"now clearly specifies which characters are acceptable. The inclusion of inline HTML (code tags) is useful provided the UI supports it.
1349-1349: Warning on non-ASCII characters updated
The revised warning"TR_PASSPHRASE_NON_ASCII_CHARS_WARNING"informs users about potential future compatibility issues. This is clear and appropriate.
1363-1363: Passphrase backup warning updated
The updated"TR_PASSPHRASE_WALLET_CONFIRMATION_STEP2_WARNING"reinforces that passphrases and wallet‑backups cannot be recovered. The succinct message helps stress security best practices.packages/suite-data/files/translations/es.json (11)
35-43: Destination Tag Translations Update
The new and updated keys for destination tags (“DESTINATION_TAG_BANNER_RECEIVE”, “DESTINATION_TAG_BANNER_SEND”, “DESTINATION_TAG_IS_NOT_NUMBER”, “DESTINATION_TAG_IS_NOT_VALID”, “DESTINATION_TAG_NOTE”, “DESTINATION_TAG_SHORT”, “DESTINATION_TAG_SWITCH”, and “DESTINATION_TAG_TOOLTIP”) are clear and instructive. They offer precise guidance to the user regarding XRP destination tags.
- Action: Confirm that the phrasing and tone here are in line with similar translation keys in other locales to maintain consistency.
64-64: Image Validation Error Message Update
The updated message for"IMAGE_VALIDATION_ERROR_INVALID_COLOR_COMBINATION"now reads:
“Color de imagen no válido. Solo puede contener blanco y negro, no escala de grises.”
This is succinct and clear.
- Action: Ensure that this phrasing is consistent with similar image validation messages across the suite (including capitalization and punctuation).
148-148: Backend Connection Info Message Update
The new translation for"SETTINGS_ADV_COIN_CONN_INFO_NO_CONNECTED"clarifies the user action needed when disconnected from the backend.
- Action: Please verify that the tone (informative yet friendly) matches other system messages and that variable placeholders (if any) are handled correctly.
269-269: Activated Coins Label Revision
The updated key"TR_ACTIVATED_COINS"now simply reads “Activado”. Although very succinct, double-check that this label fits in all UI contexts and is consistent with similar one-word status indicators in other languages.
314-314: Amount Reduced Translation
The updated key"TR_AMOUNT_REDUCED_TXS"now has the value “Importe reducido”. This short label is clear.
- Action: Confirm that this term correctly describes the context where a reduced amount is shown (for example, within transaction details) and aligns with the styling used in other transaction-related messages.
364-364: Backup Successful Message
The translation"TR_BACKUP_SUCCESSFUL"now reads “La copia de seguridad se ha realizado correctamente”. This message is clear and reassuring.
390-390: Buy Detail Error Message Adjustment
The updated text for"TR_BUY_DETAIL_ERROR_TEXT"is now “La transacción ha fallado o se ha rechazado. No se ha efectuado el cobro en tu método de pago.”
- Observation: This message clearly informs the user of the failure without unnecessary detail.
- Action: Verify consistency with similar error messages in other translation files regarding punctuation and tone.
1342-1342: Passphrase Description Enhancement
The updated key"TR_PASSPHRASE_DESCRIPTION_ITEM3"now reads:
“Nadie puede recuperar tu frase de contraseña ni tu copia de seguridad de la cartera, ni siquiera el servicio de atención al cliente de Trezor.”
- Observation: This sentence clearly reinforces the importance of safeguarding the passphrase.
- Action: Verify that this message does not conflict with other passphrase-related warnings and is consistently applied in all supported languages.
1363-1363: Passphrase Wallet Confirmation Warning
The updated key"TR_PASSPHRASE_WALLET_CONFIRMATION_STEP2_WARNING"reinforces that “Nadie puede recuperar tu frase de contraseña ni tu copia de seguridad de la cartera, ni siquiera el servicio de atención al cliente de Trezor.”
- Observation: This is a critical security reminder.
- Action: Consider whether the same message exists elsewhere in the project so users receive a consistent warning.
1414-1414: Quick Action Update Popover Revision
The key"TR_QUICK_ACTION_UPDATE_POPOVER_CLICK_TO_START_UPDATE"has been updated to “Actualizar ahora”.
- Observation: This concise call-to-action should help users initiate updates quickly.
- Action: Verify that this shorter text still clearly communicates the intent in the context of the popover.
1419-1420: RBF Amount Labels Update
The two keys"TR_RBF_NEW_AMOUNT"and"TR_RBF_ORIGINAL_AMOUNT"now read “Nuevo importe” and “Importe original”, respectively.
- Observation: These labels are straightforward and fit well in the Replace-By-Fee (RBF) context.
- Action: Confirm that the translations accurately reflect the numerical adjustments shown in the UI.
packages/suite-data/files/translations/fr.json (27)
34-43: Destination Tag Updates
The French translations for destination tag-related keys have been updated to include both “Mémo” and “étiquette” (e.g. “Mémo/étiquette de destination”, “Ajouter un mémo/une étiquette de destination”). This clarifies the dual purpose as seen in other language files and ensures consistency across the UI.
64-64: Image Validation Error Message Update
The error message now states: “Couleur d’image non valide. Elle ne peut contenir que du noir et du blanc, aucune échelle des gris.” This removes any ambiguity regarding grayscale and makes the requirement explicit.
148-148: Server Connection Info Update
The revised message for “SETTINGS_ADV_COIN_CONN_INFO_NO_CONNECTED” now instructs users to reconnect their device and verify either their Internet connection or the URL of their custom server. The instructions are clear and provide actionable guidance.
269-269: Activated Coins Label Simplification
The translation for “TR_ACTIVATED_COINS” has been updated to the simpler “Activé”. This shorter label is likely to improve UI clarity while maintaining the intended meaning.
359-364: Backup Recovery and Success Message Improvements
The keys “TR_BACKUP_RECOVERY_SEED” and “TR_BACKUP_SUCCESSFUL” have been updated to “Sauvegarde du portefeuille” and “Portefeuille sauvegardé avec succès” respectively. These changes enhance clarity and align with similar updates in other translation files.
474-474: Passphrase Entry Instruction Refinement
The update to “TR_CHECK_RECOVERY_SEED_DESC_T3B1” now advises using the 2‑button keypad for entering the seed. This provides users with a more secure method by reducing exposure of sensitive information to potentially unsecured computers or browsers.
629-630: Dashboard Assets Error Messages
Both “TR_DASHBOARD_ASSETS_ERROR” and “TR_DASHBOARD_ASSET_FAILED” now communicate that the assets have not been loaded correctly. These messages are consistent and help inform the user about the loading issue.
651-651: Fee Adjustment Explanation
The “TR_DECREASED_AMOUNT_SELECTION_EXPLANATION” key now instructs the user to select the amount to deduct for covering increased fees. The message is concise, clear, and directly informs the user of the action needed.
680-683: Device Compromise Checks
The updates to “TR_DEVICE_COMPROMISED_DEVICE_AUTHENTICITY_TEXT”, “TR_DEVICE_COMPROMISED_ENTROPY_CHECK_TEXT”, “TR_DEVICE_COMPROMISED_FW_HASH_CHECK_TEXT”, and “TR_DEVICE_COMPROMISED_FW_REVISION_CHECK_TEXT” clearly indicate various failure points in device authenticity and security checks. These messages are critical for alerting users to potential security issues.
966-966: Firmware Risk Warning Enhancement
The updated “TR_FIRMWARE_IS_POTENTIALLY_RISKY” message now warns users more explicitly that updating the firmware carries risks (such as data loss) and that a proper backup is required beforehand. This is a vital improvement for user safety.
1902-1902: Trading Fees Clarification on Website
The “TR_TRADING_FEES_ON_WEBSITE” string now informs users that some fees may not be included in the displayed price, and that the total cost will be shown on the provider’s website. This added detail improves transparency.
1904-1904: Fixed Rate Explanation Update
The updated “TR_TRADING_FIX_RATE_DESCRIPTION” succinctly explains that the rate is locked for 15 minutes in return for higher fees. The message is clear and informative.
1906-1906: Floating Rate Description Update
The “TR_TRADING_FLOATING_RATE_DESCRIPTION” now better explains that the rate is an estimate which may adjust in real time based on market fluctuations. This rewording enhances user understanding of the conditions.
1909-1909: KYC Refund Requirement Notice
The “TR_TRADING_KYC_NO_REFUND” message now states that KYC is only required under exceptional circumstances and notes when it is required for refunds. Although the wording is a bit dense, it conveys important eligibility details.
1923-1923: Offer Search Status Update
The “TR_TRADING_OFFER_LOOKING” translation now clearly indicates that the application is searching for the best offer. This concise message provides users with immediate feedback.
1948-1958: Swap Modal Terms and Legal Information
The block of translations for the swap modal—from “TR_TRADING_SWAP_MODAL_CONFIRM” to “TR_TRADING_SWAP_MODAL_TERMS_6” and “TR_TRADING_SWAP_MODAL_VERIFIED_PARTNERS_HEADER”—has been updated to provide comprehensive instructions, legal disclaimers, and security warnings regarding swapping cryptocurrencies. All dynamic placeholders (such as {fromCrypto}, {toCrypto}, and {provider}) appear to be in place. These thorough details should help users make informed decisions.
1414-1414: Update Popover Action Text
The “TR_QUICK_ACTION_UPDATE_POPOVER_CLICK_TO_START_UPDATE” string effectively prompts users to start updating now. It follows the UI’s action‐oriented style.
1419-1420: Replace-By-Fee Amount Labels
The new translations for “TR_RBF_NEW_AMOUNT” and “TR_RBF_ORIGINAL_AMOUNT” clearly distinguish between the new fee-adjusted amount and the original transaction amount. This clarity is beneficial when the RBF functionality is used.
1342-1342: Passphrase Security Reminder
The update to “TR_PASSPHRASE_DESCRIPTION_ITEM3” reinforces that no one—not even Trezor support—can recover the seed phrase if lost. This is a critical security reminder presented in clear language.
1633-1633: Staking Activation Duration Notice
The “TR_STAKE_ACTIVATION_COULD_TAKE” message now uses plural-friendly formatting to indicate that staking activation generally takes one period (with days indicated as appropriate). This update provides clear expectations.
1673-1673: Expected Rewards Formatting
The “TR_STAKE_EXPECTED_REWARDS” string now incorporates plural formatting for the duration (e.g. “# jour” vs. “# jours”), giving users a precise estimate of when rewards might appear.
1723-1723: Unstaking Duration Information
The update “TR_STAKE_UNSTAKING_TAKES” details that unstaking currently takes up to a specified number of days, with appropriate plural handling. This provides users with clear timing expectations.
2000-2000: Troubleshooting: USB Cable Advisory
The “TR_TROUBLESHOOTING_TIP_CABLE_TITLE” now advises users to “Utilisez un autre câble USB” if connection issues persist. This concise tip should help in troubleshooting hardware connection problems.
2002-2002: Troubleshooting: Alternative Computer Suggestion
The updated “TR_TROUBLESHOOTING_TIP_COMPUTER_TITLE” encourages users to try another computer if issues remain. This is a practical, straightforward troubleshooting measure.
2013-2013: Troubleshooting: USB Port Recommendation
The “TR_TROUBLESHOOTING_TIP_USB_PORT_TITLE” suggests using an alternative port for the USB connection. This new advice is clear and can help resolve connectivity issues.
2137-2137: Device Wipe Confirmation Update
The “TR_WIPE_DEVICE_CHECKBOX_1_TITLE” now clearly states, “Je comprends que cette action supprime toutes les données du dispositif.” This explicit confirmation helps ensure users are fully aware of the impact before proceeding.
2140-2140: Device Wipe Warning Message
The updated “TR_WIPE_DEVICE_DESCRIPTION” provides a detailed warning about the irreversible deletion of all stored data—including the seed phrase and PIN—and emphasizes the necessity of having a backup. This is a crucial and well-presented security alert.
| "TR_BACKUP_RECOVERY_SEED": "Cópia de segurança da carteira", | ||
| "TR_BACKUP_RECOVERY_SEED_FAILED_DESC": "O processo da cópia de segurança da carteira falhou. É altamente recomendado fazer uma cópia de segurança da sua carteira. Siga o link para saber como criar uma cópia de segurança da carteira.", | ||
| "TR_BACKUP_RECOVERY_SEED_FAILED_TITLE": "Falha na cópia de segurança da carteira", | ||
| "TR_BACKUP_SEED_IS_ULTIMATE": "Se precisar restaurar sua carteira para acessar seus fundos, é necessário ter sua semente de recuperação (backup de carteira) ao seu lado. Não perca ou se esqueça. Não há o que fazer caso ela se perca. Ninguém pode ajudar você a recuperá-la, nem mesmo o suporte da Trezor. Portanto, seja responsável e certifique-se de manter suas sementes de recuperação guardadas como se sua vida dependesse disso.", | ||
| "TR_BACKUP_SUBHEADING_1": "Uma cópia de segurança da carteira é uma série de palavras aleatórias gerada pela Tezor. É importante anotar o backup da sua carteira e mantê-lo seguro, pois é a única forma de recuperar e acessar seus fundos", | ||
| "TR_BACKUP_SUCCESSFUL": "Cópia de segurança bem sucedida", | ||
| "TR_BACKUP_SUCCESSFUL": "Cópia de segurança da carteira bem sucedida", |
There was a problem hiding this comment.
[Backup Strings – Typo and Consistency Check]
Several backup-related keys have been updated:
• "TR_BACKUP_RECOVERY_SEED": "Cópia de segurança da carteira"
• "TR_BACKUP_SUBHEADING_1": "Uma cópia de segurança da carteira é uma série de palavras aleatórias gerada pela Tezor. É importante anotar o backup da sua carteira e mantê-lo seguro, pois é a única forma de recuperar e acessar seus fundos"
• "TR_BACKUP_SUCCESSFUL": "Cópia de segurança da carteira bem sucedida"
Please note that in line 363 the word "Tezor" appears instead of "Trezor". Correcting this typo is important for brand consistency.
[refactor_suggestion_essential]
|
@MiroslavProchazka @peter-sanderson possible typo in Trezor ? see #16910 (comment) |
|
Yes, I've already fixed it in Crowdin |
Automatically generated PR for updating crowdin translations.