`, `
`, `
`, `
- `, `
- `, ``, etc.) exactly as is, including classes and styles. * **Crypto/Tech Terms:** * Bitcoin (BTC) -> Bitcoin (BTC) * Market Cap -> Marktkapitalisierung * Volume Signal -> Volumensignal * Market Sentiment -> Marktstimmung * Fear & Greed Index -> Fear & Greed Index (often kept in English or translated as "Angst-und-Gier-Index", but keeping English is common in crypto contexts. I'll translate for natural German flow but keep the name recognizable). Let's use "Fear & Greed Index" as it's a proper noun in crypto, or "Angst-und-Gier-Index". I'll stick to the common German crypto usage which often keeps "Fear & Greed Index" or translates it. I will translate it for better localization: "Angst-und-Gier-Index". * On-Chain Signal -> On-Chain-Signal * Macro Signal -> Makro-Signal * Support Level -> Unterstützungsniveau * Resistance Level -> Widerstandsniveau * RSI -> RSI (keep acronym) * Moving Average -> Gleitender Durchschnitt * Network Activity -> Netzwerkaktivität * Whale Activity -> Whale-Aktivität (or "Aktivität großer Holder") -> "Whale-Aktivität" is common. * Exchange Flows -> Börsenflüsse * HODLer -> HODLer (keep crypto slang) * DXY -> DXY (keep acronym) * Bond Yields -> Anleiherenditen * Risk Appetite -> Risikobereitschaft * Institutional Flow -> Institutioneller Fluss * Risk-off -> Risikoaversion / "Risk-Off" (often kept). I'll use "Risikoaversion". * Safe havens -> Sichere Häfen * Liquidation risk -> Liquidationsrisiko * Leverage -> Hebel * Stablecoin -> Stablecoin * Minting -> Prägung / Emission * Dry powder -> Trockenes Pulver (idiom) -> "Reserven" might be better contextually. * Price wicks -> Preisdochte (crypto slang) * Back-channel -> Hinterkanal * Monetary policies -> Geldpolitiken * **Proper Nouns:** Washington, Jerusalem, Tehran, Israel, Hamas, Iran, United States, Bitcoin, BTC, US dollar, gold. Keep these. * **Numbers:** $63,450, -2.35%, -5.10%, $1.25 Trillion, 38, 14d, $61,200, $65,800, 42, 24-72 hour, early 2022. Keep exact. * **HTML Structure:** Must be preserved exactly. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* USA informiert Israel: Iran-Verhandlungen festgefahren angesichts von Eskalationsbefürchtungen * *Executive Summary:* Washington hat Jerusalem offiziell mitgeteilt... * *What Happened:* US-Beamte übermittelten eine klare Botschaft... * *Market Data Snapshot:* Marktdaten-Schnappschuss. Primary Asset -> Primäres Asset. Current Price -> Aktueller Preis. * *Market Health Indicators:* Marktgesundheitsindikatoren. Technical Signals -> Technische Signale. * *Why This Matters:* Warum das wichtig ist. For Traders -> Für Trader. For Investors -> Für Investoren. * *What Most Media Missed:* Was die meisten Medien übersehen haben. * *What Happens Next:* Was als Nächstes passiert. * *Historical Parallel:* Historisches Pendant. * *Specific Nuances:* * "Deadlocked" -> "festgefahren" or "in einer Sackgasse". * "Impasse" -> "Pattsituation". * "Risk premiums" -> "Risikoaufschläge". * "Digital asset classes" -> "digitale Asset-Klassen". * "Pressure valve" -> "Druckventil". * "Pricing in risk" -> "Risiko einpreisen". * "Dry powder" -> "freie Mittel" or "Reserven". * "Price wicks" -> "Preisausschläge" or "Dochte". "Dochte" is more crypto-native. * "Choppy price action" -> "unbeständige Preisbewegungen". 5. **JSON Construction:** * Ensure all quotes inside the JSON strings are escaped properly (`"` -> `"`). * Ensure newlines are handled correctly (usually JSON strings shouldn't have raw newlines, but since the content is HTML, it will be a single long string or escaped newlines. The prompt asks for JSON response. I will format the HTML content as a single string value within the JSON, escaping necessary characters). * Wait, the prompt says "RESPOND IN JSON". I need to make sure the HTML inside the JSON value is valid JSON string (escaped quotes, no unescaped newlines unless using ``). However, usually, for HTML content in JSON, it's best to keep it as a continuous string or escape newlines. I will minimize whitespace in the HTML string to avoid JSON syntax errors, or escape newlines. Given the input has pretty-printed HTML, I should preserve the structure but ensure it's valid JSON. I will compress the HTML slightly or escape newlines to ensure validity. Actually, standard practice for this type of task is to return the HTML string with escaped characters where needed. I will keep the HTML structure but ensure it fits within a JSON string value (escaping double quotes inside attributes if any, though the input uses single quotes for some attributes like `class='market-snapshot'`, which is safer for JSON). * Input HTML uses single quotes for attributes (`class='...'`, `style='...'`). This is good, avoids escaping double quotes in JSON. * I need to make sure I don't introduce double quotes inside the string unless escaped. * I will construct the JSON carefully. 6. **Review against Constraints:** * Identity: I am XROOM-69. (Implicitly handled by not claiming otherwise). * Language: German. * Format: JSON. * HTML Preservation: Critical. * Accuracy: Numbers must match. 7. **Final Polish of German Text:** * "Washington has formally notified Jerusalem" -> "Washington hat Jerusalem offiziell benachrichtigt" *