mirrors/cryptomator
1
0
Fork 0
mirror of https://github.com/cryptomator/cryptomator.git synced 2026-09-26 09:54:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

closes #3246

Browse Source 
splitting registerSuccess into two scenes, one for hub 1.3.x and one for legacy
This commit is contained in:
Armin Schrenk
2024-01-17 16:52:35 +01:00
parent a1b712495f
commit 42425afe56
8 changed files with 99 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/main/resources/i18n/strings.properties
+7 -4
View File
@@ -158,15 +158,18 @@ hub.receive.message=Processing response…
hub.receive.description=Cryptomator is receiving and processing the response from Hub. Please wait.
### Register Device
hub.register.message=New Device
hub.register.description=This is the first Hub access from this device. Please authorize it using your Account Key.
hub.register.description=This is the first Hub access from this device. Please register it using your Account Key.
hub.register.nameLabel=Device Name
hub.register.invalidAccountKeyLabel=Invalid Account Key
hub.register.registerBtn=Authorize
hub.register.registerBtn=Register
### Register Device Legacy
hub.register.occupiedMsg=Name already in use
hub.register.legacy.occupiedMsg=Name already in use
hub.register.legacy.description=This is the first Hub access from this device. Please register it.
### Registration Success
hub.registerSuccess.message=Device registered
hub.registerSuccess.description=To access the vault, your device needs to be authorized by the vault owner.
hub.registerSuccess.description=Your device is successfully registered. You can now continue to unlock the vault.
hub.registerSuccess.unlockBtn=Unlock
hub.registerSuccess.legacy.description=To access the vault, your device needs to be additionally authorized by the vault owner.
### Registration Failed
hub.registerFailed.message=Device registration failed
hub.registerFailed.description.generic=An error was thrown in the registration process. For more details, look into the application log.