`, ``, `
`, `
- `, `
- `, ``, `` tags exactly as they are, including inline styles in the `health-indicators` div. * Ensure JSON escaping is correct (quotes, newlines). 5. **Drafting the Translation (Mental or Scratchpad):** * *Title:* ABD'nin İran'a Kara Birliği Konuşlandırma Olasılığı 30 Nisan Öncesinde %86'ya Ulaştı * *Exec Summary:* Jeopolitik piyasalar... %86 olasılık... Kripto piyasaları... * *What Happened:* Son stratejik analiz... Crypto Briefing... %86.5... * *Market Data:* Bitcoin (BTC)... Fiyat... Piyasa Değeri... * *Health Indicators:* Teknik Sinyaller... Destek... Direnç... RSI... * *Why This Matters:* Yatırımcılar için... Traderlar için... * *What Most Media Missed:* Büyük medya organları... %0.5 fark... * *What Happens Next:* Kısa Vadeli Beklenti... Uzun Vadeli Senaryolar... * *Historical Parallel:* Tarihsel Benzerlik... 2020... 6. **JSON Formatting:** * Need to escape double quotes inside the content string. * Need to ensure newlines are handled correctly (usually JSON strings shouldn't have literal newlines, they should be ``, but since I'm outputting a JSON block, I need to make sure the structure is valid). Actually, the prompt asks to respond IN JSON. I will construct a valid JSON object. * The `content` field should contain the HTML string. I need to be careful with escaping quotes within the HTML attributes (e.g., `class='market-snapshot'` uses single quotes, which is good, but if I use double quotes in translation inside attributes, I need to escape). The original HTML uses single quotes for classes/styles mostly, which helps. I will maintain single quotes where possible to minimize escaping, but JSON requires double quotes for keys and string values. So internal double quotes in the HTML string must be escaped `"`. * Wait, the original HTML uses `class='market-snapshot'` (single quotes). I should keep that. If I introduce any double quotes in the translation (e.g., inside a title attribute, though none exist), I'd need to escape. I will stick to the original HTML quoting style to avoid issues. 7. **Review against Constraints:** * Identity: XROOM-69. (Implicit in system instruction, I just need to perform the task). * No mention of AI identity in the output (just the JSON). * Accurate numbers: 86%, 86.5%, April 30, $104,250, etc. * Turkish terminology: "Kara Birliği", "Konuşlandırma", "Oynaklık", "Güvenli Liman". 8. **Final Polish:** * Check specific phrases: "Strong Hands" -> "Güçlü Eller" (Crypto slang translation) or keep "Strong Hands"? In Turkish crypto community, "Güçlü Eller" is used. I'll use "Güçlü Eller". * "Risk-Off" -> "Riskten Kaçış" or "Risk Off". I'll use "Riskten Kaçınan" for clarity. * "Headwind" -> "Baş Rüzgarı" (metaphor) or "Olumsuz Etki". "Baş Rüzgarı" is common in finance. * "Safe Haven" -> "Güvenli Liman". * Ensure the `div` with inline styles remains intact. *Self-Correction on JSON:* The output must be *only* the JSON object. No markdown code blocks around it? The prompt says "RESPOND IN JSON". Usually, wrapping in ```json is helpful for clarity, but strict JSON response means raw text. However, as an AI chat interface, markdown blocks are standard. I will output a markdown code block containing the JSON to ensure it's parsed correctly by the user, but the content inside must be valid JSON. Wait, often "RESPOND IN JSON" implies the raw text should be JSON. But to be safe and clear, I will output the JSON block. Actually, looking at typical instructions, if it says "Respond in JSON", I should provide the JSON structure. I will wrap it in a code block for clarity as is standard practice for structured data responses. *Wait, one more check:* The prompt says "RESPOND IN JSON: { ... }". I should output exactly that structure. *Escaping:* I need to make sure any double quotes inside the HTML content are escaped. The original HTML uses single quotes for attributes (`class='...'`, `style='...'`). I will maintain this. If I add any quotes in Turkish text, I'll use Turkish quotation marks («») or escape them. I'll avoid quotes in the text where possible. *Let's build the