`, `
`, `
`, `
- `, `
- `, ``, etc.) exactly as they are, only changing text content.
* **Crypto Terms:**
* Bitcoin (BTC) -> Bitcoin (BTC)
* Market Cap -> Capitalización de Mercado
* Volume Signal -> Señal de Volumen
* Market Sentiment -> Sentimiento de Mercado
* Fear & Greed Index -> Índice de Miedo y Codicia
* On-Chain Signal -> Señal On-Chain
* Macro Signal -> Señal Macro
* Stablecoin -> Stablecoin (or Moneda Estable, but Stablecoin is common)
* Support/Resistance Level -> Nivel de Soporte/Resistencia
* RSI -> RSI
* Moving Average -> Media Móvil
* Whale Activity -> Actividad de Ballenas
* HODLer -> HODLer (common term)
* DXY -> DXY
* Bond Yields -> Rendimientos de Bonos
* Risk-Off -> Risk-Off (often kept in English in finance context, or "aversión al riesgo")
* Liquidation heatmaps -> Mapas de calor de liquidación
* Derivatives markets -> Mercados de derivados
* Protective puts -> Puts de protección
* **Proper Nouns:** Michel Aoun, Israel, Hezbollah, Israel Defense Forces (IDF) -> Fuerzas de Defensa de Israel (FDI) or keep IDF? Usually better to translate organization names but keep acronyms if well known. Let's translate IDF to FDI or keep IDF with explanation. The prompt says "Keep proper nouns (names, company names) in original form". IDF is an organization name. I will translate the full name but keep the acronym if used, or translate the acronym to FDI. Let's look at standard Spanish media: "Fuerzas de Defensa de Israel (IDF)" or just "IDF". I will translate the name for clarity but keep the acronym in parentheses if it appears. Actually, the prompt says "Keep proper nouns... in original form". This usually applies to names like "Michel Aoun", "Bitcoin", "Israel". "Israel Defense Forces" is an organization. I will translate it to "Fuerzas de Defensa de Israel (IDF)" to maintain accuracy while respecting the language target, but strictly speaking, "Israel Defense Forces" is a proper noun. I will translate the descriptive part for natural flow but keep the acronym. Actually, to be safe with "Keep proper nouns... in original form", I will keep "Israel Defense Forces (IDF)" but maybe add the Spanish translation in parentheses or just translate it if it's common practice. Let's check the instruction again: "Keep proper nouns (names, company names) in original form". "Israel Defense Forces" is a specific entity name. I will keep "Israel Defense Forces (IDF)" or translate to "Fuerzas de Defensa de Israel (IDF)". Given "Translate naturally", translating the organization name is better for Spanish readers. I will use "Fuerzas de Defensa de Israel (IDF)".
* **Numbers/Data:** $67,450, -2.35%, etc. must remain exact.
* **HTML Structure:** Must be preserved exactly (classes, styles, etc.).
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* El Presidente de Líbano Pide Conversaciones con Israel en Medio de Ataques Escalantes
* *Executive Summary:* Resumen Ejecutivo. Michel Aoun... pivot diplomático... Hezbollah e IDF...
* *What Happened:* Qué Ocurrió. Canales oficiales... tensiones fronterizas...
* *Market Data Snapshot:* Instantánea de Datos de Mercado. Bitcoin (BTC)...
* *Market Health Indicators:* Indicadores de Salud del Mercado. Technical Signals -> Señales Técnicas. On-Chain Health -> Salud On-Chain. Macro Environment -> Entorno Macro.
* *Why This Matters:* Por Qué Esto Importa. Traders -> Operadores/Traders (Traders is very common in crypto Spanish). Investors -> Inversores.
* *What Most Media Missed:* Lo Que la Mayoría de los Medios Pasaron por Alto.
* *What Happens Next:* Qué Sucede Después.
* *Historical Parallel:* Paralelismo Histórico.
* *Specific Terms:*
* "Risk-off behavior" -> "comportamiento de aversión al riesgo (risk-off)"
* "High-beta assets" -> "activos de alta beta"
* "Cold storage" -> "almacenamiento en frío"
* "Liquidation heatmaps" -> "mapas de calor de liquidación"
* "V-shaped recovery" -> "recuperación en V"
* "Weak Hands" -> "Manos Débiles" (common crypto slang)
* "HODLer" -> "HODLer"
* *HTML Check:* Ensure ``, ``, etc., are copied exactly. 5. **JSON Construction:** * Need to escape quotes within the JSON string values properly. * Ensure newlines are handled correctly (usually JSON strings shouldn't have raw newlines, need ``). However, the `content` field contains HTML. HTML often contains newlines for readability. In JSON, I should escape newlines as `` or keep the HTML structure compact. The prompt shows the original content with indentation. I should preserve the HTML structure but ensure it's valid JSON. I will minimize whitespace inside the JSON string value to avoid issues, or escape newlines. Best practice for JSON with HTML content is to escape newlines (``) or keep it as a single line string. I will format the HTML inside the JSON string with escaped newlines `` to preserve readability if parsed, but strictly speaking, JSON strings cannot contain unescaped line breaks. I will ensure the JSON is valid. * *Wait, one constraint:* "RESPOND IN JSON". I must output *only* the JSON object. No markdown code blocks like ```json ... ``` unless implied, but usually raw JSON is safer. However, most interfaces expect markdown blocks for code. I will output a markdown code block with json tag to be safe and clear, but the content inside must be valid JSON. Actually, strict JSON response means no markdown fences sometimes. But looking at typical behavior, a code block is preferred for structure. I will output the JSON directly within a code block to ensure it's treated as code. * *Correction:* The prompt says "RESPOND IN JSON". I should output the raw JSON string or a code block containing it. I will use a code block for clarity. * *Escaping:* I need to be very careful with double quotes inside the HTML content (e.g., `class='market-snapshot'` uses single quotes, which is good. `style='...'`