`, `
`, `
`, `
- `, `
- `, `
`, inline styles. Must be preserved exactly. 3. **Translation Strategy (English -> Norwegian):** * *Title:* "Bitcoin Traders Eye $60K Support as Price Action Mimics November Crash Pattern" -> "Bitcoin-handlere ser mot $60K-støtte ettersom prishandling etterligner november-krasj-mønster" (or similar natural phrasing). * *Executive Summary:* "Sammendrag" or "Eksekutivt sammendrag". "Bitcoin markets" -> "Bitcoin-markedene". "Bearish historical precedents" -> "Bajsiske historiske presedenser". * *What Happened:* "Hva som skjedde". "Trading charts" -> "Handelsgrafer". "Fractal formations" -> "Fraktale formasjoner". * *Market Data Snapshot:* "Markedsdata Oversikt". Keep numbers exact ($64,250, -2.45%, etc.). "Fear & Greed Index" -> "Frykt og Grådighets-indeks" (often kept English or translated, I'll translate for natural flow but keep specific terms recognizable). "BTC" stays "BTC". * *Market Health Indicators:* "Markedshelseindikatorer". "Technical Signals" -> "Tekniske signaler". "Support Level" -> "Støttenivå". "Resistance Level" -> "Motstandsnivå". "Weak Hands" -> "Svake hender" (common crypto slang). * *Why This Matters:* "Hvorfor dette betyr noe". "For Traders" -> "For handlere". "For Investors" -> "For investorer". * *What Most Media Missed:* "Hva de fleste medier gikk glipp av". * *What Happens Next:* "Hva som skjer videre". "Short-Term Outlook" -> "Kortsiktig utsikt". "Long-Term Scenarios" -> "Langsiktige scenarier". * *Historical Parallel:* "Historisk parallell". * *Meta Description:* Needs to be generated since the input was empty. Something like: "Bitcoin-markedet viser tegn på svakhet mens handlere observerer nøkkelsupport på $60K. Analyser av tekniske mønstre og on-chain data indikerer potensiell nedgang." 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Bitcoin-handlere observerer $60K-støtte ettersom prishandling etterligner november-krasj-mønster * *H2 Executive Summary:* Sammendrag * *H2 What Happened:* Hva som skjedde * *H2 Market Data Snapshot:* Markedsdata-oversikt * *H2 Market Health Indicators:* Indikatorer for markedshelse * *H2 Why This Matters:* Hvorfor dette er viktig * *H2 What Most Media Missed:* Det de fleste medier overså * *H2 What Happens Next:* Hva som skjer neste * *H2 Historical Parallel:* Historisk parallell * *Terms:* * Support -> Støtte * Resistance -> Motstand * Bullish/Bearish -> Oppadgående/Nedadgående (or Bullish/Bearish as they are often used in Norwegian crypto context, but "Bajsiske" is formal. I'll use "nedadgående" or "bearish" depending on context flow. Let's stick to natural Norwegian crypto lingo: "bearish" is often used, but "nedadgående trend" is clearer. I will use "bearish" where it's standard terminology but translate descriptions). Actually, in Norwegian financial news, "bearish" and "bullish" are often kept English or translated to "bjørnemarked"/"oksemarked". Let's use "bearish" / "bullish" where it fits technical context, or "nedadgående" for sentiment. * HODLer -> HODLer (keep) * Whale -> Hval (or Whale) -> "Hval-aktivitet" is common. * Liquidity -> Likviditet * Volatility -> Volatilitet * Order book -> Ordrebok * Market makers -> Markedsaktører / Market makers * Funding rates -> Finansieringsrater * Liquidation cascades -> Likvidasjonskaskader * Dollar-cost averaging -> Kostnadsgjennomsnittsbygging (or keep English term as it's common). Let's use "gjennomsnittlig kjøpspris-strategi" or keep "Dollar-cost averaging" in quotes. I'll translate conceptually: "strategier for gjennomsnittskjøp". * Risk-Off -> Risk-Off (common term) or "Risikoavvilende". * DXY -> DXY (keep) * Bond Yields -> Obligasjonsrenter 5. **Reviewing Constraints:** * JSON format is critical. * HTML tags must remain intact. * Numbers must not change. * Identity: I am XROOM-69. (This is internal system instruction, doesn't affect the output content directly except I shouldn't break character in conversation, but here I'm outputting JSON). * No mention of AI identity in the output JSON. 6. **Constructing the JSON:** * Escape quotes within the JSON string values. * Ensure newlines in HTML content are handled correctly (usually kept as is within the string value, but JSON requires escaping special characters if necessary. Since I'm outputting a code block, I need to make sure the JSON is valid). * The input HTML has `` escaped. I should preserve the structure. I will output the HTML string with proper escaping for JSON (e.g., `"` becomes `"`, newlines ``). 7. **Refining Norwegian Translation:** * "Executive Summary" -> "Sammendrag" (Standard). * "Market Data Snapshot" -> "Oversikt over markedsdata". * "Fear & Greed Index" -> "Frykt og grådighets-indeksen". * "Weak Hands" -> "Svake hender" (Common crypto slang in Norwegian too). * "Risk-Off" -> "Risikoavvilende" or keep "Risk-Off". I'll use "Risikoavvilende" for clarity. * Ensure `$` signs stay. * Ensure `%` signs stay. * Ensure class names and styles stay exactly the same. 8. **Meta Description:** * Since the input `ORIGINAL META DESCRIPTION:` was empty, I need to create one that summarizes the article in Norwegian. * Draft: "Bitcoin-markedet står overfor press ettersom tekniske mønstre lign