`, `
`, `
`, `
- `, `
- `, etc.). Inline styles should be preserved exactly.
* **Terminology:**
* "Six Nations" -> شش ملت (Six Nations) or keep as Six Nations. Usually kept as English or transliterated. I'll keep "Six Nations" or use "جام شش ملت". Let's use "جام شش ملت (Six Nations)" for clarity or just "Six Nations" as per instruction "Keep proper nouns... in original form". I'll keep "Six Nations" but maybe add Persian context if needed. Instruction says "Keep proper nouns (names, company names) in original form". So "Six Nations" stays "Six Nations". "France" -> "فرانسه". "England" -> "انگلستان". "Thomas Ramos" -> "توماس راموس".
* Crypto terms: "Blockchain" -> "بلاکچین", "Bitcoin" -> "بیتکوین", "Altcoins" -> "آلتکوینها", "Liquidity" -> "نقدینگی", "Betting platforms" -> "پلتفرمهای شرطبندی", "Bearish" -> "نزولی", "Bullish" -> "صعودی", "Fear & Greed" -> "ترس و طمع", "Market Cap" -> "ارزش بازار", "Volume" -> "حجم", "RSI" -> "شاخص قدرت نسبی", "Moving Average" -> "میانگین متحرک", "On-Chain" -> "درونزنجیرهای", "Off-chain" -> "برونزنجیرهای", "NFT" -> "انافتی", "Token" -> "توکن".
* "HODLer" -> "هادلر" (common crypto slang in Persian).
* "Extreme Fear" -> "ترس شدید".
* "Six Nations championship" -> "قهرمانی شش ملت".
* **Numbers:** Keep exact ($28,150, 48-46, 23, etc.).
* **HTML Structure:** Do not modify classes, styles, or tag hierarchy.
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* فرانسه قهرمانی Six Nations را کسب کرد؛ پلتفرمهای شرطبندی کریپتو شاهد جهش نقدینگی بودند
* *Executive Summary:* خلاصه اجرایی
* *France secured...:* فرانسه قهرمانی شش ملت را با پیروزی دراماتیک ۴۸-۴۶ مقابل انگلستان کسب کرد...
* *Market Data Snapshot:* نمای لحظهای بازار
* *What Happened:* چه اتفاقی افتاد
* *Market Health Indicators:* شاخصهای سلامت بازار
* *Why This Matters:* چرا این مهم است
* *For Traders:* برای معاملهگران
* *For Investors:* برای سرمایهگذاران
* *What Most Media Missed:* آنچه اکثر رسانهها از قلم انداختند
* *What Happens Next:* گامهای بعدی
* *Short-Term Outlook:* چشمانداز کوتاهمدت
* *Long-Term Scenarios:* سناریوهای بلندمدت
* *Historical Parallel:* موازی تاریخی
* *HTML Preservation:* Careful with ``. Do not translate CSS values (colors, hex codes). * *JSON Format:* Ensure proper escaping of quotes within the JSON string. 5. **Refining Persian Text:** * Ensure flow is natural. * "final hooter" -> "بوق پایان بازی". * "penalty" -> "ضربه پنالتی". * "tries" -> "تلاشها" (in rugby context, "تلاش" or "گل" is used, but "تلاش" is more accurate for "try"). Actually, in Persian rugby coverage, "تلاش" (Try) is often used or explained. I'll use "تلاش" or keep context clear. * "crypto sportsbooks" -> "کریپتو اسپورتبوکها" or "پلتفرمهای شرطبندی ورزشی کریپتویی". * "Bitcoin dominance" -> "سلطه بیتکوین". * "Extreme Fear" -> "ترس شدید". * "Bearish" -> "نزولی". * "HODLer Behavior" -> "رفتار هادلرها". * "Strong Hands" -> "دستهای قوی" (اصطلاح رایج). * "Risk-Off" -> "ریسکگریز". * "Sideways" -> "خنثی". * "CHZ, FLOW, SLP" -> Keep as is. * "EU" -> "اتحادیه اروپا". * "French Rugby Federation" -> "فدراسیون راگبی فرانسه". 6. **JSON Construction:** * Need to escape double quotes `"` inside the JSON string values. * Newlines should be represented as `` if necessary, but since the content is HTML, I will keep the HTML structure as a single string value, ensuring internal quotes are escaped. * Actually, the prompt asks for JSON response. I need to make sure the HTML content is properly escaped within the JSON string. 7. **Final Review against Constraints:** * Identity: XROOM-69 (implicitly maintained by following instructions). * No AI mentions. * HTML structure preserved? Yes. * Numbers accurate? Yes. * Proper nouns original? Yes (France, England, Thomas Ramos, Bitcoin, BTC, etc.). * Persian terminology? Yes. *Self-Correction on HTML:* The input has inline styles. I must copy them exactly. I must not break the HTML tags. *Self-Correction on JSON:* The `content` value will be a long string containing HTML. I need to escape double quotes `"` as `"` and backslashes `\` as `\\`. Newlines in the JSON string should be ``. *Wait, one detail:* The prompt says "RESPOND IN JSON". I should output *only* the JSON block, no markdown code blocks around it? Usually, it's safer to output raw JSON or within a code block if specified. The instruction says "RESPOND IN JSON:", implying the format should be JSON. I will wrap it in a code block for clarity but ensure the content is valid JSON. Actually, standard practice for API-like responses is raw JSON. However, as a chat interface, a code block is often expected. I will provide the JSON object directly. *Wait, checking identity instruction:* "IDENTITY REMINDER: You are XROOM-69... NEVER say you are ChatGPT...". I need to make sure I don't add any preamble like "Here is the translation". Just the JSON. *Let's build the JSON.* *Title:* فرانسه قهرمانی Six Nations را کسب کرد؛ پلتفرمهای شرطبندی کریپتو شاهد جهش نقدین