- Overhaul Japanese translation catalogue and synchronize with current documentation
- Localise pending UI labels across dialogues, panels, and settings
- Add Japanese translation mapping for provisional LiveSync messages
- Update and refine all Japanese documentation files
- Strip weak ETag prefix in ObsHttpHandler for object storage compatibility
"The fetch flag does not contain one supported selection. Choose new options and continue with the current remote?\n\nCurrent remote: ${REMOTE}\n\nThe flag contents will remain unchanged. The new choices apply only to this attempt; another restart will ask again. Completing or cancelling the fetch removes the flag.":
"The fetch flag does not contain one supported selection. Choose new options and continue with the current remote?\n\nCurrent remote: ${REMOTE}\n\nThe flag contents will remain unchanged. The new choices apply only to this attempt; another restart will ask again. Completing or cancelling the fetch removes the flag.",
"Choose new options and continue":"Choose new options and continue",
"Batch database updates in LiveSync mode":"Batch database updates in LiveSync mode",
"Wait for a bounded local quiet period before processing file updates in LiveSync mode, reducing intermediate database updates while delaying their reflection to remote devices.":
"Wait for a bounded local quiet period before processing file updates in LiveSync mode, reducing intermediate database updates while delaying their reflection to remote devices.",
Apply:"Apply",
Add:"Add",
Revert:"Revert",
"Vault history":"Vault history",
"From:":"From:",
"To:":"To:",
"Info:":"Info:",
"To stop the countdown, tap anywhere on the dialogue":"To stop the countdown, tap anywhere on the dialogue",
"No joined devices are recorded on this remote.":"このリモートには参加済みデバイスが記録されていません。",
"Locked out":"接続拒否",
"Loading joined devices…":"参加済みデバイスを読み込んでいます…",
"Last recorded":"最終記録日時",
"Joined devices could not be updated. Refresh the list and try again. If the remote configuration has changed, close this dialogue and open Joined devices again.":
"Synchronisation between different plug-in versions is generally safe unless the connection is explicitly blocked. However, it may be less efficient or use more storage, and P2P synchronisation may be unavailable.":
"After restarting, select an online source device for the initial Fetch. The local LiveSync database on this device will be rebuilt from that source. Unsynchronised files in this Vault may conflict with the fetched data.":
"Restart this device, then choose the source device when P2P Rebuild opens.":
"このデバイスを再起動してください。P2P 再構築が開いたら、ソースデバイスを選択します。",
"Restart and Select Source Device":"再起動してソースデバイスを選択",
"P2P Status pane":"P2P ステータスペイン",
"No central data-storage server is required, but a signalling relay is required for peer discovery. Both devices must be online at the same time. Vault data travels through the encrypted P2P connection, not through the signalling relay. Some features may be limited.":
"Use the project's public signalling relay":"プロジェクトの公開シグナリングリレーを使用",
"The project's public signalling relay is a best-effort convenience operated by the project author. It does not store Vault contents, but signalling metadata may be visible to the relay. Availability and log retention are not guaranteed. You can replace it with your own Nostr-compatible relay.":
"Learn more about P2P connections":"P2P 接続について詳しく見る",
"Learn more about signalling and TURN":"シグナリングと TURN について詳しく見る",
"WebRTC encrypts data between your devices, including when it passes through TURN. The TURN provider cannot read the transferred data. It can see network addresses and traffic volume.":
"Smaller messages can improve compatibility on paths which fragment or drop larger WebRTC messages. This setting limits outgoing P2P messages, so use a compatible profile on each sending device when required.":
"Announce changes automatically after connecting":"接続後に変更を自動通知",
"When enabled, this device notifies connected peers after a local change. The notification contains no Vault data; a peer which follows this device then fetches the change through the encrypted P2P connection.":
"Stop following changes from this device":"このデバイスからの変更受信を停止",
"Follow changes from this device":"このデバイスからの変更を受信",
"Synchronise when this device connects":"このデバイスの接続時に同期",
"Follow whenever this device connects":"このデバイスが接続するたびに変更を受信",
"Include in the P2P synchronisation command":"P2P 同期コマンドに含める",
"More actions for ${DEVICE}":"${DEVICE} のその他の操作",
"Use this device's settings":"このデバイスの設定を使用",
Retry:"再試行",
"No Synchronisation Settings Found":"同期設定が見つかりません",
"The selected remote has no saved synchronisation settings. This is normal for a new remote. Use this device's settings, or cancel if you expected existing settings.":
"Could not read the remote's synchronisation settings. Retry, or continue the overwrite with this device's settings. A working connection is still required.":
"Skips checking and applying synchronisation settings from the remote.":
"リモートの同期設定の確認と適用をスキップします。",
"Change CouchDB server setting":"CouchDB サーバー設定を変更",
"Change CouchDB server setting '${SETTING}' to '${VALUE}'?":
"CouchDB サーバー設定「${SETTING}」を「${VALUE}」に変更しますか？",
"TURN relay only requires TURN configuration. Connection path has been restored to Automatic.":
"TURN リレーのみを使うには TURN の設定が必要です。接続経路を自動に戻しました。",
"This file has unresolved conflicts.":"このファイルには未解決の競合があります。",
"This file has ${COUNT} unresolved versions. They will be reviewed one pair at a time.":
"このファイルには未解決の版が ${COUNT} 件あります。1組ずつ確認します。",
"Sync now":"今すぐ同期",
"Apply pending changes now":"保留中の変更を今すぐ適用",
"Copy database information for the active file":"アクティブなファイルのデータベース情報をコピー",
"Copy database information for a file":"ファイルのデータベース情報をコピー",
"Copy revision, conflict, and local chunk availability information, including document and chunk identifiers but not file contents.":
"ファイルの内容を含めずに、ドキュメント ID やチャンク ID などのリビジョン、競合、ローカルのチャンク有無に関する情報をコピーします。",
"Choose file":"ファイルを選択",
"Choose a file to inspect":"確認するファイルを選択",
"Database information for ${FILE}":"${FILE} のデータベース情報",
"All revisions and chunk availability below are a snapshot of this device's local database; the remote is not queried. Review the Vault-relative path, document identifier, content-derived chunk identifiers, and metadata before sharing this report. File contents are omitted.":
"Discard database branch ${REVISION} of ${FILE}? This creates a logical deletion for that exact live branch. The current Vault file will not be changed.":
"Discard database revision ${REVISION} of ${FILE}? This creates a logical deletion for that exact live revision. Missing content cannot be recovered by this action.":
"Revision metadata is unavailable on this device":"このデバイスではリビジョンのメタデータを利用できません",
"Shared ancestor ${REVISION} is not readable on this device. Automatic three-way merging may be unavailable, but the live revisions remain available for explicit review.":
"Resolve every conflict by modification time? This logically deletes every version except the newest one and cannot recover content which is already unavailable.":
"Resolve all conflicts by the newest version":"すべての競合を最も新しい版で解決",
"Inspect conflicts and file/database differences":"競合とファイル／データベース間の差異を調査",
"Scan Vault files and local-database Metadata for conflicts, missing chunks, identity mismatches, and differences. Each result provides actions for one exact entry or revision.":
"An exact target is already present; repair can remove the obsolete ID.":
"同一の対象がすでに存在するため、修復時に古い ID を削除できます。",
"Repair is available for this entry.":"この項目は修復できます。",
"Repair this Metadata document ID":"このメタデータドキュメント ID を修復",
"Repair Metadata ID":"メタデータ ID を修復",
"Keep unchanged":"変更せずに保持",
"This moves one local Metadata entry to the ID derived from its recorded path.\n\n**File:** `${FILE}` \n**Source:** `${SOURCE}@${REVISION}` \n**Target:** `${TARGET}`\n\nThe target is verified before the source is removed. Its CouchDB revision ancestry cannot be preserved.\n\n> [!warning] Before repairing\n> - Back up this device.\n> - If file-name case or path obfuscation was intentionally changed for the whole database, use Rebuild instead.\n> - If other devices share this database, pause them, allow this device to upload the repair, then resume them one at a time.":
"Metadata document ID repair and the ordinary Vault scan completed. Run this inspection again after synchronisation.":
"メタデータドキュメント ID の修復と通常の Vault スキャンが完了しました。同期後にこの調査を再実行してください。",
"Metadata document ID repair completed, but the ordinary Vault scan did not run. Keep synchronisation paused, resolve the scan condition, then run 'Scan storage and database again'.":
"メタデータドキュメント ID の修復は完了しましたが、通常の Vault スキャンは実行されませんでした。同期を一時停止したままスキャンを妨げている状態を解消し、「ストレージとデータベースを再スキャン」を実行してください。",
"The inspected state changed. No repair was performed; run inspection again.":
"調査対象の状態が変化しました。修復は行われていません。調査を再実行してください。",
"Repair stopped after creating the target. The source was retained. Run inspection again before retrying.":
"Repair Metadata document ID":"メタデータドキュメント ID を修復",
"Connection settings":"接続設定",
"Saved connections":"保存済みの接続",
"ID generation":"ID の生成",
"Keep current configuration":"現在の設定を維持",
"Set an ID key":"ID キーを設定",
"Current configuration: a saved ID key is used.":"現在の設定: 保存済みの ID キーを使用します。",
"Current configuration: the saved ID key is retained while E2EE is off.":
"現在の設定: E2EE が無効な間も保存済みの ID キーを保持します。",
"Current configuration: no ID key is saved. With E2EE enabled, keeping it uses legacy IDs tied to the E2EE passphrase.":
"現在の設定: ID キーは保存されていません。E2EE が有効な場合、現在の設定を維持すると E2EE パスフレーズに紐づく旧形式の ID を使用します。",
"Changing the E2EE passphrase changes IDs generated by the legacy configuration.":
"旧形式の設定では、E2EE パスフレーズを変更すると生成される ID も変わります。",
"This uses a saved key for new Chunk IDs and obfuscated Metadata document IDs, so changing the E2EE passphrase does not derive a new key automatically.":
"新しいチャンク ID と難読化されたメタデータドキュメント ID に保存済みのキーを使います。そのため、E2EE パスフレーズを変更しても新しいキーは自動導出されません。",
Configured:"設定済み",
"The saved ID key is configured. Its source cannot be shown again.":
"保存済みの ID キーが設定されています。キーの導出元を再表示することはできません。",
"Leave this input empty to keep the saved ID key.":
"保存済みの ID キーを維持するには、この欄を空のままにしてください。",
"Generate a random ID key":"ランダムな ID キーを生成",
"How to set the ID key":"ID キーの設定方法",
"Derive from current E2EE passphrase":"現在の E2EE パスフレーズから導出",
"Enter an ID source":"ID の導出元を入力",
"Import an ID recovery code":"ID 復旧コードをインポート",
"ID source":"ID の導出元",
"ID recovery code":"ID 復旧コード",
"Enter an ID recovery code":"ID 復旧コードを入力",
"Choose a long, unpredictable source. It is used once and cannot be shown again after saving. A recovery code can be displayed on this device later. This input also accepts a tagged recovery code.":
"The recovery code could not be copied. Select and copy the visible code instead.":
"復旧コードをコピーできませんでした。表示されているコードを選択してコピーしてください。",
"The ID key is derived from the current E2EE passphrase and saved separately. Changing that passphrase later does not change the saved ID key. To reduce the risk of guessing that passphrase from known IDs, use a separate, unpredictable ID source instead.":
"ID キーは現在の E2EE パスフレーズから導出され、別に保存されます。後からパスフレーズを変更しても、保存済みの ID キーは変わりません。既知の ID からパスフレーズを推測されるリスクを下げるには、別の推測されにくい ID の導出元を使用してください。",
"An ID source is required to enable this option.":"このオプションを有効にするには、ID の導出元が必要です。",
"The ID source or recovery code is invalid. Check it and try again.":
"ID の導出元または復旧コードが無効です。確認してもう一度お試しください。",
"Read normal-file Metadata and current conflicts locally and in CouchDB, then compare content for suspect groups. Choose original names or pseudonyms before starting.":
"Pseudonyms include a public salt, so guessed paths can be checked. Original names include private filenames. Reports omit file contents and credentials.":
"Inspect normal-file Metadata, current conflicts, and suspect content against the Vault. Remote inspection supports CouchDB. Older history is excluded; findings do not authorise deletion.":
"Apply these saved choices to the current remote?\n\nCurrent remote: ${REMOTE}\n\n- ${STAGE1}\n- ${STAGE2}\n\nThe fetch flag may remain after an interruption or an incomplete cleanup. Continue only if this fetch is still intended.":
"Saved fetch choices could not be read":"保存済みの取得設定を読み取れませんでした",
"The fetch flag does not contain one supported selection. Choose new options and continue with the current remote?\n\nCurrent remote: ${REMOTE}\n\nThe flag contents will remain unchanged. The new choices apply only to this attempt; another restart will ask again. Completing or cancelling the fetch removes the flag.":
"Choose new options and continue":"新しい選択肢を指定して続行",
"Batch database updates in LiveSync mode":"LiveSync モードでデータベース更新をバッチ処理",
"Wait for a bounded local quiet period before processing file updates in LiveSync mode, reducing intermediate database updates while delaying their reflection to remote devices.":
expect(firstPrompt).toContain("We are about to retrieve the remote data.");
// We can't easily check performFullScan call here because it's imported,
// but we can verify rebuilder was called.
});
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Chihiro WATANABE committed