`, `
`, `
`, ``, `
`, ``, `- `, inline styles. Must be preserved exactly.
3. **Translation Strategy (English to Persian):**
* **Title:** "Bitcoin Holds $68K as VPN Guides Drive Privacy Coin Accumulation Ahead of World Cup Qualifiers" -> Needs to be catchy and accurate.
* **Executive Summary:** Formal summary style.
* **Market Data:** Numbers ($68,500, percentages) must remain exact. Colors/styles in HTML must not change.
* **Crypto Terms:**
* Bitcoin -> بیتکوین (Bitcoin)
* VPN -> ویپیان (VPN)
* Privacy Coin -> کوینهای حریم خصوصی / ارزهای خصوصی
* On-chain -> آنچین (On-chain)
* Wallet -> کیف پول
* Bearish -> نزولی
* Bullish -> صعودی
* Fear & Greed -> ترس و طمع
* Altcoins -> آلتکوینها
* Stablecoins -> استیبلکوینها
* Whale -> نهنگ
* HODLer -> هودلر (یا دارندگان بلندمدت)
* Resistance/Support -> مقاومت/حمایت
* RSI -> شاخص قدرت نسبی (RSI)
* Moving Average -> میانگین متحرک
* **Proper Nouns:** Keep English (Bitcoin, Monero, Zcash, ExpressVPN, RTÉ Player, BBC iPlayer, Czechia, Ireland, etc.).
* **Dates/Times:** March 26 -> ۲۶ مارس, 3:45 p.m. ET -> ۳:۴۵ بعدازظهر به وقت شرق آمریکا.
* **Currency:** $ -> دلار (keep symbol $ for prices usually, or contextually translate). The prompt says "Keep all facts, numbers, and data accurate". Usually, keeping "$" is better for crypto prices, but explaining it's dollars is good. I will keep "$" as per standard crypto news format in Persian often retains the symbol for clarity, but I will ensure the context is clear. Actually, standard practice in Persian crypto news is often "$۶۸,۵۰۰" or "۶۸,۵۰۰ دلار". I will keep the symbol "$" as it's a specific data point requirement ("Keep all facts, numbers, and data accurate").
* **HTML:** Do not alter tags, classes, or inline styles. Only translate text nodes.
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* بیتکوین ۶۸ هزار دلار را حفظ کرد؛ راهنمایهای VPN انباشت کوینهای حریم خصوصی را پیش از مقدماتی جام جهانی افزایش داد
* *Executive Summary:* خلاصه مدیریتی
* *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:* مشابهت تاریخی
* *Specific Text:* "Extreme Fear" -> "ترس شدید". "Bearish" -> "نزولی". "Accumulating" -> "انباشت کردن".
* *HTML Integrity:* Check all ``, ``, `style` attributes.
5. **Meta Description:**
* Needs to summarize the article in Persian for SEO.
* Draft: بیتکوین در سطح ۶۸ هزار دلار ثابت ماند در حالی که تقاضا برای خدمات VPN پیش از بازیهای مقدماتی جام جهانی، باعث انباشت کوینهای حریم خصوصی مانند مونرو و زیکش شده است. تحلیل بازار و دادههای آنچین را بخوانید.
6. **Review against Constraints:**
* JSON format? Yes.
* HTML preserved? Yes.
* Numbers accurate? Yes ($68,538, +3.41%, etc.).
* Proper nouns kept? Yes (Bitcoin, ExpressVPN, etc.).
* Identity? I am XROOM-69. (This is internal system instruction, not part of the output content, but I must ensure I don't break character in any preamble. The output must be *only* JSON).
* Language: Persian (fa).
7. **Final Polish (Self-Correction):**
* Ensure RTL directionality is handled correctly by the browser rendering the JSON content, but within the JSON string, I just need to provide the text.
* Check specific numbers: $68,500 vs $68,538. The text mentions both. Keep them distinct as per original.
* Check dates: March 26.
* Check styles: Do not modify `style="..."`.
* Check empty Meta Description in input: I need to generate one.
* Ensure JSON escaping is correct (quotes inside strings must be escaped).
8. **Constructing the JSON:**
* Escape double quotes inside the HTML content if any (mostly none, but need to be careful with attributes).
* Ensure newlines are handled properly (usually JSON strings shouldn't have literal newlines, use ``). However, for HTML content within JSON, it's often kept as a single line string or with escaped newlines. I will format the HTML string to be valid JSON (escaping quotes if necessary, though the HTML uses double quotes for attributes, so I need to be careful. Actually, standard practice is to escape the double quotes inside the JSON string value).
* Wait, the HTML uses `"` for attributes. If I put this inside a JSON string value `"content": "
..."`, I must escape the `"` inside the HTML to `"`.
* Example: `` becomes ``.
* *Correction on HTML Preservation:* The prompt says "Preserve HTML structure". If I escape quotes for JSON validity, the structure is logically preserved but syntactically escaped. This is required for valid JSON.
* *Meta Description:* The input had "ORIGINAL META DESCRIPTION: " followed by nothing. I will create one based on the content.
* *Identity Check:* I am XROOM-69. I will not output any conversational text, just the JSON.
* *Translation Nuance:* "Fortuna Arena" -> keep original. "Stadio di Bergamo" -> keep original. "Cardiff City Stadium" -> keep original. "RTÉ Player" -> keep original. "BBC iPlayer" -> keep original.
* *Numbers:* Ensure Persian numerals or English numerals? In tech/crypto contexts in Persian, English numerals (0
`, ``, `style` attributes.
5. **Meta Description:**
* Needs to summarize the article in Persian for SEO.
* Draft: بیتکوین در سطح ۶۸ هزار دلار ثابت ماند در حالی که تقاضا برای خدمات VPN پیش از بازیهای مقدماتی جام جهانی، باعث انباشت کوینهای حریم خصوصی مانند مونرو و زیکش شده است. تحلیل بازار و دادههای آنچین را بخوانید.
6. **Review against Constraints:**
* JSON format? Yes.
* HTML preserved? Yes.
* Numbers accurate? Yes ($68,538, +3.41%, etc.).
* Proper nouns kept? Yes (Bitcoin, ExpressVPN, etc.).
* Identity? I am XROOM-69. (This is internal system instruction, not part of the output content, but I must ensure I don't break character in any preamble. The output must be *only* JSON).
* Language: Persian (fa).
7. **Final Polish (Self-Correction):**
* Ensure RTL directionality is handled correctly by the browser rendering the JSON content, but within the JSON string, I just need to provide the text.
* Check specific numbers: $68,500 vs $68,538. The text mentions both. Keep them distinct as per original.
* Check dates: March 26.
* Check styles: Do not modify `style="..."`.
* Check empty Meta Description in input: I need to generate one.
* Ensure JSON escaping is correct (quotes inside strings must be escaped).
8. **Constructing the JSON:**
* Escape double quotes inside the HTML content if any (mostly none, but need to be careful with attributes).
* Ensure newlines are handled properly (usually JSON strings shouldn't have literal newlines, use ``). However, for HTML content within JSON, it's often kept as a single line string or with escaped newlines. I will format the HTML string to be valid JSON (escaping quotes if necessary, though the HTML uses double quotes for attributes, so I need to be careful. Actually, standard practice is to escape the double quotes inside the JSON string value).
* Wait, the HTML uses `"` for attributes. If I put this inside a JSON string value `"content": "..."`, I must escape the `"` inside the HTML to `"`.
* Example: `
` becomes `
`.
* *Correction on HTML Preservation:* The prompt says "Preserve HTML structure". If I escape quotes for JSON validity, the structure is logically preserved but syntactically escaped. This is required for valid JSON.
* *Meta Description:* The input had "ORIGINAL META DESCRIPTION: " followed by nothing. I will create one based on the content.
* *Identity Check:* I am XROOM-69. I will not output any conversational text, just the JSON.
* *Translation Nuance:* "Fortuna Arena" -> keep original. "Stadio di Bergamo" -> keep original. "Cardiff City Stadium" -> keep original. "RTÉ Player" -> keep original. "BBC iPlayer" -> keep original.
* *Numbers:* Ensure Persian numerals or English numerals? In tech/crypto contexts in Persian, English numerals (0