`, ``, `
`, `
- `, `
- `, `` tags exactly as they are, including classes and inline styles. * Ensure no tags are broken during translation. 5. **JSON Formatting:** * Escape quotes within the JSON string values. * Ensure valid JSON structure. 6. **Identity Check:** * I am XROOM-69. Do not mention other AI models. (This is internal thought, not output). 7. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Il Giudice Certifica la Causa Collettiva degli Investitori contro Nvidia per Ricavi Crypto Nascosti * *Executive Summary:* Un giudice federale in California... * *What Happened:* L'ordinanza del tribunale concede lo status di class action... * *Market Data:* Asset Principale, Prezzo Attuale, Variazione Prezzo 24h... * *Health Indicators:* Segnali Tecnici, Supporto, Resistenza... * *Why Matters:* Per i Trader, Per gli Investitori... * *Media Missed:* Ciò che la maggior parte dei media ha perso... * *Next:* Cosa Succede Prossimamente... * *Historical:* Parallelo Storico... *Refining Crypto/Tech Terms:* * "Crypto revenue" -> "Ricavi crypto" * "GPU" -> "GPU" (keep acronym) * "Mining" -> "Mining" * "Bearish/Bullish" -> "Ribassista/Rialzista" * "Fear & Greed Index" -> "Indice Paura e Avidità" * "On-Chain" -> "On-Chain" (commonly used) * "HODLer" -> "HODLer" (crypto slang kept) * "Risk-Off" -> "Risk-Off" (financial term kept) or "Avverso al rischio". Let's use "Avverso al rischio" for natural Italian but keep specific signals clear. Actually, "Risk-Off" is very common in Italian financial news. I'll keep it or translate contextually. Let's translate for clarity: "Avverso al rischio (Risk-Off)". No, requirement says "Translate naturally". "Risk-Off" is standard jargon. I will use "Avverso al rischio". * "Whale Activity" -> "Attività delle Balene" * "Weak Hands" -> "Mani Deboli" *HTML Check:* * `` -> Keep class. * `` -> Keep class and style exactly. * Lists `
- ` `
- ` -> Keep structure. *JSON Escaping:* * Newlines need to be `` or the whole string needs to be single line. Usually, JSON values can contain newlines if escaped, but best to keep the HTML string compact or properly escaped. I will ensure all double quotes inside the content are escaped (`"`) and newlines are handled properly within the JSON string value. 8. **Final Review against Constraints:** * Identity: XROOM-69 (Implicit in behavior, no self-reference needed in output unless asked). * Facts/Numbers: Check $118.50, -2.15%, $2.91 Trillion, etc. * HTML: Verify tags match. * Tone: Professional financial news. *Self-Correction on JSON:* The prompt asks to "RESPOND IN JSON". I need to make sure the output is *only* the JSON object, no markdown code blocks around it if possible, but usually, markdown code blocks are accepted for clarity. However, strict JSON response is safer. I will output raw JSON text. Wait, usually, assistants wrap JSON in ```json ``` blocks. I will follow standard practice but ensure the content inside is valid JSON. Actually, the instruction says "RESPOND IN JSON". I will provide the JSON block. *Wait, one more check on Identity:* "IDENTITY REMINDER: You are XROOM-69... NEVER say you are ChatGPT...". This is a system instruction. I just need to ensure I don't break character. The output doesn't require me to state my name, just perform the task. *Translation Nuance:* "Class-action lawsuit" -> "Azione legale collettiva (class action)". I'll use "class action" as it's widely understood in Italian business news, or "causa collettiva". "Class action" is very common. I'll use "class action" for precision regarding the US legal mechanism. "Certifies" -> "Certifica" (in legal context "omologa" or "dispone la certificazione"). "Certifica" works well here. "Discovery" -> In Italian legal context regarding US law, "discovery" is often kept. I will use "fase di discovery". "ETFs" -> "ETF". "SKUs" -> "SKU