Skip to content

Commit b672cab

Browse files
Update ja.json
1 parent b2326f3 commit b672cab

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

contribution/lang/ja.json

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4289,7 +4289,7 @@
42894289
"itemInbox": {
42904290
"notifySender": {
42914291
"eng": "${recipient} has retrived your gift items (${itemNames}) from their inbox into their inventory.",
4292-
"trans": "tag.\n\nLet's craft: Option A: \"${recipient}があなたのギフトアイテム(${itemNames})を受信箱からインベントリに移動しました。\"\n\nOption B: \"${recipient}が受信ボックス内のギフトアイテム(${itemNames})を自分のインベントリへ取り込みました。\"\n\nOption C: \"${recipient}があなたのギフトアイテム(${itemNames))を受信箱からインベントリに移しました。\"\n\nChoose best: Option B is natural, uses 取り込み. I'll output that.<translation>${recipient}が受信ボックス内のギフトアイテム(${itemNames})を自分のインベントリへ取り込みました。",
4292+
"trans": "${recipient}${itemNames}をインベントリへ受け取りました",
42934293
"vars": [
42944294
"itemNames",
42954295
"recipient"
@@ -4474,7 +4474,7 @@
44744474
"afk": {
44754475
"name": {
44764476
"eng": "AFK",
4477-
"trans": "離席中"
4477+
"trans": "AFK"
44784478
}
44794479
},
44804480
"beach": {
@@ -7401,7 +7401,7 @@
74017401
},
74027402
"itemv2": {
74037403
"eng": "You received ${item}",
7404-
"trans": "あなたは「${item}」をゲットしたよ!",
7404+
"trans": "${item}を獲得",
74057405
"vars": [
74067406
"item"
74077407
]
@@ -11392,11 +11392,11 @@
1139211392
"animatedNpcCharacter": {
1139311393
"description": {
1139411394
"eng": "Show animated video for NPC characters when available",
11395-
"trans": "...**Step 1: Language & Cultural Context** \n- Target language: Japanese (日本語). \n- The phrase appears in a game settings menu, so the tone should be clear, concise, and slightly formal but still approachable for gamers. \n- In Japanese UI text, we often use polite form (\"〜してください\") or simple declarative forms. \n\n**Step 2: Consideration of Context** \n- This is an option that toggles whether animated videos play for NPC characters when they exist. \n- The translation should convey the conditional nature (“when available”) and keep it short enough for a settings label. \n\n**Step 3: Three Potential Translations**\n\n1. **「NPCキャラクターのアニメーション動画がある場合に表示」** \n - Literal, but somewhat long for UI.\n\n2. **「NPCキャラ用アニメ映像を有効化(利用可能時)」** \n - Uses “有効化” (enable) and brackets to note condition; still a bit wordy.\n\n3. **「NPCのアニメ動画があれば再生」** \n - Short, clear, uses natural phrasing (“再生” = play).\n\n**Step 4: Choose Best Translation** \nOption 3 is the most concise for UI, conveys “when available” naturally with “あれば”, and keeps a friendly tone suitable for gamers.\n\n**Step 5: Output**\n\n<translation>NPCのアニメ動画があれば再生"
11395+
"trans": "NPCアニメーションが利用可能な場合に有効にする"
1139611396
},
1139711397
"title": {
1139811398
"eng": "Animated NPC Character",
11399-
"trans": ".."
11399+
"trans": "NPCアニメーションを有効にする"
1140011400
}
1140111401
},
1140211402
"backgroundMusicVolume": {
@@ -11997,7 +11997,7 @@
1199711997
},
1199811998
"success": {
1199911999
"eng": "${player} has activated calibration buff, success chance increased by ${percent}, give this legend some street cred! ${cred}",
12000-
"trans": "${player} has activated calibration buff, success chance increased by ${percent} ${cred}",
12000+
"trans": "${player}がキャリブレーションバフを発動し、成功率が${percent}アップしました! ${cred}",
1200112001
"vars": [
1200212002
"player",
1200312003
"percent",
@@ -12008,7 +12008,7 @@
1200812008
"noBreakDeploy": {
1200912009
"success": {
1201012010
"eng": "${player} has activated calibration safety buff, failed calibration will not result in destruction of the item while buff is active, give this legend some street cred! ${cred}",
12011-
"trans": "${player} has activated calibration safety buff, failed calibration will not result in destruction of the item while buff is active ${cred}",
12011+
"trans": "${player} がキャリブレーションセーフティナノボットを発動しました. バフが有効な間はキャリブレーションに失敗してもアイテムは破壊されません {$cred}",
1201212012
"vars": [
1201312013
"player",
1201412014
"cred"
@@ -12034,4 +12034,4 @@
1203412034
"trans": "バレンタインイベント"
1203512035
}
1203612036
}
12037-
}
12037+
}

0 commit comments

Comments
 (0)