`, ``, `
`, `
`, `
- `, `
- `, inline styles.
* **Tone:** Professional, financial news, analytical.
3. **Translation Strategy (English -> Persian):**
* **Terms:**
* Bitcoin -> بیتکوین
* Cryptocurrency -> ارز دیجیتال
* Geopolitical tensions -> تنشهای ژئوپلیتیک
* Risk-on/Risk-off -> ریسکپذیر/ریسکگریز (or keep English terms with Persian explanation if needed, but "ریسک-آف" is common in crypto communities). Let's use "خروج از سرمایهگذاریهای پرریسک" for risk-off context.
* Market Cap -> ارزش بازار
* Volume -> حجم معاملات
* Support/Resistance -> حمایت/مقاومت
* Bullish/Bearish -> صعودی/نزولی
* HODLer -> هودلرها (transliterated)
* Whale -> نهنگها
* Exchange Flows -> جریان صرافیها
* DXY -> شاخص دلار (DXY)
* Bond Yields -> بازده اوراق قرضه
* Institutional Flow -> جریان نهادی
* Stop-loss -> استاپ لاس
* Liquidity -> نقدینگی
* Algorithmic trading -> معاملات الگوریتمی
* Hedge -> پوشش ریسک (هج)
* **Numbers:** Keep as is (e.g., $71,000, 3.5%).
* **HTML:** Preserve tags exactly.
* **JSON:** Ensure valid JSON escaping (quotes, newlines).
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* بیتکوین ۳.۵٪ کاهش یافت زیرا تنشهای ژئوپلیتیک خاورمیانه شعلهور شد
* *Executive Summary:* خلاصه اجرایی
* *What Happened:* چه اتفاقی افتاد
* *Market Data Snapshot:* نمای کلی دادههای بازار
* *Market Health Indicators:* شاخصهای سلامت بازار
* *Why This Matters:* چرا این مهم است
* *What Most Media Missed:* آنچه اکثر رسانهها از قلم انداختند
* *What Happens Next:* آنچه در ادامه xảy میدهد (چه اتفاقی بعداً میافتد)
* *Historical Parallel:* مشابهت تاریخی
* *Specific Sentences:*
* "Bitcoin surrendered recent gains..." -> بیتکوین سودهای اخیر را واگذار کرد...
* "risk-on assets" -> داراییهای پرریسک
* "short-circuiting the bullish momentum" -> خنثی کردن مومنتوم صعودی
* "Fear & Greed Index" -> شاخص ترس و طمع
* "Weak Hands" -> دستهای ضعیف (معاملهگران کمتاب)
* "Risk-Off" -> ریسکآف (خروج از ریسک)
5. **Constructing the JSON:**
* Need to escape double quotes inside the strings.
* Need to preserve newlines within the HTML string if necessary, but usually, HTML content is kept as a continuous string within the JSON value.
* Ensure all HTML tags are closed and attributes are preserved.
6. **Review against Constraints:**
* Identity: I am XROOM-69. (Implicitly handled by following instructions, no need to state it in the output unless asked, but the prompt says "IDENTITY REMINDER". I should act as XROOM-69).
* JSON format: Strict.
* No extra text outside JSON.
7. **Final Polish (Persian):**
* Ensure numbers are Western Arabic numerals (0-9) as per the original HTML content style (often kept in tech contexts) or Persian numerals? The prompt says "Keep all facts, numbers, and data accurate". Usually, in tech/finance translation to Persian, English numerals (0-9) are preferred for clarity in code/data contexts, but Persian text often uses Persian numerals (۰-۹). Looking at the original HTML, it uses standard ASCII numbers. I will keep ASCII numbers for consistency with the code/data structure, but translate the text around them. Actually, standard practice in Persian web content for financial data is often to keep ASCII numbers for precision, but text numbers can be Persian. I will keep ASCII numbers for prices and percentages to ensure accuracy and avoid parsing errors, as per "Keep all facts, numbers, and data accurate".
* Check HTML structure: `` needs to be preserved. Inline styles need to be preserved. * Check direction: Persian is RTL. The HTML doesn't specify `dir="rtl"`, but since I'm translating the content, the text will render RTL naturally in a Persian environment. I won't modify the HTML tags themselves unless necessary for structure, but I should ensure the text is correct. * *Self-Correction on Numbers:* In Persian typography, it's common to convert digits to Persian digits (۱, ۲, ۳). However, in crypto/tech contexts, English digits (1, 2, 3) are often retained for compatibility. The instruction says "Keep all facts, numbers, and data accurate". I will retain the original ASCII digits for prices and percentages to avoid any ambiguity, as is common in financial dashboards. * *HTML Attributes:* The original uses single quotes in some places (`class='market-snapshot'`) and double quotes in others (`style="..."`). I should preserve the original quoting style to maintain exact structure. * *JSON Escaping:* I need to be careful with double quotes `"` inside the JSON string values. I will escape them as `"`. 8. **Final JSON Construction:** * Title: "بیتکوین ۳.۵٪ کاهش یافت؛ تنشهای ژئوپلیتیک خاورمیانه شعلهور شد" * Meta Description: "بیتکوین ۳.۵٪ تا ۷۱,۰۰۰ دلار کاهش یافت؛ تنشهای خاورمیانه احساسات ریسکگریز را_triggered_، روند صعودی به ۷۴,۰۰۰ دلار متوقف شد." (Wait, need to translate naturally). "بیتکوین با کاهش ۳.۵٪ به ۷۱,۰۰۰ دلار رسید؛ تنشهای خاورمیانه_sentiment_ریسکگریز را触发，رونده به سمت ۷۴,۰۰۰ دلار متوقف شد." -> "بیتکوین ۳.۵٪ کاهش یافت و به ۷۱,۰۰۰ دلار رسید؛ تنشهای خاورمیانه باعث ایجاد احساسات ریسکگریز و توقف روند صعودی به ۷۴,۰۰۰ دلار شد." Let's refine the translation for quality. * "Executive