mirror of
https://github.com/vrtmrz/obsidian-livesync.git
synced 2026-10-25 10:33:21 +00:00
Merge current main into Simplified Chinese translations
This commit is contained in:
vorotamoroz committed
commit
4876374b7e
24 files changed
+650
-319
No files matched your search
@@ -2235,10 +2235,6 @@ Ui:
|
||||
Scram: Scram!
|
||||
SendChunks: Send chunks
|
||||
Syncing: Syncing
|
||||
WarningLockedReadyAction: I am ready, unlock the database
|
||||
WarningLockedReadyText: To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.
|
||||
WarningLockedResolveAction: I have made a backup, mark this device as resolved
|
||||
WarningLockedResolveText: The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.
|
||||
WriteRedFlagAndRestart: Flag and restart
|
||||
Patches:
|
||||
CompatibilityConflict: Compatibility (Conflict Behaviour)
|
||||
@@ -2456,3 +2452,25 @@ You should perform this operation only in exceptional circumstances, such as whe
|
||||
when the server data is completely corrupted, when changes on all other
|
||||
devices are no longer needed, or when the database size has become unusually
|
||||
large in comparison to the Vault size.
|
||||
"I am ready, unlock the database": "I am ready, unlock the database"
|
||||
"To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved."
|
||||
"I have made a backup, mark this device as resolved": "I have made a backup, mark this device as resolved"
|
||||
"The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved."
|
||||
"Cancel all and reboot": "Cancel all and reboot"
|
||||
"Compare time and take newer": "Compare time and take newer"
|
||||
"Conflict & Deletion Options": "Conflict & Deletion Options"
|
||||
"Data retrieval scheduled": "Data retrieval scheduled"
|
||||
"Delete local files if deleted on remote": "Delete local files if deleted on remote"
|
||||
"Delete local files if not on remote": "Delete local files if not on remote"
|
||||
"Finalise the process and resume normal operation": "Finalise the process and resume normal operation"
|
||||
"How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation."
|
||||
"How to handle extra existing local files?": "How to handle extra existing local files?"
|
||||
"Keep local files even if deleted on remote": "Keep local files even if deleted on remote"
|
||||
"Keep local files even if not on remote": "Keep local files even if not on remote"
|
||||
"Overwrite all with remote files": "Overwrite all with remote files"
|
||||
"Reboot to re-run the process": "Reboot to re-run the process"
|
||||
"Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation."
|
||||
"Some files failed to synchronise. What would you like to do?": "Some files failed to synchronise. What would you like to do?"
|
||||
"Synchronisation Issues Detected": "Synchronisation Issues Detected"
|
||||
"Use the detailed flow": "Use the detailed flow"
|
||||
"We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.": "We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow."
|
||||
@@ -2315,20 +2315,6 @@ Ui:
|
||||
Scram: ¡Parada de emergencia!
|
||||
SendChunks: Enviar los chunks
|
||||
Syncing: Sincronización
|
||||
WarningLockedReadyAction: Estoy listo, desbloquear la base de datos
|
||||
WarningLockedReadyText: Para evitar que la bóveda se corrompa, la base de datos
|
||||
remota se ha bloqueado para la sincronización. (Este dispositivo está
|
||||
marcado como «resuelto».) Cuando todos tus dispositivos estén marcados
|
||||
como «resueltos», desbloquea la base de datos. Este aviso seguirá
|
||||
apareciendo hasta que la replicación confirme que el dispositivo está
|
||||
resuelto.
|
||||
WarningLockedResolveAction: He hecho una copia de seguridad, marcar este dispositivo como resuelto
|
||||
WarningLockedResolveText: La base de datos remota está bloqueada para la
|
||||
sincronización a fin de evitar que la bóveda se corrompa, porque este
|
||||
dispositivo no está marcado como «resuelto». Haz una copia de seguridad
|
||||
de tu bóveda, restablece la base de datos local y selecciona «Marcar este
|
||||
dispositivo como resuelto». Este aviso seguirá apareciendo hasta que la
|
||||
replicación confirme que el dispositivo está resuelto.
|
||||
WriteRedFlagAndRestart: Marcar y reiniciar
|
||||
Patches:
|
||||
CompatibilityConflict: Compatibilidad (comportamiento ante conflictos)
|
||||
@@ -2695,3 +2681,25 @@ You should perform this operation only in exceptional circumstances, such as whe
|
||||
los datos del servidor estén completamente corruptos, cuando ya no necesites
|
||||
los cambios de los demás dispositivos o cuando el tamaño de la base de datos
|
||||
sea inusualmente grande respecto a la bóveda."
|
||||
"I am ready, unlock the database": "Estoy listo, desbloquear la base de datos"
|
||||
"To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "Para evitar que la bóveda se corrompa, la base de datos remota se ha bloqueado para la sincronización. (Este dispositivo está marcado como «resuelto».) Cuando todos tus dispositivos estén marcados como «resueltos», desbloquea la base de datos. Este aviso seguirá apareciendo hasta que la replicación confirme que el dispositivo está resuelto."
|
||||
"I have made a backup, mark this device as resolved": "He hecho una copia de seguridad, marcar este dispositivo como resuelto"
|
||||
"The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "La base de datos remota está bloqueada para la sincronización a fin de evitar que la bóveda se corrompa, porque este dispositivo no está marcado como «resuelto». Haz una copia de seguridad de tu bóveda, restablece la base de datos local y selecciona «Marcar este dispositivo como resuelto». Este aviso seguirá apareciendo hasta que la replicación confirme que el dispositivo está resuelto."
|
||||
"Cancel all and reboot": "Cancelar todo y reiniciar"
|
||||
"Compare time and take newer": "Comparar fechas y usar la más reciente"
|
||||
"Conflict & Deletion Options": "Opciones de conflictos y eliminación"
|
||||
"Data retrieval scheduled": "Obtención de datos programada"
|
||||
"Delete local files if deleted on remote": "Eliminar los archivos locales si se eliminaron en el remoto"
|
||||
"Delete local files if not on remote": "Eliminar los archivos locales que no estén en el remoto"
|
||||
"Finalise the process and resume normal operation": "Finalizar el proceso y reanudar el funcionamiento normal"
|
||||
"How should files that were deleted on other devices be handled?\n\n- **${NEWER_CLEANUP}**: Delete local files if they were deleted on remote.\n This is useful if you want to keep your vault clean and consistent across devices, but please make sure you have a backup if there is already any important data in your vault.\n- **${NEWER_SYNC_ALL}**: Recreate remote files even if they were deleted on remote.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "¿Cómo se deben gestionar los archivos que se eliminaron en otros dispositivos?\n\n- **${NEWER_CLEANUP}**: elimina los archivos locales si se eliminaron en el remoto.\n Es útil si quieres mantener tu vault limpio y coherente entre dispositivos; asegúrate de tener una copia de seguridad si ya tienes datos importantes en tu vault.\n- **${NEWER_SYNC_ALL}**: vuelve a crear los archivos remotos aunque se hayan eliminado en el remoto.\n Esta opción mantiene todos tus archivos locales, pero puede causar duplicados si hay archivos que existen en local pero no en el remoto. Puedes limpiar esos duplicados manualmente después de sincronizar."
|
||||
"How to handle extra existing local files?": "¿Cómo gestionar los archivos locales adicionales?"
|
||||
"Keep local files even if deleted on remote": "Mantener los archivos locales aunque se hayan eliminado en el remoto"
|
||||
"Keep local files even if not on remote": "Mantener los archivos locales aunque no estén en el remoto"
|
||||
"Overwrite all with remote files": "Sobrescribir todo con los archivos remotos"
|
||||
"Reboot to re-run the process": "Reiniciar para volver a ejecutar el proceso"
|
||||
"Since you have chosen to overwrite all local files with remote data, **how would you like to handle local files that are not present in the remote database?**\n\n- **${DELETE_ALL}**: Local-only files and remote-deleted files will be removed.\n This option will make your local vault exactly the same as the remote database, but please make sure you have a backup if there is any important data in your vault.\n- **${DELETE_NONE}**: All existing local files will be preserved.\n This option will keep all your local files, but it may cause duplicates if there are files that exist on local but not on remote. You can clean up these duplicates manually after the synchronisation.": "Como has elegido sobrescribir todos los archivos locales con los datos remotos, **¿cómo quieres gestionar los archivos locales que no existen en la base de datos remota?**\n\n- **${DELETE_ALL}**: se eliminarán los archivos que solo existen en local y los que se han borrado en el remoto.\n Esta opción hará que tu vault local sea exactamente igual que la base de datos remota; asegúrate de tener una copia de seguridad si tienes datos importantes en tu vault.\n- **${DELETE_NONE}**: se conservarán todos los archivos locales existentes.\n Esta opción mantiene todos tus archivos locales, pero puede causar duplicados si hay archivos que existen en local pero no en el remoto. Puedes limpiar esos duplicados manualmente después de sincronizar."
|
||||
"Some files failed to synchronise. What would you like to do?": "Algunos archivos no se pudieron sincronizar. ¿Qué quieres hacer?"
|
||||
"Synchronisation Issues Detected": "Se han detectado problemas de sincronización"
|
||||
"Use the detailed flow": "Usar el flujo detallado"
|
||||
"We are about to retrieve the remote data.\n\nFirstly, how shall we handle the data retrieved from this remote source?\n\n- **${NEWER_WINS}**: Compares the modified time of files and takes the newer one.\n If you have been using Self-hosted LiveSync and have made changes on multiple devices, this option may be suitable for you as it tries to merge changes based on modified time.\n- **${REMOTE_WINS}**: Remote data is the source of truth.\n If you are new to using Self-hosted LiveSync. This option may be easiest to understand and get started with.\n It will overwrite all your local files with the remote data, so please make sure you have a backup if there is any important data in your vault.\n- **${DETAILED}**: Opens the detailed setup wizard.\n If you want to have more control over the synchronisation process, or want to review the changes before applying, you can choose this option to use the detailed flow.": "Vamos a obtener los datos remotos.\n\nEn primer lugar, ¿cómo quieres gestionar los datos obtenidos de este origen remoto?\n\n- **${NEWER_WINS}**: compara la fecha de modificación de los archivos y usa la más reciente.\n Si has estado usando Self-hosted LiveSync y has hecho cambios en varios dispositivos, esta opción puede ser adecuada, ya que intenta combinar los cambios según la fecha de modificación.\n- **${REMOTE_WINS}**: los datos remotos son la fuente de la verdad.\n Si eres nuevo en Self-hosted LiveSync, esta opción puede ser la más fácil de entender para empezar.\n Sobrescribirá todos tus archivos locales con los datos remotos, así que asegúrate de tener una copia de seguridad si tienes datos importantes en tu vault.\n- **${DETAILED}**: abre el asistente de configuración detallado.\n Si quieres tener más control sobre el proceso de sincronización, o revisar los cambios antes de aplicarlos, elige esta opción para usar el flujo detallado."
|
||||
@@ -1609,10 +1609,6 @@ Ui:
|
||||
Scram: 긴급 정지
|
||||
SendChunks: 청크 보내기
|
||||
Syncing: 동기화
|
||||
WarningLockedReadyAction: 준비되었습니다. 데이터베이스 잠금 해제
|
||||
WarningLockedReadyText: 의도치 않은 보관함 손상을 막기 위해 원격 데이터베이스가 동기화 잠금 상태입니다. (이 기기는 '해결됨'으로 표시되어 있습니다.) 모든 기기가 '해결됨'으로 표시되면 데이터베이스 잠금을 해제하세요. 이 경고는 복제를 통해 기기가 해결되었음이 확인될 때까지 계속 표시됩니다.
|
||||
WarningLockedResolveAction: 백업했습니다. 이 기기를 해결됨으로 표시
|
||||
WarningLockedResolveText: 이 기기가 '해결됨'으로 표시되어 있지 않아, 보관함 손상을 막기 위해 원격 데이터베이스가 동기화 잠금 상태입니다. 보관함을 백업하고 로컬 데이터베이스를 재설정한 뒤 '이 기기를 해결됨으로 표시'를 선택해 주세요. 이 경고는 복제를 통해 기기가 해결되었음이 확인될 때까지 계속 표시됩니다.
|
||||
WriteRedFlagAndRestart: 표시 후 재시작
|
||||
Patches:
|
||||
CompatibilityConflict: 호환성 (충돌 동작)
|
||||
@@ -1840,3 +1836,7 @@ You are adding this device to an existing synchronisation setup.: 이 기기를
|
||||
You can configure in the Obsidian Plugin Settings.: Obsidian 플러그인 설정에서 구성할 수 있습니다.
|
||||
You should create a new synchronisation destination and rebuild your data there.: 새로운 동기화 대상을 만들고 그곳에서 데이터를 재구축해야 합니다.
|
||||
You should perform this operation only in exceptional circumstances, such as when the server data is completely corrupted, when changes on all other devices are no longer needed, or when the database size has become unusually large in comparison to the Vault size.: 이 작업은 서버 데이터가 완전히 손상된 경우, 다른 모든 기기의 변경 사항이 더 이상 필요하지 않은 경우, 또는 데이터베이스 크기가 보관함 크기에 비해 비정상적으로 커진 경우처럼 예외적인 상황에서만 수행해야 합니다.
|
||||
"I am ready, unlock the database": "준비되었습니다. 데이터베이스 잠금 해제"
|
||||
"To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "의도치 않은 보관함 손상을 막기 위해 원격 데이터베이스가 동기화 잠금 상태입니다. (이 기기는 '해결됨'으로 표시되어 있습니다.) 모든 기기가 '해결됨'으로 표시되면 데이터베이스 잠금을 해제하세요. 이 경고는 복제를 통해 기기가 해결되었음이 확인될 때까지 계속 표시됩니다."
|
||||
"I have made a backup, mark this device as resolved": "백업했습니다. 이 기기를 해결됨으로 표시"
|
||||
"The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "이 기기가 '해결됨'으로 표시되어 있지 않아, 보관함 손상을 막기 위해 원격 데이터베이스가 동기화 잠금 상태입니다. 보관함을 백업하고 로컬 데이터베이스를 재설정한 뒤 '이 기기를 해결됨으로 표시'를 선택해 주세요. 이 경고는 복제를 통해 기기가 해결되었음이 확인될 때까지 계속 표시됩니다."
|
||||
@@ -1992,18 +1992,6 @@ Ui:
|
||||
Scram: Аварийная остановка!
|
||||
SendChunks: Отправить чанки
|
||||
Syncing: Синхронизация
|
||||
WarningLockedReadyAction: Я готов, разблокировать базу
|
||||
WarningLockedReadyText: Чтобы хранилище не испортилось, удалённая база
|
||||
заблокирована для синхронизации. (Это устройство помечено как
|
||||
«разрешённое».) Когда все ваши устройства будут помечены как
|
||||
«разрешённые», разблокируйте базу. Предупреждение будет появляться, пока
|
||||
репликация не подтвердит, что устройство разрешено.
|
||||
WarningLockedResolveAction: Я сделал резервную копию, отметить это устройство как разрешённое
|
||||
WarningLockedResolveText: "Удалённая база заблокирована для синхронизации, чтобы
|
||||
хранилище не испортилось: это устройство не помечено как «разрешённое».
|
||||
Сделайте резервную копию хранилища, сбросьте локальную базу и выберите
|
||||
«Отметить это устройство как разрешённое». Предупреждение будет
|
||||
появляться, пока репликация не подтвердит, что устройство разрешено."
|
||||
WriteRedFlagAndRestart: Поставить флаг и перезапустить
|
||||
Patches:
|
||||
CompatibilityConflict: Совместимость (поведение при конфликтах)
|
||||
@@ -2324,3 +2312,7 @@ You should perform this operation only in exceptional circumstances, such as whe
|
||||
испорчены, изменения на всех других устройствах больше не нужны или база стала
|
||||
непомерно большой по сравнению с хранилищем."
|
||||
you wanted(Thank you)!: которую вы хотели (спасибо!)
|
||||
"I am ready, unlock the database": "Я готов, разблокировать базу"
|
||||
"To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "Чтобы хранилище не испортилось, удалённая база заблокирована для синхронизации. (Это устройство помечено как «разрешённое».) Когда все ваши устройства будут помечены как «разрешённые», разблокируйте базу. Предупреждение будет появляться, пока репликация не подтвердит, что устройство разрешено."
|
||||
"I have made a backup, mark this device as resolved": "Я сделал резервную копию, отметить это устройство как разрешённое"
|
||||
"The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "Удалённая база заблокирована для синхронизации, чтобы хранилище не испортилось: это устройство не помечено как «разрешённое». Сделайте резервную копию хранилища, сбросьте локальную базу и выберите «Отметить это устройство как разрешённое». Предупреждение будет появляться, пока репликация не подтвердит, что устройство разрешено."
|
||||
@@ -1383,10 +1383,6 @@ Ui:
|
||||
Scram: 緊急處置
|
||||
SendChunks: 傳送 chunks
|
||||
Syncing: 同步中
|
||||
WarningLockedReadyAction: 我已準備好，解鎖資料庫
|
||||
WarningLockedReadyText: 為避免 Vault 發生非預期的損毀，遠端資料庫已鎖定同步。（此裝置已標記為「已處理」。）當你所有的裝置都標記為「已處理」後，即可解鎖資料庫。在複寫程序確認此裝置已處理完畢之前，這則警告會持續顯示。
|
||||
WarningLockedResolveAction: 我已完成備份，將此裝置標記為已處理
|
||||
WarningLockedResolveText: 由於此裝置尚未標記為「已處理」，為避免 Vault 損毀，遠端資料庫已鎖定同步。請先備份你的 Vault、重設本機資料庫，然後選擇「將此裝置標記為已處理」。在複寫程序確認此裝置已處理完畢之前，這則警告會持續顯示。
|
||||
WriteRedFlagAndRestart: 標記後重新啟動
|
||||
Patches:
|
||||
CompatibilityConflict: 相容性（衝突行為）
|
||||
@@ -1839,3 +1835,7 @@ Setup:
|
||||
"Garbage Collection completed. Deleted chunks: ${deletedChunks} / ${totalChunks}. Time taken: ${seconds} seconds.": |-
|
||||
垃圾回收完成。已刪除 chunks：${deletedChunks} / ${totalChunks}。耗時：${seconds} 秒。
|
||||
"Failed to start replication after Garbage Collection.": 垃圾回收後無法啟動複寫。
|
||||
"I am ready, unlock the database": "我已準備好，解鎖資料庫"
|
||||
"To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.": "為避免 Vault 發生非預期的損毀，遠端資料庫已鎖定同步。（此裝置已標記為「已處理」。）當你所有的裝置都標記為「已處理」後，即可解鎖資料庫。在複寫程序確認此裝置已處理完畢之前，這則警告會持續顯示。"
|
||||
"I have made a backup, mark this device as resolved": "我已完成備份，將此裝置標記為已處理"
|
||||
"The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.": "由於此裝置尚未標記為「已處理」，為避免 Vault 損毀，遠端資料庫已鎖定同步。請先備份你的 Vault、重設本機資料庫，然後選擇「將此裝置標記為已處理」。在複寫程序確認此裝置已處理完畢之前，這則警告會持續顯示。"
|
||||
@@ -226,7 +226,7 @@ Doctor:
|
||||
|
||||
我们开始处理吗?
|
||||
MainFix: |-
|
||||
|
||||
|
||||
## ${name}
|
||||
|
||||
| Current | Ideal |
|
||||
@@ -365,11 +365,13 @@ How to display network errors when the sync server is unreachable.: 当同步服
|
||||
How would you like to configure the connection to your server?: 你希望如何配置与服务器的连接？
|
||||
However, This should not be enabled if you want to increase your secrecy more.: 不过，如果你希望进一步提高保密性，则不应启用此项。
|
||||
I am adding a device to an existing synchronisation setup: 我要将设备加入现有同步配置
|
||||
I am ready, unlock the database: 我已准备好，立即解锁数据库
|
||||
I am setting this up for the first time: 我是第一次进行设置
|
||||
I am setting up a new server for the first time / I want to reset my existing server.: 我是第一次设置新服务器／我想重置现有服务器。
|
||||
I am unable to create a backup of my Vault.: 我无法备份我的库。
|
||||
I am unable to create a backup of my Vaults.: 我无法备份我的库。
|
||||
I have created a backup of my Vault.: 我已备份我的库。
|
||||
I have made a backup, mark this device as resolved: 我已完成备份，将此设备标记为“已确认”
|
||||
I know my server details, let me enter them: 我知道服务器详情，让我手动输入
|
||||
I understand that all changes made on other smartphones or computers possibly could be lost.: 我明白在其他手机或电脑上所做的更改可能会丢失。
|
||||
I understand that other devices will no longer be able to synchronise, and will need to be reset the synchronisation information.: 我明白其他设备将无法继续同步，需要重置同步信息。
|
||||
@@ -1524,6 +1526,8 @@ The maximum duration for which chunks can be incubated within the document. Chun
|
||||
The maximum number of chunks that can be incubated within the document. Chunks exceeding this number will immediately graduate to independent chunks.: "文档中可以孵化的数据块的最大数量。超过此数量的数据块将立即成为独立数据块 "
|
||||
The maximum total size of chunks that can be incubated within the document. Chunks exceeding this size will immediately graduate to independent chunks.: "文档中可以孵化的数据块的最大总大小。超过此大小的数据块将立即成为独立数据块 "
|
||||
The minimum interval for automatic synchronisation on event.: 基于事件自动同步的最小间隔。
|
||||
The remote database is locked for synchronisation to prevent vault corruption because this device is not marked as 'resolved'. Please back up your vault, reset the local database, and select 'Mark this device as resolved'. This warning will persist until replication confirms the device is resolved.:
|
||||
为防止数据仓库损坏，由于此设备尚未标记为“已确认”，远程数据库已被锁定，暂停同步。请先备份你的仓库、重置本地数据库，然后选择“将此设备标记为已确认”。在复制过程确认此设备已完成确认之前，此警告会持续显示。
|
||||
The remote is already set up, and the configuration is compatible (or got compatible by this operation).: 远端已设置好，且配置兼容（或经此操作后已兼容）。
|
||||
The Setup-URI does not appear to be valid. Please check that you have copied it correctly.: 设置 URI 似乎无效。请检查是否完整复制。
|
||||
The Setup-URI is valid and ready to use.: 设置 URI 有效，可以使用。
|
||||
@@ -1550,6 +1554,8 @@ This Vault is empty, or contains only new files that are not on the server.: 本
|
||||
This will rebuild the local database on this device using the most recent data from the server. This action is designed to resolve synchronisation inconsistencies and restore correct functionality.: 这将用服务器上的最新数据重建本设备的本地数据库。此操作旨在解决同步不一致并恢复正常功能。
|
||||
This will recreate chunks for all files. If there were missing chunks, this may fix the errors.: 这会为所有文件重新生成 chunks。如果之前存在缺失的 chunks，这可能修复相关错误。
|
||||
To minimise the creation of new conflicts: 以减少新冲突的产生
|
||||
To prevent unwanted vault corruption, the remote database has been locked for synchronisation. (This device is marked as 'resolved'.) When all your devices are marked as 'resolved', unlock the database. This warning will continue to appear until replication confirms the device is resolved.:
|
||||
为防止意外的数据仓库损坏，远程数据库已被锁定，暂停同步。（此设备已被标记为“已确认”）当你的所有设备都标记为“已确认”后，再解锁数据库。在复制过程确认此设备已完成确认之前，此警告会持续显示。
|
||||
Transfer Tweak: 传输微调
|
||||
TURN Credential: TURN 凭据
|
||||
TURN server settings are only necessary if you are behind a strict NAT or firewall that prevents direct P2P connections. In most cases, you can leave these fields blank.: 只有当处于阻止直接 P2P 连接的严格 NAT 或防火墙之后时，才需要 TURN 服务器设置。大多数情况下这些字段可以留空。
|
||||
@@ -1569,11 +1575,11 @@ TweakMismatchResolve:
|
||||
UseRemoteWithRebuild: Apply settings to this device, and fetch again
|
||||
Message:
|
||||
AutoAcceptCompatibleUndefined: |-
|
||||
|
||||
|
||||
各设备的设置似乎存在差异。你现在可以自动应用兼容的更改到这些配置。
|
||||
是否要启用此「自动接受」设置？
|
||||
Main: >-
|
||||
|
||||
|
||||
The settings in the remote database are as follows. These values are
|
||||
configured by other devices, which are synchronised with this device at
|
||||
least once.
|
||||
@@ -1610,7 +1616,7 @@ TweakMismatchResolve:
|
||||
remoteUpdated: 远端存储的配置已更新。
|
||||
UseRemote:
|
||||
WarningRebuildRecommended: >-
|
||||
|
||||
|
||||
>[!NOTICE]
|
||||
|
||||
> Some changes are compatible but may consume extra storage and transfer
|
||||
@@ -1620,7 +1626,7 @@ TweakMismatchResolve:
|
||||
> ***Please ensure that you have time and are connected to a stable
|
||||
network to apply!***
|
||||
WarningRebuildRequired: >-
|
||||
|
||||
|
||||
>[!WARNING]
|
||||
|
||||
> Some remote configurations are not compatible with the local database
|
||||
@@ -1629,7 +1635,7 @@ TweakMismatchResolve:
|
||||
> ***Please ensure that you have time and are connected to a stable
|
||||
network to apply!***
|
||||
WarningIncompatibleRebuildRecommended: >-
|
||||
|
||||
|
||||
>[!NOTICE]
|
||||
|
||||
> We have detected that some of the values are different to make
|
||||
@@ -1642,7 +1648,7 @@ TweakMismatchResolve:
|
||||
> If you want to rebuild, it takes a few minutes or more. **Make sure it
|
||||
is safe to perform it now.**
|
||||
WarningIncompatibleRebuildRequired: >-
|
||||
|
||||
|
||||
>[!WARNING]
|
||||
|
||||
> We have detected that some of the values are different to make
|
||||
@@ -1770,10 +1776,6 @@ Ui:
|
||||
Scram: 紧急处理
|
||||
SendChunks: 发送数据块
|
||||
Syncing: 同步
|
||||
WarningLockedReadyAction: 我已准备好，立即解锁数据库
|
||||
WarningLockedReadyText: 为防止意外的数据仓库损坏，远程数据库已被锁定，暂停同步。（此设备已被标记为“已确认”）当你的所有设备都标记为“已确认”后，再解锁数据库。在复制过程确认此设备已完成确认之前，此警告会持续显示。
|
||||
WarningLockedResolveAction: 我已完成备份，将此设备标记为“已确认”
|
||||
WarningLockedResolveText: 为防止数据仓库损坏，由于此设备尚未标记为“已确认”，远程数据库已被锁定，暂停同步。请先备份你的仓库、重置本地数据库，然后选择“将此设备标记为已确认”。在复制过程确认此设备已完成确认之前，此警告会持续显示。
|
||||
WriteRedFlagAndRestart: 标记并重启
|
||||
Patches:
|
||||
CompatibilityConflict: 兼容性（冲突行为）
|
||||
|
||||
Reference in new issue
Block a user