@vantagesec/socc 0.1.13 → 0.1.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (127) hide show
  1. package/README.md +8 -8
  2. package/dist/cli.mjs +10734 -10807
  3. package/package.json +7 -8
  4. package/scripts/bootstrap-socc-soul.mjs +23 -1
  5. package/socc-canonical/.agents/generated/socc-agent-manifest.json +0 -231
  6. package/socc-canonical/.agents/generated/socc-agent.md +0 -256
  7. package/socc-canonical/.agents/rules/AGENT.md +0 -109
  8. package/socc-canonical/.agents/rules/AQL_REFERENCE.md +0 -40
  9. package/socc-canonical/.agents/rules/MEMORY.md +0 -19
  10. package/socc-canonical/.agents/rules/TOOLS.md +0 -48
  11. package/socc-canonical/.agents/soc-copilot/AGENTS.md +0 -28
  12. package/socc-canonical/.agents/soc-copilot/MEMORY.md +0 -20
  13. package/socc-canonical/.agents/soc-copilot/SKILL.md +0 -51
  14. package/socc-canonical/.agents/soc-copilot/SOUL.md +0 -31
  15. package/socc-canonical/.agents/soc-copilot/TOOLS.md +0 -33
  16. package/socc-canonical/.agents/soc-copilot/USER.md +0 -31
  17. package/socc-canonical/.agents/soc-copilot/identity.md +0 -7
  18. package/socc-canonical/.agents/soc-copilot/references/evidence-rules.md +0 -30
  19. package/socc-canonical/.agents/soc-copilot/references/intelligence-source-registry.md +0 -32
  20. package/socc-canonical/.agents/soc-copilot/references/ioc-extraction.md +0 -25
  21. package/socc-canonical/.agents/soc-copilot/references/knowledge-ingestion-policy.md +0 -34
  22. package/socc-canonical/.agents/soc-copilot/references/mitre-guidance.md +0 -21
  23. package/socc-canonical/.agents/soc-copilot/references/output-contract.md +0 -31
  24. package/socc-canonical/.agents/soc-copilot/references/security-json-patterns.md +0 -129
  25. package/socc-canonical/.agents/soc-copilot/references/telemetry-investigation-patterns.md +0 -39
  26. package/socc-canonical/.agents/soc-copilot/schemas/analysis_response.json +0 -119
  27. package/socc-canonical/.agents/soc-copilot/skills/code-review-excellence/SKILL.md +0 -538
  28. package/socc-canonical/.agents/soc-copilot/skills/cybersecurity-analyst/QUICK_REFERENCE.md +0 -263
  29. package/socc-canonical/.agents/soc-copilot/skills/cybersecurity-analyst/README.md +0 -243
  30. package/socc-canonical/.agents/soc-copilot/skills/cybersecurity-analyst/SKILL.md +0 -1707
  31. package/socc-canonical/.agents/soc-copilot/skills/cybersecurity-analyst/tests/quiz.md +0 -472
  32. package/socc-canonical/.agents/soc-copilot/skills/data-visualization/SKILL.md +0 -304
  33. package/socc-canonical/.agents/soc-copilot/skills/deep-research/SKILL.md +0 -192
  34. package/socc-canonical/.agents/soc-copilot/skills/excel-analysis/SKILL.md +0 -247
  35. package/socc-canonical/.agents/soc-copilot/skills/find-skills/SKILL.md +0 -133
  36. package/socc-canonical/.agents/soc-copilot/skills/humanizer/README.md +0 -120
  37. package/socc-canonical/.agents/soc-copilot/skills/humanizer/SKILL.md +0 -439
  38. package/socc-canonical/.agents/soc-copilot/skills/malware-behavior/SKILL.md +0 -54
  39. package/socc-canonical/.agents/soc-copilot/skills/mitre/SKILL.md +0 -200
  40. package/socc-canonical/.agents/soc-copilot/skills/observability-logs-search/SKILL.md +0 -237
  41. package/socc-canonical/.agents/soc-copilot/skills/observability-logs-search/references/log-search-reference.md +0 -76
  42. package/socc-canonical/.agents/soc-copilot/skills/payload-triage/SKILL.md +0 -53
  43. package/socc-canonical/.agents/soc-copilot/skills/phishing-analysis/SKILL.md +0 -51
  44. package/socc-canonical/.agents/soc-copilot/skills/prd/SKILL.md +0 -143
  45. package/socc-canonical/.agents/soc-copilot/skills/remembering-conversations/MCP-TOOLS.md +0 -137
  46. package/socc-canonical/.agents/soc-copilot/skills/remembering-conversations/SKILL.md +0 -65
  47. package/socc-canonical/.agents/soc-copilot/skills/sequential-thinking/README.md +0 -118
  48. package/socc-canonical/.agents/soc-copilot/skills/sequential-thinking/SKILL.md +0 -93
  49. package/socc-canonical/.agents/soc-copilot/skills/sequential-thinking/references/advanced.md +0 -122
  50. package/socc-canonical/.agents/soc-copilot/skills/sequential-thinking/references/examples.md +0 -274
  51. package/socc-canonical/.agents/soc-copilot/skills/soc-generalist/SKILL.md +0 -53
  52. package/socc-canonical/.agents/soc-copilot/skills/suspicious-url/SKILL.md +0 -51
  53. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/CREATION-LOG.md +0 -119
  54. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/SKILL.md +0 -296
  55. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/condition-based-waiting-example.ts +0 -158
  56. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/condition-based-waiting.md +0 -115
  57. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/defense-in-depth.md +0 -122
  58. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/find-polluter.sh +0 -63
  59. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/root-cause-tracing.md +0 -169
  60. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/test-academic.md +0 -14
  61. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/test-pressure-1.md +0 -58
  62. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/test-pressure-2.md +0 -68
  63. package/socc-canonical/.agents/soc-copilot/skills/systematic-debugging/test-pressure-3.md +0 -69
  64. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/SKILL.md +0 -284
  65. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/chinese-traditional.md +0 -535
  66. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/english.md +0 -372
  67. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/japanese.md +0 -515
  68. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/tools-resources.md +0 -527
  69. package/socc-canonical/.agents/soc-copilot/skills/translation-expertise/translation-challenges.md +0 -603
  70. package/socc-canonical/.agents/soc-copilot/skills/web-search/SKILL.md +0 -322
  71. package/socc-canonical/.agents/soc-copilot/skills.md +0 -21
  72. package/socc-canonical/.agents/workflows/SOP.md +0 -137
  73. package/socc-canonical/README.md +0 -10
  74. /package/{.claude → .socc}/agents/socc.md +0 -0
  75. /package/{.claude → .socc}/references/evidence-rules.md +0 -0
  76. /package/{.claude → .socc}/references/intelligence-source-registry.md +0 -0
  77. /package/{.claude → .socc}/references/ioc-extraction.md +0 -0
  78. /package/{.claude → .socc}/references/knowledge-ingestion-policy.md +0 -0
  79. /package/{.claude → .socc}/references/mitre-guidance.md +0 -0
  80. /package/{.claude → .socc}/references/output-contract.md +0 -0
  81. /package/{.claude → .socc}/references/security-json-patterns.md +0 -0
  82. /package/{.claude → .socc}/references/telemetry-investigation-patterns.md +0 -0
  83. /package/{.claude → .socc}/rules/socc-business-rules.md +0 -0
  84. /package/{.claude → .socc}/skills/code-review-excellence/SKILL.md +0 -0
  85. /package/{.claude → .socc}/skills/cybersecurity-analyst/QUICK_REFERENCE.md +0 -0
  86. /package/{.claude → .socc}/skills/cybersecurity-analyst/README.md +0 -0
  87. /package/{.claude → .socc}/skills/cybersecurity-analyst/SKILL.md +0 -0
  88. /package/{.claude → .socc}/skills/cybersecurity-analyst/tests/quiz.md +0 -0
  89. /package/{.claude → .socc}/skills/data-visualization/SKILL.md +0 -0
  90. /package/{.claude → .socc}/skills/deep-research/SKILL.md +0 -0
  91. /package/{.claude → .socc}/skills/excel-analysis/SKILL.md +0 -0
  92. /package/{.claude → .socc}/skills/find-skills/SKILL.md +0 -0
  93. /package/{.claude → .socc}/skills/humanizer/README.md +0 -0
  94. /package/{.claude → .socc}/skills/humanizer/SKILL.md +0 -0
  95. /package/{.claude → .socc}/skills/malware-behavior/SKILL.md +0 -0
  96. /package/{.claude → .socc}/skills/mitre/SKILL.md +0 -0
  97. /package/{.claude → .socc}/skills/observability-logs-search/SKILL.md +0 -0
  98. /package/{.claude → .socc}/skills/observability-logs-search/references/log-search-reference.md +0 -0
  99. /package/{.claude → .socc}/skills/payload-triage/SKILL.md +0 -0
  100. /package/{.claude → .socc}/skills/phishing-analysis/SKILL.md +0 -0
  101. /package/{.claude → .socc}/skills/prd/SKILL.md +0 -0
  102. /package/{.claude → .socc}/skills/remembering-conversations/MCP-TOOLS.md +0 -0
  103. /package/{.claude → .socc}/skills/remembering-conversations/SKILL.md +0 -0
  104. /package/{.claude → .socc}/skills/sequential-thinking/README.md +0 -0
  105. /package/{.claude → .socc}/skills/sequential-thinking/SKILL.md +0 -0
  106. /package/{.claude → .socc}/skills/sequential-thinking/references/advanced.md +0 -0
  107. /package/{.claude → .socc}/skills/sequential-thinking/references/examples.md +0 -0
  108. /package/{.claude → .socc}/skills/soc-generalist/SKILL.md +0 -0
  109. /package/{.claude → .socc}/skills/suspicious-url/SKILL.md +0 -0
  110. /package/{.claude → .socc}/skills/systematic-debugging/CREATION-LOG.md +0 -0
  111. /package/{.claude → .socc}/skills/systematic-debugging/SKILL.md +0 -0
  112. /package/{.claude → .socc}/skills/systematic-debugging/condition-based-waiting-example.ts +0 -0
  113. /package/{.claude → .socc}/skills/systematic-debugging/condition-based-waiting.md +0 -0
  114. /package/{.claude → .socc}/skills/systematic-debugging/defense-in-depth.md +0 -0
  115. /package/{.claude → .socc}/skills/systematic-debugging/find-polluter.sh +0 -0
  116. /package/{.claude → .socc}/skills/systematic-debugging/root-cause-tracing.md +0 -0
  117. /package/{.claude → .socc}/skills/systematic-debugging/test-academic.md +0 -0
  118. /package/{.claude → .socc}/skills/systematic-debugging/test-pressure-1.md +0 -0
  119. /package/{.claude → .socc}/skills/systematic-debugging/test-pressure-2.md +0 -0
  120. /package/{.claude → .socc}/skills/systematic-debugging/test-pressure-3.md +0 -0
  121. /package/{.claude → .socc}/skills/translation-expertise/SKILL.md +0 -0
  122. /package/{.claude → .socc}/skills/translation-expertise/chinese-traditional.md +0 -0
  123. /package/{.claude → .socc}/skills/translation-expertise/english.md +0 -0
  124. /package/{.claude → .socc}/skills/translation-expertise/japanese.md +0 -0
  125. /package/{.claude → .socc}/skills/translation-expertise/tools-resources.md +0 -0
  126. /package/{.claude → .socc}/skills/translation-expertise/translation-challenges.md +0 -0
  127. /package/{.claude → .socc}/skills/web-search/SKILL.md +0 -0
@@ -1,603 +0,0 @@
1
- # Common Translation Challenges
2
-
3
- This document provides detailed examples and strategies for handling common translation challenges between English, Japanese, and Traditional Chinese.
4
-
5
- ## Challenge 1: Idioms and Expressions
6
-
7
- **Strategy**: Find equivalent expressions, not word-for-word translations. The goal is to convey the same meaning and impact in the target language, even if the imagery or metaphor changes completely.
8
-
9
- ### Example 1: "Break a leg"
10
-
11
- **Context**: Wishing someone good luck before a performance
12
-
13
- **Literal Translation Issues**:
14
-
15
- - **Japanese**: 「足を折って」(ashi wo otte) - Sounds like wishing harm on someone
16
- - **Chinese**: 「打斷腿」(daduan tui) - Violent and inappropriate
17
-
18
- **Correct Translation with Reasoning**:
19
-
20
- **Japanese**: 頑張って (ganbatte) - "Do your best"
21
-
22
- - **Why**: Standard encouragement phrase in Japanese culture
23
- - **Cultural note**: Japanese culture prefers direct encouragement over superstitious phrases
24
- - **Alternative**: 成功を祈ります (seikou wo inorimasu) - "I pray for your success" (more formal)
25
-
26
- **Chinese**: 加油 (jiayou) - "Add oil" (idiomatic: "Go for it")
27
-
28
- - **Why**: Common encouragement phrase that matches the supportive tone
29
- - **Alternative**: 祝你成功 (zhu ni chenggong) - "Wishing you success" (more formal)
30
- - **Regional note**: 加油 is universal across all Chinese-speaking regions
31
-
32
- ### Example 2: "It's raining cats and dogs"
33
-
34
- **Context**: Describing heavy rain
35
-
36
- **Literal Translation Issues**:
37
-
38
- - Would be completely incomprehensible in both Japanese and Chinese
39
- - Animal metaphors for weather differ across cultures
40
- - Direct translation would sound bizarre and confusing
41
-
42
- **Correct Translation with Reasoning**:
43
-
44
- **Japanese**: 土砂降りだ (doshaburi da) - "Dirt and sand pouring"
45
-
46
- - **Why**: Standard Japanese idiom for heavy rain
47
- - **Cultural note**: Uses earthy imagery of mud/landslide intensity
48
- - **Alternatives**:
49
- - バケツをひっくり返したような雨 (baketsu wo hikkuri kaeshita you na ame) - "Rain like overturned buckets" (more descriptive)
50
- - どしゃ降り (doshaburi) in hiragana for casual contexts
51
-
52
- **Chinese**: 傾盆大雨 (qingpen dayu) - "Overturning basin big rain"
53
-
54
- - **Why**: Classical four-character idiom (成語) for heavy rain
55
- - **Cultural note**: Uses water vessel imagery common in Chinese idioms
56
- - **Alternatives**:
57
- - 下大雨 (xia dayu) - "Big rain falling" (simpler, less idiomatic)
58
- - 滂沱大雨 (pangtuó dayu) - "Torrential rain" (literary)
59
-
60
- ### Example 3: "Piece of cake"
61
-
62
- **Context**: Something very easy to do
63
-
64
- **Literal Translation Issues**:
65
-
66
- - Food metaphors don't transfer between cultures
67
- - Each culture has different associations with cake
68
- - Cake as "luxury/special" varies across cultures
69
-
70
- **Correct Translation with Reasoning**:
71
-
72
- **Japanese**: 朝飯前 (asameshi mae) - "Before breakfast"
73
-
74
- - **Why**: Traditional Japanese idiom meaning something so easy it can be done before breakfast
75
- - **Cultural note**: Reflects Japanese value of early morning productivity
76
- - **Alternatives**:
77
- - 楽勝 (rakushou) - "Easy victory" (more casual, modern)
78
- - 簡単だよ (kantan da yo) - "It's simple" (direct but less idiomatic)
79
-
80
- **Chinese**: 小菜一碟 (xiaocai yidie) - "Small dish"
81
-
82
- - **Why**: Common idiom comparing easy tasks to a simple side dish
83
- - **Cultural note**: Uses food metaphor but with different food item (small dish vs. cake)
84
- - **Alternatives**:
85
- - 輕而易舉 (qing'er yijǔ) - "Light and easy to lift" (formal)
86
- - 易如反掌 (yi rú fan zhang) - "Easy as turning over palm" (classical)
87
-
88
- ### Example 4: "Spill the beans"
89
-
90
- **Context**: Reveal a secret
91
-
92
- **Literal Translation Issues**:
93
-
94
- - Bean-related metaphor doesn't exist in Japanese/Chinese
95
- - Would sound completely nonsensical if translated literally
96
- - No cultural connection between beans and secrets
97
-
98
- **Correct Translation with Reasoning**:
99
-
100
- **Japanese**: 秘密をばらす (himitsu wo barasu) - "Expose the secret"
101
-
102
- - **Why**: Direct and clear; Japanese often prefers clarity over metaphor in this context
103
- - **Alternatives**:
104
- - 口を滑らす (kuchi wo suberasu) - "Slip the mouth" (implies accidental revealing)
105
- - ネタバレする (netabare suru) - "Spoil" (modern slang, from internet culture)
106
-
107
- **Chinese**: 洩漏秘密 (xielou mimi) - "Leak the secret"
108
-
109
- - **Why**: Straightforward expression commonly used
110
- - **Alternatives**:
111
- - 說漏嘴 (shuo lou zui) - "Speak leaked mouth" (colloquial, implies accidental)
112
- - 揭露秘密 (jielu mimi) - "Reveal secret" (more formal)
113
-
114
- ### Example 5: "Hit the nail on the head"
115
-
116
- **Context**: Be exactly right / Get to the point accurately
117
-
118
- **Literal Translation Issues**:
119
-
120
- - Carpentry metaphor doesn't translate culturally
121
- - Different cultures have different expressions for accuracy
122
- - The physical act of nailing has no metaphorical meaning in target cultures
123
-
124
- **Correct Translation with Reasoning**:
125
-
126
- **Japanese**: 的を射る (mato wo iru) - "Hit the target"
127
-
128
- - **Why**: Uses archery metaphor instead, widely understood idiom
129
- - **Cultural note**: Archery (kyudo) has cultural significance in Japan
130
- - **Alternatives**:
131
- - 正鵠を得る (seikoku wo eru) - "Get the bullseye" (more formal, same origin)
132
- - 核心をつく (kakushin wo tsuku) - "Strike the core" (direct)
133
-
134
- **Chinese**: 一針見血 (yi zhen jian xue) - "One needle sees blood"
135
-
136
- - **Why**: Classical idiom using acupuncture metaphor for getting to the point
137
- - **Cultural note**: Medical/acupuncture metaphor reflects Chinese cultural background
138
- - **Alternatives**:
139
- - 切中要害 (qiezhong yaohai) - "Cut to the vital point"
140
- - 一語中的 (yi yǔ zhongdi) - "One phrase hits the target"
141
-
142
- ### Example 6: "Kill two birds with one stone"
143
-
144
- **Context**: Accomplish two things with one action
145
-
146
- **Japanese**: 一石二鳥 (isseki nichou)
147
-
148
- - **Why**: This idiom actually exists in Japanese (borrowed concept)
149
- - **Note**: Direct parallel exists, so translation is straightforward
150
-
151
- **Chinese**: 一石二鳥 (yi shi er niao) or 一舉兩得 (yi jǔ liǎng dé)
152
-
153
- - **Why**: Both versions exist; the second means "one action, two gains" (more common)
154
- - **Note**: Shows how some Western idioms have been adopted
155
-
156
- ## Challenge 2: Cultural References
157
-
158
- **Strategy**: Adapt or explain references unfamiliar to target culture. Consider whether the specific cultural reference is essential to meaning, or if the underlying concept can be conveyed through a more familiar equivalent.
159
-
160
- ### Example 1: "Turkey on Thanksgiving"
161
-
162
- **Original Context**: American holiday tradition, centerpiece of family gathering meal
163
-
164
- **Translation Approaches**:
165
-
166
- **Japanese**:
167
-
168
- **Option 1 - Direct + Explanation**: 感謝祭の七面鳥 (Kanshasai no shichimenchou)
169
-
170
- - Add brief explanation: アメリカの感謝祭に食べる伝統的な料理
171
- - **When to use**: When discussing American culture specifically
172
- - **Pros**: Accurate, educational
173
- - **Cons**: May feel distant to Japanese readers
174
-
175
- **Option 2 - Cultural Adaptation**: お正月のおせち料理 (Oshougatsu no osechi ryouri)
176
-
177
- - Translation: New Year's feast dishes
178
- - **Why**: Similar role as holiday feast centerpiece in Japanese culture
179
- - **When to use**: When the function matters more than the specific tradition
180
- - **Pros**: Relatable to Japanese audience
181
- - **Cons**: Changes the specific cultural reference
182
-
183
- **Option 3 - Generalization**: 伝統的な祝日料理 (dentouteki na shukujitsu ryouri)
184
-
185
- - Translation: Traditional holiday food
186
- - **When to use**: When specific holiday doesn't matter
187
- - **Pros**: Clear and neutral
188
- - **Cons**: Loses cultural specificity
189
-
190
- **Chinese**:
191
-
192
- **Option 1 - Direct + Explanation**: 感恩節火雞 (gan'en jie huoji)
193
-
194
- - Add context: 美國感恩節的傳統大餐
195
- - **When to use**: Educational or cultural content about America
196
-
197
- **Option 2 - Cultural Adaptation**: 年夜飯 (nianye fan)
198
-
199
- - Translation: New Year's Eve dinner (reunion dinner)
200
- - **Why**: Important family gathering meal in Chinese culture
201
- - **When to use**: When emphasizing family gathering aspect
202
-
203
- **Option 3 - Keep + Context**: 美國感恩節的傳統火雞大餐
204
-
205
- - Translation: American Thanksgiving's traditional turkey feast
206
- - **Why**: Makes the American context clear while keeping the specific reference
207
-
208
- ### Example 2: Baseball metaphors
209
-
210
- **Original Context**: "Home run" (great success), "Strike out" (fail completely)
211
-
212
- **Translation Approaches**:
213
-
214
- **Japanese**:
215
-
216
- **Option 1 - Keep original**: ホームラン (hoomuran), ストライクアウト (sutoraiku auto)
217
-
218
- - **Why**: Baseball is extremely popular in Japan; terms are widely understood
219
- - **Best choice**: Keep the baseball reference in most cases
220
- - **Cultural note**: Japan has professional baseball leagues; the sport is culturally familiar
221
-
222
- **Option 2 - Adapt meaning**: 大成功 (daiseikou) / 失敗 (shippai)
223
-
224
- - Translation: Great success / Failure
225
- - **When to use**: If baseball context isn't relevant or might be confusing
226
- - **Pros**: Universal understanding
227
- - **Cons**: Loses the vivid imagery
228
-
229
- **Chinese**:
230
-
231
- **Option 1 - Keep + explain**: 全壘打 (quanlei da)
232
-
233
- - **Context**: Baseball terminology understood in Taiwan and Hong Kong
234
- - **Regional note**: More familiar in Taiwan than mainland China
235
-
236
- **Option 2 - Adapt**: 一舉成功 (yiju chenggong) / 完全失敗 (wanquan shibai)
237
-
238
- - Translation: Succeed in one stroke / Complete failure
239
- - **Why**: Baseball less culturally prominent in mainland China
240
- - **When to use**: When audience is primarily mainland Chinese
241
-
242
- **Decision factors**:
243
-
244
- - Taiwan readers: Keep baseball terms (baseball is popular)
245
- - Hong Kong readers: Keep with brief explanation
246
- - Mainland readers: Consider adapting unless in sports context
247
-
248
- ### Example 3: Roman mythology references
249
-
250
- **Original Context**: "Achilles' heel" (fatal weakness)
251
-
252
- **Translation Approaches**:
253
-
254
- **Japanese**:
255
-
256
- **Direct translation**: アキレス腱 (Akiresu ken)
257
-
258
- - **Why**: This particular reference has become international; commonly used in Japanese
259
- - **Best choice**: Keep as is; widely understood even outside sports/medical contexts
260
- - **Note**: Used metaphorically in Japanese just as in English
261
-
262
- **Alternative**: 弱点 (jakuten) or 急所 (kyuusho)
263
-
264
- - Translation: Weakness / Vital point
265
- - **When to use**: If context makes the reference unclear or overly foreign
266
-
267
- **Chinese**:
268
-
269
- **Option 1 - Direct translation**: 阿基里斯腱 (Ajiilisi jian)
270
-
271
- - Used in formal/academic contexts
272
- - **Pros**: Accurate for educated audiences
273
- - **Cons**: May be unfamiliar to general readers
274
-
275
- **Option 2 - Cultural adaptation**: 致命弱點 (zhiming ruodian)
276
-
277
- - Translation: Fatal weakness
278
- - **Better choice**: More accessible to general audience
279
- - **Pros**: Clear meaning without requiring classical Western knowledge
280
-
281
- **Option 3 - Literary option**: 命門 (mingmen)
282
-
283
- - Translation: "Life gate" (vital point/weakness)
284
- - **Why**: Classical Chinese term from martial arts/medicine
285
- - **When to use**: Formal or literary texts
286
- - **Cultural note**: Has roots in traditional Chinese medicine
287
-
288
- ### Example 4: Biblical references
289
-
290
- **Original Context**: "Good Samaritan" (someone who helps strangers)
291
-
292
- **Japanese**:
293
-
294
- - **Direct**: 良きサマリア人 (yoki samaria jin) - rarely understood
295
- - **Adapted**: 困っている人を助ける親切な人 (komatte iru hito wo tasukeru shinsetsu na hito)
296
- - Translation: "Kind person who helps people in trouble"
297
- - **Best approach**: Explain or adapt, as Christianity is minority religion
298
-
299
- **Chinese**:
300
-
301
- - **Direct**: 好撒馬利亞人 (hǎo Samǎlìyà rén) - understood in Christian contexts only
302
- - **Adapted**: 樂於助人的好心人 (lè yú zhù rén de hǎo xīn rén)
303
- - Translation: "Warm-hearted person happy to help others"
304
- - **Context matters**: Christian audiences understand reference; general audiences don't
305
-
306
- ## Challenge 3: Wordplay and Puns
307
-
308
- **Strategy**: Recreate the effect, not the exact wordplay. Puns are highly language-specific. The translator's goal is to convey that humor exists and ideally create a similar effect, even if the mechanism changes completely.
309
-
310
- ### Example 1: "Time flies like an arrow; fruit flies like a banana"
311
-
312
- **Original Wordplay**: "Flies" used as verb (time) and noun (fruit)
313
-
314
- **Translation Challenge**: This specific wordplay is impossible to recreate in target languages
315
-
316
- **Solutions**:
317
-
318
- **Japanese**:
319
-
320
- **Option 1 - Explain**: 時は矢のように飛ぶが、ミバエはバナナが好きだ
321
-
322
- - Translation: "Time flies like an arrow, but fruit flies like bananas"
323
- - **Why**: Preserves the joke structure even though wordplay is lost
324
- - **Result**: Audience understands it was a pun in English
325
- - **Add note**: (英語の言葉遊び) "English wordplay"
326
-
327
- **Option 2 - Different wordplay**: Create new pun in Japanese
328
-
329
- - Example: 時は金なり、銀なりたくない (toki wa kin nari, gin naritakunai)
330
- - Translation: "Time is money (gold), (but I) don't want to become silver"
331
- - **Why**: Creates new wordplay on 金 (gold/money) and なり (is/become)
332
- - **Pros**: Maintains the humor and surprise
333
- - **Cons**: Completely different from original joke
334
-
335
- **Chinese**:
336
-
337
- **Option 1 - Preserve structure**: 時光飛逝如箭,果蠅喜歡香蕉
338
-
339
- - Translation: "Time flies like arrow, fruit flies like banana"
340
- - **Result**: Keeps the surprising twist but loses the linguistic pun
341
- - **Add note**: (英語雙關語) "English pun"
342
-
343
- **Option 2 - Create new pun**: 時間不等人,但人可以等時間
344
-
345
- - Translation: "Time waits for no one, but people can wait for time"
346
- - **Why**: Creates parallel structure with philosophical twist
347
- - **Pros**: Maintains surprise element
348
- - **Cons**: Different type of wordplay (philosophical rather than grammatical)
349
-
350
- ### Example 2: Business name puns
351
-
352
- **Original**: "Curl Up and Dye" (hair salon)
353
- **Wordplay**: Sounds like "curl up and die"
354
-
355
- **Translation Challenge**: Sound-based wordplay specific to English pronunciation
356
-
357
- **Solutions**:
358
-
359
- **Japanese**:
360
-
361
- **Option 1 - Explain meaning**: カールアップ・アンド・ダイ (髪を染めてカールする店)
362
-
363
- - Keep romanization + add explanation in parentheses
364
- - **When to use**: When the English name is kept for branding
365
-
366
- **Option 2 - Create Japanese pun**:
367
-
368
- - Example: 髪切るべー (kamikiru bē)
369
- - Sounds like casual "let's cut hair" in some dialects
370
- - Plays on 髪 (kami - hair) and casual invitation
371
- - Example: カミングアップ (kamingu appu)
372
- - Plays on 髪 (kami - hair) and "coming up"
373
- - **Why**: Creates bilingual wordplay (Japanese 髪 + English "coming up")
374
-
375
- **Chinese**:
376
-
377
- **Option 1 - Direct translation**: 捲染髮廊
378
-
379
- - Translation: "Curl and dye salon"
380
- - **Result**: Loses the pun entirely; just descriptive
381
-
382
- **Option 2 - Create Chinese pun**:
383
-
384
- - Example: 髮現美 (faxian mei)
385
- - Sounds like 發現美 (discover beauty)
386
- - Uses 髮 (hair) character instead of 發
387
- - Example: 剪愛你 (jian ai ni)
388
- - Sounds like 見愛你 (see love you) or 建愛你 (build love for you)
389
- - Uses 剪 (cut/scissors) character
390
- - **Why**: Creates Chinese-specific sound-based wordplay
391
-
392
- ### Example 3: "Why did the scarecrow win an award? He was outstanding in his field"
393
-
394
- **Original Wordplay**: "Outstanding in his field" means both "excellent in his profession" and "standing in a field"
395
-
396
- **Translation Challenge**: Double meaning specific to English
397
-
398
- **Solutions**:
399
-
400
- **Japanese**:
401
-
402
- **Option 1 - Explain joke**:
403
-
404
- - かかしが賞を取った理由は?畑で最も優れていたから(実際に畑に立っていた)
405
- - Translation: "Why did scarecrow win? Because he was most excellent in the field (actually standing in the field)"
406
- - **Result**: Joke explained but less punny; parenthetical clarifies the wordplay
407
-
408
- **Option 2 - Create new scarecrow joke**:
409
-
410
- - Example: かかしが人気者になった理由は?いつも畑にいるから
411
- - Translation: "Why did scarecrow become popular? Because he's always in the field"
412
- - Plays on いる (present/committed) - weaker pun but maintains humor structure
413
-
414
- **Chinese**:
415
-
416
- **Option 1 - Adapt the pun**:
417
-
418
- - 稻草人為什麼得獎?因為他在自己的領域裡站得最高(出眾)
419
- - Translation: "Why did scarecrow win? Because he stood tallest in his field (outstanding)"
420
- - **Result**: Partially preserves the standing/outstanding wordplay using 站 (stand) and 出眾 (outstanding/standing out)
421
-
422
- **Option 2 - Different approach**:
423
-
424
- - Use 田間 (field) and 傑出 (outstanding) with footnote explaining English pun
425
- - **When to use**: When precision matters more than humor preservation
426
-
427
- ## Challenge 4: Formality Levels
428
-
429
- **Strategy**: Understand formality indicators in each language and match them appropriately across languages.
430
-
431
- ### English Formality Indicators
432
-
433
- **Informal**:
434
-
435
- - Contractions: don't, can't, won't
436
- - Simple vocabulary: buy, help, get
437
- - Personal pronouns: you, I, we
438
- - Short sentences
439
- - Colloquialisms and slang
440
-
441
- **Formal**:
442
-
443
- - No contractions: do not, cannot, will not
444
- - Sophisticated vocabulary: purchase, assist, obtain
445
- - Passive voice: "It is recommended that..."
446
- - Complex sentence structures
447
- - Technical or literary terms
448
-
449
- ### Japanese Formality Levels
450
-
451
- **Casual (Plain form)**:
452
-
453
- - 食べる (taberu), 行く (iku), いい (ii), だ (da)
454
- - Pronouns: 俺 (ore - masculine), あたし (atashi - feminine)
455
- - Sentence endings: だ, だよ, だね
456
-
457
- **Standard Polite (です/ます form)**:
458
-
459
- - 食べます (tabemasu), 行きます (ikimasu), いいです (ii desu)
460
- - Pronouns: 私 (watashi), あなた (anata - use sparingly)
461
- - Sentence endings: です, ます
462
-
463
- **Formal/Respectful**:
464
-
465
- - いらっしゃる (irassharu), 召し上がる (meshiagaru)
466
- - Pronouns: わたくし (watakushi)
467
- - Honorific prefixes: ご〜 (go-), お〜 (o-)
468
- - Sentence endings: でございます (de gozaimasu)
469
-
470
- ### Chinese Formality Indicators
471
-
472
- **Informal**:
473
-
474
- - Simple vocabulary: 吃 (chi - eat), 買 (mai - buy)
475
- - Pronouns: 你 (ni - you), 我們 (women - we)
476
- - Colloquial expressions
477
- - Sentence-final particles: 啦, 嘍, 唄
478
-
479
- **Formal**:
480
-
481
- - Literary vocabulary: 用餐 (yongcan - dine), 購買 (goumai - purchase)
482
- - Pronouns: 您 (nin - polite "you"), 本人 (benren - "this person" for "I")
483
- - Classical expressions: 誠摯 (chengzhi - sincere), 敬請 (qingqing - respectfully request)
484
- - More complex sentence structures
485
- - Formal sentence patterns
486
-
487
- ### Translation Example: "Please let me know if you have any questions"
488
-
489
- **English Informal**: Let me know if you have any questions
490
-
491
- **English Formal**: Please do not hesitate to contact me should you have any inquiries
492
-
493
- **Japanese Casual**: 質問があったら教えてね (Shitsumon ga attara oshiete ne)
494
-
495
- **Japanese Polite**: ご質問があればお知らせください (Go-shitsumon ga areba o-shirase kudasai)
496
-
497
- **Japanese Formal**: ご不明な点がございましたら、お気軽にお問い合わせくださいませ
498
-
499
- - (Go-fumei na ten ga gozaimashitara, o-kigaru ni o-toiawase kudasaimase)
500
-
501
- **Chinese Informal**: 有問題就告訴我 (You wenti jiu gaosu wo)
502
-
503
- **Chinese Polite**: 如有問題請告訴我 (Ru you wenti qing gaosu wo)
504
-
505
- **Chinese Formal**: 如有任何疑問,敬請隨時與我聯繫 (Ru you renhe yiwen, qingqing suishi yu wo lianxi)
506
-
507
- ## Challenge 5: Ambiguity Resolution
508
-
509
- **Strategy**: When source text is ambiguous, use context clues, research, and informed judgment to determine the most likely intended meaning.
510
-
511
- ### Types of Ambiguity
512
-
513
- **1. Lexical Ambiguity** (word has multiple meanings)
514
-
515
- **Example**: "I saw her duck"
516
-
517
- - Did I see her pet duck?
518
- - Did I see her lower her head?
519
-
520
- **Resolution approach**:
521
-
522
- - Check surrounding context
523
- - Consider what makes sense in the situation
524
- - If truly ambiguous, choose most common meaning
525
- - Note the ambiguity for reviewer
526
-
527
- **2. Structural Ambiguity** (sentence structure creates multiple meanings)
528
-
529
- **Example**: "The chicken is ready to eat"
530
-
531
- - The chicken is cooked and ready for us to eat
532
- - The chicken (alive) is hungry and ready to eat food
533
-
534
- **Resolution approach**:
535
-
536
- - Analyze broader context
537
- - Consider the document type (recipe vs. farm guide)
538
- - Choose interpretation that fits the context
539
-
540
- **3. Referential Ambiguity** (unclear what a pronoun refers to)
541
-
542
- **Example**: "John told Mike that he needed to leave"
543
-
544
- - Who needs to leave - John or Mike?
545
-
546
- **Resolution approach**:
547
-
548
- - Look at preceding and following sentences
549
- - Consider the logical flow
550
- - In translation, may need to use names instead of pronouns for clarity
551
-
552
- **4. Cultural Ambiguity** (meaning unclear across cultures)
553
-
554
- **Example**: "Let's table this discussion"
555
-
556
- - US English: Postpone the discussion
557
- - UK English: Put it on the table (discuss it now)
558
-
559
- **Resolution approach**:
560
-
561
- - Determine the source variety (US vs. UK English)
562
- - Consider speaker's cultural background
563
- - Ask for clarification if possible
564
-
565
- ### Ambiguity Resolution Checklist
566
-
567
- When encountering ambiguous source text:
568
-
569
- 1. **Analyze context**: Read surrounding paragraphs
570
- 2. **Research domain**: Check if it's domain-specific terminology
571
- 3. **Consult references**: Use dictionaries, corpora, native speaker resources
572
- 4. **Apply logic**: What makes sense in this situation?
573
- 5. **Check consistency**: How are similar terms used elsewhere in the document?
574
- 6. **Note uncertainty**: Flag for reviewer if truly unresolvable
575
- 7. **Choose most likely**: Make informed decision based on available evidence
576
- 8. **Document reasoning**: Keep notes on why you chose this interpretation
577
-
578
- ### Example Workflow
579
-
580
- **Source**: "The professor didn't recommend the book because it was too advanced"
581
-
582
- **Ambiguity**: Did the professor:
583
-
584
- - NOT recommend it because it's too advanced (too difficult)?
585
- - Recommend it for reasons other than being advanced?
586
-
587
- **Resolution process**:
588
-
589
- 1. Check context: Is this about a beginner or advanced course?
590
- 2. Consider logical meaning: First interpretation is more common
591
- 3. Make decision: Choose first interpretation (didn't recommend due to difficulty)
592
- 4. Note for reviewer: Add comment about potential ambiguity
593
- 5. Translate with chosen interpretation
594
-
595
- **Japanese translation** (first interpretation):
596
- 教授はその本を推薦しなかった。内容が高度すぎるためだ。
597
-
598
- - Explicitly clarifies the causal relationship
599
-
600
- **Chinese translation** (first interpretation):
601
- 教授沒有推薦那本書,因為內容太深奧了。
602
-
603
- - Uses 因為 (because) to make causal relationship explicit