`, `
`, `
`, `
- `, `
- `, `
`) are kept exactly as is, including classes and inline styles. * Do not alter the structure. 5. **JSON Formatting:** * Escape quotes within the content string. * Ensure valid JSON structure. 6. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Dommer godkjenner investorsøksmål mot Nvidia over skjult kryptoinntekt * *Executive Summary:* En føderal dommer i California har offisielt godkjent et gruppesøksmål mot Nvidia... * *Market Data:* "Primary Asset" -> "Primæreiendel" (or "Hovedaktivum"). Let's use "Hovedaktivum". "Volume Signal" -> "Volumsignal". "Fear & Greed Index" -> "Frykt og grådighet-indeks". * *Health Indicators:* "Support Level" -> "Støttenivå". "Resistance Level" -> "Motstandsnivå". "Oversold" -> "Oversolgt". "Weak Hands" -> "Svake hender" (common crypto slang). "Risk-Off" -> "Risk-off" (kept as is usually). * *Meta Description:* Føderal dommer godkjenner gruppesøksmål mot Nvidia over ukjent kryptoutvinningsinntekt... 7. **Review against Constraints:** * Identity: XROOM-69. (Implicit in behavior, no need to state unless asked). * No AI names mentioned. * JSON output only. * Norwegian language (no). * HTML structure intact. 8. **Refining Terminology:** * "Class-action lawsuit" -> "Gruppesøksmål" is the correct Norwegian legal term. * "Certified" -> "Godkjent" or "Sertifisert" (in legal context "godkjent" fits better for class action certification). * "GPU" -> Keep as GPU. * "Crypto" -> "Krypto". * "Mining" -> "Mining" (often used) or "Utvinning". I will use "mining" as it's very common in Norwegian crypto contexts, or "kryptoutvinning" for clarity. Let's use "kryptomining" for flow. * "Securities fraud" -> "Verdipapirsvindel". * "Discovery processes" -> "Bevisopptaksprosesser". * "HODLer" -> Keep as "HODLer" (crypto slang). * "Risk-Off" -> Keep as "Risk-off". * "Bearish/Bullish" -> "Bjørnemarked"/"Oksemarked" or keep "Bearish"/"Bullish". In professional Norwegian financial contexts, "Bearish" is often translated to "negativ" or "nedadgående", but "Bearish" is understood. I will translate to "Negativ" / "Positiv" or "Bearish" depending on context. Actually, "Bearish" -> "Bearish" is common, but "Negativ" is clearer. Let's use "Negativ" for sentiment, but keep "Bullish case" as "Optimistisk scenario" or "Bullish-scenario". Let's stick to natural Norwegian: "Negativ" for sentiment, "Optimistisk" for case. Wait, requirement 5 says "appropriate Norwegian terminology". "Bearish" is often kept. I will use "Negativ" for sentiment to be natural, but "Bullish case" -> "Et positivt scenario". * Actually, looking at crypto communities in Norway, "Bearish" and "Bullish" are frequently used. However, for a formal article, "Negativ" and "Positiv" might be better. Let's compromise: "Market Sentiment: Bearish" -> "Markedsstemning: Negativ". "A bullish case" -> "Et positivt scenario". * "Weak Hands" -> "Svake hender" (direct translation is understood in crypto). * "Whale Activity" -> "Hvalaktivitet". 9. **Final Polish:** Check JSON escaping. Ensure no newlines break the JSON string value improperly (use `` if needed, but usually better to keep the HTML string continuous or properly escaped). Since the output is JSON, I need to make sure the HTML inside the `content` string is properly escaped (e.g., double quotes inside attributes must be escaped or the string must use single quotes for JSON wrapper). The prompt asks for JSON output. I will construct the JSON carefully. *Self-Correction on JSON:* The HTML contains double quotes (e.g., `class='market-snapshot'` uses single quotes in the source, but `style='...'` uses single quotes too). Wait, the source uses single quotes for attributes: `class='market-snapshot'`, `style='background: rgba(255,255,255,0.03); ...'`. This makes embedding in a JSON string (which uses double quotes) easier