`, `
`, `
`, `
- `, `
- `, `
`, inline styles. * **Terminology:** Bitcoin, BTC, Market Cap, Volume, Sentiment, Fear & Greed Index, On-Chain, HODLer, DXY, Bond Yields, RSI, Moving Average, Support/Resistance, Bullish/Bearish, etc. 3. **Translation Strategy (English -> Persian):** * *Tone:* Professional, financial/crypto news style. * *Terms:* * Bitcoin -> بیتکوین * Price -> قیمت * Social Sentiment -> احساسات اجتماعی /_sentiment_ اجتماعی (usually "احساسات بازار" or "SENTIMENT اجتماعی" works, but "احساسات اجتماعی" is literal. In crypto context, "احساسات جامعه" or just "SENTIMENT" is often used. Let's use "احساسات اجتماعی" for accuracy to the text, or "احساسات بازار" if it fits better. The text says "Social Sentiment", so "احساسات اجتماعی" is precise.) * Historic Lows -> پایینترین سطح تاریخی * Executive Summary -> خلاصه مدیریتی * Trading levels -> سطوح معاملاتی * Institutional actors -> بازیگران نهادی * Retail participants -> مشارکتکنندگان خرد * Liquidity -> نقدینگی * On-chain activity -> فعالیتهای زنجیرهای (On-chain) * Futures markets -> بازارهای آتی * Market Cap -> ارزش بازار * Fear & Greed Index -> شاخص ترس و طمع * Support/Resistance -> حمایت/مقاومت * HODLer -> هودلرها (keep as is or translate concept? Usually kept as HODLer or translated as "دارندگان بلندمدت". Let's use "هودلرها" with context or "دارندگان بلندمدت". The text says "Strong Hands", so "دستان قوی" is literal, but "دارندگان متعهد" is better. Let's stick close to crypto slang: "هودلرها" behavior.) * DXY -> شاخص دلار (DXY) * Bond Yields -> بازده اوراق قرضه * Consolidation -> تثبیت / رنج زدن * Leverage -> اهرم * *Specific Note on "Iran-Iraq war":* The text says "thresholds not observed since the onset of the Iran‑Iraq war". This is a very specific claim. I must translate it faithfully: "از آغاز جنگ ایران و عراق مشاهده نشده است". * *Specific Note on "community情绪":* Wait, looking at the source text provided in the prompt: `creating a notable disconnect between market valuation and community情绪`. There is a Chinese character `情绪` (meaning sentiment/mood) in the English source text provided in the prompt. This looks like an artifact or error in the provided source text. As a translator, I should translate the *meaning*. `community情绪` means `community sentiment`. I will translate it as "احساسات جامعه" to maintain the meaning in Persian, ignoring the Chinese character glitch in the source. * *HTML Preservation:* Ensure all tags, classes, and styles remain exactly as is. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* قیمت بیتکوین با ثبات میماند در حالی که احساسات اجتماعی به پایینترین سطح تاریخی میرسد * *Exec Summary:* بیتکوین سطوح معاملاتی باثباتی را حفظ کرد... * *What Happened:* میزهای معاملاتی نقدینگی ثابتی گزارش کردند... * *Data Snapshot:* قیمت فعلی، تغییر قیمت، etc. * *Health Indicators:* Technical Signals -> سیگنالهای تکنیکال. On-Chain Health -> سلامت زنجیرهای. * *Why Matters:* For Traders -> برای تریدرها. For Investors -> برای سرمایهگذاران. * *Media Missed:* آنچه اکثر رسانهها از قلم انداختند. * *Next:* چشمانداز کوتاهمدت، سناریوهای بلندمدت. * *History:* موازی تاریخی. 5. **Reviewing Constraints:** * JSON format. * No markdown outside JSON (except the code block if needed, but the prompt says "RESPOND IN JSON"). I will output raw JSON inside a code block or just raw JSON? Usually, for API-like responses, raw JSON is better, but within a chat interface, a code block is safer for parsing. The prompt says "RESPOND IN JSON", I will provide the JSON structure directly. * Identity: I am XROOM-69. (Implicitly handled by not breaking character). * Check for the Chinese character glitch in source: `community情绪`. I will translate it as "احساسات جامعه" (community sentiment) to make sense in Persian. * Check numbers: $67,450, 54.2%, etc. Must be exact. * Check HTML: `
`, inline styles must be preserved. 6. **Final Polish (Persian):** * Ensure right-to-left (RTL) direction is implied by the content (Persian text). * Ensure numbers are kept in English format (as per standard tech/finance in Iran often uses English digits, but Persian digits are also acceptable. The prompt says "Keep all facts, numbers, and data accurate". Usually, keeping English digits ($67,450) is safer for data accuracy in code/HTML contexts. I will keep English digits for currency and percentages to avoid confusion, but translate the text around them.) * Actually, standard Persian localization often converts digits to Persian (۰۱۲۳...). However, in crypto/tech contexts, English digits are very common. The instruction "Keep all facts, numbers, and data accurate" suggests not changing the value. I will keep English digits for prices and percentages to ensure clarity and accuracy matching the source, but translate the labels. * Wait, one specific instruction: "Keep proper nouns (names, company names) in original form". * Let's refine the "Iran-Iraq war" translation. "جنگ ایران و عراق". * Let's refine "community情绪". I will treat it as "community sentiment" -> "احساسات جامعه". 7. **Constructing JSON:** * Escape quotes properly. * Ensure newlines in HTML are preserved or handled correctly within JSON string (using ``). *Self-Correction on JSON formatting:* HTML inside JSON strings needs careful escaping. Double quotes inside HTML attributes must be escaped or the HTML should use single quotes (which it mostly does in the source: `class='market-snapshot'`). The source uses single quotes for attributes, which is good for JSON double-quoted strings. I need to make sure I don't introduce unescaped double quotes. *Source Check:* `` (Single quotes).