`, `
`, `
`, `
- `, `
- `, `
`, inline styles. Needs to be preserved exactly. 3. **Translation Strategy:** * *Title:* "Bitcoin Momentum Indicator Flashes Sell-Off Warning After Reliable October Streak" -> "Indicador de Momentum de Bitcoin Emite Advertencia de Venta Masiva Después de Racha Confiable de Octubre". * *Executive Summary:* "Critical Bitcoin momentum indicator" -> "Indicador de momentum crítico de Bitcoin". "Sell-offs" -> "ventas masivas" or "caídas de precio". "Bullish investors" -> "inversores alcistas". * *What Happened:* "Crossed a critical threshold" -> "Cruzó un umbral crítico". "Sell-side signal" -> "señal de venta". "Buying pressure" -> "presión de compra". * *Market Data Snapshot:* Keep numbers exact. Translate labels (Current Price -> Precio Actual, Market Cap -> Capitalización de Mercado, etc.). Keep "Bitcoin (BTC)", "Fear & Greed Index" (often kept or translated as "Índice de Miedo y Codicia", but standard practice varies; I'll translate for clarity but keep specific terms like "Greed" contextually clear). Let's use "Índice de Miedo y Codicia" for clarity but keep "Greed" in parentheses if needed or translate to "Codicia". The prompt says "Use appropriate Spanish terminology". "Fear & Greed Index" is often known by its English name in crypto circles, but translating it is safer for general Spanish audience. I will translate the label but keep the value "Greed" as "Codicia". * *Market Health Indicators:* Preserve classes and styles. Translate headers and list items. "Support Level" -> "Nivel de Soporte". "Resistance Level" -> "Nivel de Resistencia". "HODLer" is a crypto slang, often kept as is or explained. I'll keep "HODLer" as it's a proper noun/slang in crypto. "DXY", "Bond Yields" -> "Rendimientos de Bonos". "Risk-On" -> "Apetito por el Riesgo" or keep "Risk-On" as it's technical. I'll translate to "Apetito por el Riesgo (Risk-On)" or just "Apetito por el Riesgo". Let's stick to natural Spanish: "Apetito por el Riesgo". * *Why This Matters:* "Traders" -> "Operadores" or "Traders" (commonly used). "Investors" -> "Inversores". "Stop-loss" -> "Stop-loss" (commonly used) or "límites de pérdida". I'll use "stop-loss" as it's standard tech terminology. "Liquidation risk" -> "riesgo de liquidación". * *What Most Media Missed:* "Divergence" -> "Divergencia". "Internal engine" -> "motor interno". * *What Happens Next:* "Short-Term Outlook" -> "Perspectiva a Corto Plazo". "Long-Term Scenarios" -> "Escenarios a Largo Plazo". * *Historical Parallel:* "Correction" -> "Corrección". "Altcoins" -> "Altcoins" (kept). 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Indicador de Momentum de Bitcoin Emite Advertencia de Venta Masiva Después de Racha Confiable de Octubre * *Meta:* El indicador de momentum de Bitcoin activa una señal de advertencia de venta por primera vez desde octubre, generando preocupaciones para los inversores alcistas en medio de una acción de precio estable. * *HTML:* Careful with tags. Do not escape quotes inside the JSON string improperly. I need to make sure the JSON is valid. I will escape double quotes inside the content if necessary, but since the HTML uses single quotes for some attributes (`class='market-snapshot'`), I should be careful. Actually, the input HTML uses single quotes for classes (`class='market-snapshot'`) and double quotes for styles (`style='background: ...'`). Wait, looking closely at the input: * `
` (single quotes) * `` (single quotes for class, single quotes for style attribute value). * To be safe in JSON, I should ensure the content string doesn't break the JSON structure. I will escape double quotes if I use them, but I'll try to maintain the original quoting style to minimize escaping issues. However, standard JSON requires double quotes for keys and string values. Inside the string value, double quotes need escaping `"`. The original HTML uses single quotes for attributes mostly, which is good. I will keep them as single quotes to avoid escaping hell, but ensure the JSON wrapper is correct. 5. **Refining Terminology:** * "Momentum" -> "Momentum" (often kept in Spanish crypto context) or "Impulso". "Momentum" is more precise technically. I'll use "Momentum". * "Sell-Off" -> "Venta masiva" or "Liquidación". "Venta masiva" fits "Sell-Off Warning". * "Bullish" -> "Alcista". * "Bearish" -> "Bajista". * "Volatility" -> "Volatilidad". * "Oscillators" -> "Osciladores". * "Market Makers" -> "Creadores de Mercado". * "Hedging" -> "Cobertura". * "Long positions" -> "Posiciones largas". * "Pullback" -> "Retroceso". * "Consolidation" -> "Consolidación". * "Leverage" -> "Apalancamiento". * "Support/Resistance" -> "Soporte/Resistencia". * "Whale Activity" -> "Actividad de Ballenas". * "Exchange Flows" -> "Flujos de Exchanges". * "HODLer" -> "HODLer" (Keep). * "DXY" -> "DXY" (Keep). * "Bond Yields" -> "Rendimientos de Bonos". * "Risk-On" -> "Apetito por el Riesgo". * "Institutional Flow" -> "Flujo Institucional". * "Derivatives markets" -> "Mercados de derivados". * "Put option" -> "Opciones de venta (Put)". * "Accumulation" -> "Acumulación". * "Altcoins" -> "Altcoins". 6. **JSON Construction:** * Must be valid JSON. * Keys: `title`, `content`, `meta`. * `meta` is an object with `description`. * Escape newlines if necessary (usually JSON strings shouldn't have literal newlines, they should be ``). However, the prompt asks for HTML content inside the JSON string. I will keep the HTML structure compact or ensure newlines are escaped properly. To be safe and valid, I will minimize whitespace in the JSON string value or escape newlines. Actually, standard practice for this type of task is to include the HTML as a single string with `` for line breaks if needed, or just keep it as a continuous string. I will preserve the indentation of the HTML for readability within the string but escape newlines as