`, `
`, `
`, `
- `, `
- `, `
`, ``. Classes and styles need to be preserved. 3. **Translation Strategy (Persian):** * **Tone:** Professional, informative, journalistic. * **Crypto/Tech Terms:** * Quantum Computer: رایانه کوانتومی * Bitcoin: بیتکوین * Proof-of-work: اثبات کار * BTC: BTC (keep symbol) * Qubits: کیوبیت * Cryptographic security: امنیت رمزنگاری * Wallet: کیف پول * Address formats: فرمتهای آدرس * Market Cap: ارزش بازار * Volume: حجم معاملات * Sentiment: احساسات بازار * Fear & Greed Index: شاخص ترس و طمع * On-Chain: آنچین (or زنجیرهای) * Support/Resistance: حمایت/مقاومت * RSI: شاخص قدرت نسبی (RSI) * Moving Average: میانگین متحرک * HODLer: هولدر (or سرمایهگذار بلندمدت) * DXY: شاخص دلار (DXY) * Bond Yields: بازده اوراق قرضه * **Proper Nouns:** Google, Bitcoin, BTC, Twitter (not present), Media outlets (keep generic or translate contextually). * **HTML Structure:** Must remain exactly as is, only text content translated. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* مقاله تحقیقاتی گوگل ادعا میکند رایانه کوانتومی میتواند بیتکوین را در ۹ دقیقه شکست دهد * *Executive Summary:* خلاصه مدیریتی * *Google has released...:* گوگل یک مقاله تحقیقاتی جدید در زمینه رایانش کوانتومی منتشر کرده است... * *6.9 million BTC:* حدود ۶.۹ میلیون BTC * *What Happened:* چه اتفاقی افتاد * *Market Data Snapshot:* نمای کلی دادههای بازار * *Market Health Indicators:* شاخصهای سلامت بازار * *Technical Signals:* سیگنالهای تکنیکال * *On-Chain Health:* سلامت آنچین * *Macro Environment:* محیط کلان اقتصادی * *Why This Matters:* چرا این موضوع مهم است * *For Traders:* برای معاملهگران * *For Investors:* برای سرمایهگذاران * *What Most Media Missed:* آنچه اکثر رسانهها از قلم انداختند * *What Happens Next:*接下来 چه اتفاقی میافتد (بعد چه میشود) * *Short-Term Outlook:* چشمانداز کوتاهمدت * *Meta Description:* Needs to be generated based on the content since the original was empty/missing in the prompt provided (ORIGINAL META DESCRIPTION: [Empty]). I will create a concise summary in Persian. 5. **Reviewing Constraints:** * **JSON Format:** Ensure valid JSON (escape quotes, newlines). * **HTML Preservation:** Keep classes, styles, tags intact. * **Numbers:** Keep English numerals or convert to Persian numerals? Usually, in tech/finance contexts in Persian, English numerals (0-9) are often kept for clarity, especially in code/HTML contexts, but standard Persian text uses Persian numerals (۰-۹). Given the instruction "Keep all facts, numbers, and data accurate", keeping them as digits is safer for copy-pasting, but Persian localization often prefers Persian digits. However, in crypto/tech HTML content, English digits are very common. I will use Persian digits for text flow but keep currency symbols and specific data points clear. Actually, standard practice for professional Persian tech news often keeps English digits for prices and percentages to avoid confusion. I will stick to English digits for prices/percentages to ensure accuracy and ease of reading for traders, but Persian digits for counts like "9 minutes" could go either way. Let's use Persian digits for general text numbers (۹ دقیقه) and keep financial data precise (often English digits are preferred in charts). To be safe and natural, I will use Persian digits for text narratives (۹ دقیقه، ۶.۹ میلیون) but keep financial figures clear. Actually, consistency is key. I will use Persian numerals for the text body to make it natural Persian, but keep symbols like $ and % as is. * *Correction:* In professional Persian financial contexts, English numerals (1, 2, 3) are often preferred for prices and percentages to avoid ambiguity with copy-pasting into trading tools. I will keep prices/percentages in English numerals (e.g., $67,450) but translate counts like "9 minutes" to Persian numerals (۹ دقیقه) for natural flow, or keep them English for consistency. Let's look at the instruction: "Keep all facts, numbers, and data accurate". I will use Persian numerals for the narrative text (۹ دقیقه) but keep the market data table numbers as they are (English) because that's standard for trading interfaces, or convert them consistently. Let's convert narrative numbers to Persian (۹، ۶.۹) and keep market data precise (often English is better for data). Actually, to be most natural in a translated article, Persian numerals are expected. I will use Persian numerals for all numbers within the text for consistency, except maybe inside the specific data snapshot where English is standard. No, better to be consistent. I will use Persian numerals for all numbers in the text to ensure it looks like a proper Persian translation. * *Wait, re-evaluation:* In crypto news translated to Persian, prices like $67,450 are almost always kept with English digits to prevent confusion with trading platforms. I will keep market data numbers in English digits, but narrative numbers (9 minutes, 6.9 million) can be Persian. Actually, let's keep all digits English for data accuracy and ease of reading technical data, but write the text in Persian. This is a common hybrid style in Persian tech news. * *Decision:* I will use Persian numerals for general text (۹ دقیقه) and English numerals for financial data tables to maintain precision and standard formatting for traders. * *HTML:* Must be escaped properly in JSON. 6. **Constructing the JSON:** * Need to escape double quotes inside the HTML content. * Need to ensure newlines are handled (though JSON strings can contain ). * Meta description needs to be created since the original was empty. 7. **Final Polish:** * Check