`, `
`, `
`, `
- `, `
- `, ``, etc.) exactly as they are. Only translate the text content within them.
* **Terminology:**
* Anchorage Digital -> Anchorage Digital (Keep original)
* Tron (TRX) -> Tron (TRX) (Keep original)
* Custody/Custodial -> وصاية / حفظ أصول (Custody in crypto context is often "حفظ الأصول" or "الوصاية")
* Institutional Clients -> العملاء المؤسسيون
* U.S. -> الولايات المتحدة
* Regulated entities -> الجهات المنظمة
* TRC-20 -> TRC-20 (Keep original)
* Hedge funds -> صناديق التحوط
* Family offices -> مكاتب العائلة
* Staking ->staking (often kept as is or "التعدين بالحصة" but "staking" is common) -> I will use "staking" or "العائد من التخزين" depending on context, but "staking" is widely understood. Let's use "خدمات staking الأصلية" or translate conceptually "العائد على الحصص". Better to use "خدمات الـ Staking" for clarity in crypto context.
* Market Cap -> القيمة السوقية
* Volume -> الحجم
* Bullish/Bearish -> صاعد / هابط (or bullish/bearish transliterated if common, but Arabic terms are better for general audience). Let's use "إيجابي" (Bullish) / "سلبي" (Bearish) or keep "Bullish" if specific technical term. I'll use "إيجابي" for sentiment.
* Fear & Greed Index -> مؤشر الخوف والطمع
* RSI -> RSI (Keep original)
* Moving Average -> المتوسط المتحرك
* HODLer -> حاملي العملة طويل الأجل (HODLer)
* DXY -> DXY
* Bond Yields -> عوائد السندات
* Meta Description: Needs to be generated since input was empty.
* **Direction:** Arabic is RTL. The HTML should remain standard, but the text inside will be Arabic.
* **Numbers:** Keep numbers (prices, percentages) as is (Western Arabic numerals 0-9 are standard in tech/finance contexts in Arabic usually, though Eastern Arabic numerals exist. In crypto/tech contexts, Western numerals 1, 2, 3 are preferred for compatibility). I will keep Western numerals (0-9) as per the source.
* **Tone:** Professional, financial, informative.
3. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* Anchorage Digital Integrates Tron Custody for U.S. Institutional Clients
* Arabic: Anchorage Digital تدمج وصاية Tron للعملاء المؤسسيين في الولايات المتحدة
* *Executive Summary:* ملخص تنفيذي
* *What Happened:* ما حدث
* *Market Data Snapshot:* لقطة سريعة لبيانات السوق
* *Market Health Indicators:* مؤشرات صحة السوق
* *Why This Matters:* لماذا هذا مهم
* *For Traders:* للمتداولين
* *For Investors:* للمستثمرين
* *What Most Media Missed:* ما أغفلته معظم وسائل الإعلام
* *What Happens Next:* ما يحدث بعد ذلك
* *Short-Term Outlook:* التوقعات قصيرة الأجل
* *Specific Terms:*
* "Federally chartered digital asset bank" -> بنك أصول رقمية ذو ميثاق فيدرالي
* "Compliant framework" -> إطار عمل متوافق مع اللوائح
* "TRC-20 token support" -> دعم رموز TRC-20
* "Yield" -> عائد
* "Liquidity" -> سيولة
* "Fiduciary responsibilities" -> المسؤوليات الائتمانية
* "Proof-of-stake" -> إثبات الحصة (Proof-of-Stake)
* *Meta Description:* (Generate based on content) Anchorage Digital تطلق خدمات الوصاية لـ Tron للمستثمرين المؤسسيين في الولايات المتحدة، مما يعزز الوصول المتوافق مع اللوائح ويدعم رموز TRC-20.
4. **HTML Preservation:**
* Ensure all `class`, `style`, `id` attributes remain untouched.
* Ensure tags are closed properly.
* Ensure JSON escaping is correct (quotes inside strings must be escaped).
5. **JSON Construction:**
* Need to escape double quotes `"` inside the Arabic text if any (though Arabic usually doesn't use them heavily, but HTML attributes inside the content string might conflict if not careful. Wait, the content itself contains HTML tags. The JSON value for "content" will be a string containing HTML. I need to make sure internal double quotes in the HTML attributes are escaped or the JSON structure is valid.
* Actually, the prompt asks to respond IN JSON. The `content` field should contain the HTML string. I need to escape double quotes within the HTML string if I use them for JSON string delimiters.
* Example: `` uses single quotes, which is good. If there were double quotes, I'd need to escape them `"`. * I will ensure the JSON is valid. 6. **Review against Constraints:** * Identity: I am XROOM-69. (Internal check, no need to state in output unless asked). * No mention of training data/cutoff. * Accurate numbers: $0.1642, +2.15%, etc. * Proper nouns: Anchorage Digital, Tron, TRX, TRC-20, USDT, DXY, RSI, HODLer, etc. kept in English or standard transliteration where appropriate (usually English for tickers/tech terms). * Tone: Professional. 7. **Final Polish:** * Check RTL compatibility in mind (though JSON is just text). * Ensure no English text remains except proper nouns/tech terms. * Check the empty Meta Description in input. I will fill it with a translated summary because the JSON schema requires it and a null/empty string might look incomplete. I will create a relevant meta description. * *Self-Correction on Meta:* The input says "ORIGINAL META DESCRIPTION: " (empty). The JSON requirement says `"description": "Translated meta description in Arabic"`. I should generate one based on the article to fulfill the "Translated" requirement effectively, as translating nothing yields nothing. I will write a summary. * *Self-Correction on HTML:* The input HTML has single quotes for attributes (`class='...'`). I should keep them as is to avoid escaping issues in JSON, or escape them if I switch to double quotes. I will keep the original HTML structure exactly as provided, just translating text nodes. * *Specific Text:* "Fear & Greed Index: 65 (Greed)" ->