~exprez135/cryptomator-libre

77b2e67c4974578d174d8c4baa5d50a3c326e4a7 — Sebastian Stenzel 9 months ago c48c9b1
updated labels
1 files changed, 3 insertions(+), 3 deletions(-)

M main/ui/src/main/resources/i18n/strings.properties
M main/ui/src/main/resources/i18n/strings.properties => main/ui/src/main/resources/i18n/strings.properties +3 -3
@@ 110,9 110,9 @@ unlock.error.invalidMountPoint.existing=Mount point "%s" already exists or paren

# Lock
## Force
lock.forced.heading=Forcefully lock vault?
lock.forced.message=The vault "%s" cannot be locked due to open files or pending operations. You can enforce locking, but unsaved data will be lost and pending read/write operations aborted.
lock.forced.confirmBtn=Force locking
lock.forced.heading=Graceful lock failed
lock.forced.message=Locking "%s" was blocked by pending operations or open files. You may force lock this vault, however interrupting I/O may result in the loss of unsaved data.
lock.forced.confirmBtn=Force Lock
## Failure
lock.fail.heading=Locking vault failed.
lock.fail.message=Vault "%s" could not be locked. Ensure unsaved work is saved elsewhere and important Read/Write operations are finished. In order to close the vault, kill the Cryptomator process.