** Needs to be concise and accurate.

`, `

`, `

`, `

`, `
• `, etc.). Do not translate attribute values unless they are content (e.g., `class` names stay English). * **Proper Nouns:** Nvidia, California, GPU, NVDA, RSI, DXY, HODLer, ETFs, SKUs, etc., should remain in English or transliterated if commonly used in Arabic tech context (usually English is preferred for tickers and specific tech acronyms). * **Crypto/Tech Terms:** * Class-action lawsuit -> دعوى جماعية * Certified -> certify -> اعتمد / certify status -> منح صفة * Semiconductor -> أشباه الموصلات * Revenue -> إيرادات * Cryptocurrency mining -> تعدين العملات المشفرة * Volatile -> متقلبة * Securities fraud -> احتيال أوراق مالية * Market Cap -> القيمة السوقية * Bearish/Bullish -> هبوطي / صعودي * Support/Resistance -> دعم / مقاومة * Discovery phase -> مرحلة الاكتشاف (legal context) -> مرحلة جمع الأدلة/الاستقصاء * Subpoenas -> مذكرات إحضار * **Numbers:** Keep exactly as is ($118.50, 2.15%, etc.). * **Direction:** Arabic is RTL, but the JSON output doesn't need specific direction markers unless inside the HTML content (which usually handles it via `dir="auto"` or CSS, but I should just output the text). The HTML structure provided doesn't have `dir` attributes, so I will just translate the text content within the tags. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Judge Certifies Investor Lawsuit Against Nvidia Over Hidden Crypto Revenue -> قاضٍ يعتمد دعوى مستثمرين ضد Nvidia بشأن إيرادات تعدين مشفرة مخفية * *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:* التوقعات قصيرة الأجل * *Long-Term Scenarios:* السيناريوهات طويلة الأجل * *Historical Parallel:* مقارنة تاريخية * *Specific Terms:* * "Class-action lawsuit" -> "دعوى جماعية" * "Semiconductor giant" -> "عملاق أشباه الموصلات" * "GPU" -> "GPU" (keep English) * "NVDA" -> "NVDA" * "Bearish" -> "هبوطي" * "Fear & Greed Index" -> "مؤشر الخوف والطمع" * "On-Chain Signal" -> "إشارة على السلسلة" * "HODLer" -> "HODLer" (keep English as it's specific crypto slang) * "DXY" -> "DXY" * "ETFs" -> "صناديق المؤشرات المتداولة (ETFs)" or just "ETFs" * "SKUs" -> "SKUs" * *HTML Preservation:* Ensure all `
  `, `` remain intact. Only text nodes change. 5. **Reviewing Constraints:** * JSON format is mandatory. * No markdown outside JSON (though the prompt says "RESPOND IN JSON", usually I should output raw JSON block). * Identity: XROOM-69. (This is a system instruction, I don't need to state it in the output unless asked, but I must adhere to it). * Accuracy: Check numbers ($118.50, -2.15%, etc.). 6. **Constructing the JSON:** * Escape quotes within the JSON string values. * Ensure newlines in HTML are preserved or handled correctly within the JSON string (usually single line or escaped newlines). I will keep the HTML structure compact but readable within the string value. 7. **Final Polish (Arabic):** * Ensure flow is natural. * Example: "Jurisdictional details confirm..." -> "تؤكد التفاصيل القضائية..." * Example: "Weak Hands" -> "أيدي ضعيفة" (common crypto translation) or keep English context. Let's use "أيدي ضعيفة" as it's understood in Arabic crypto communities, or keep "Weak Hands" if unsure. Better to translate meaning: "مستثمرون ذوو أيدي ضعيفة" or just "أيدي ضعيفة". Let's go with "أيدي ضعيفة" for naturalness. * Example: "Risk-Off" -> "تجنب المخاطر". * Example: "Headwind" -> "عائق رياحي" -> "عائق". * *Refining Legal Terms:* "Certified" in legal context -> "اعتمد المحكمة" or "منح الصفة". "Class-action status" -> "صفة الدعوى الجماعية". * *Refining Tech Terms:* "Discovery processes" -> "عمليات الكشف عن الأدلة". * *Checking HTML:* * `

  ` -> Keep class. * `

  ` -> Keep class and style. * Colors in style (`#f39c12`, etc.) -> Keep. * *Meta Description:* Translate accurately. 8. **Final JSON Construction:** * Escape double quotes inside the content string. * Ensure no trailing commas. *Self-Correction on JSON Escaping:* Since the content contains HTML with double quotes (e.g., `class='...'` uses single quotes in the source, which is good. But if I use double quotes in JSON value, I need to escape any double quotes inside the HTML. The source HTML uses single quotes for attributes `class='...'` and `style='...'`, which makes JSON escaping easier. I will maintain single quotes in HTML attributes to avoid excessive escaping.) *Wait, one detail:* The source HTML uses single quotes for attributes (`class='market-snapshot'`). This is valid HTML. I will keep them as is to minimize JSON escaping issues. *Let's check the text content for double quotes.* "Primary Asset:" -> No double quotes. "Current Price:" -> No double quotes. Text like "Weak Hands" -> I will translate but keep English terms if necessary. Text like "Risk-Off" -> Translate. *Let's assemble.* *Title:* قاضٍ يعتمد دعوى مستثمرين ضد Nvidia بشأن إيرادات تعدين مشفرة مخفية *Meta:* قاضٍ اتحادي يعتمد دعوى جماعية ضد Nvidia بشأن إيرادات تعدين العملات المشفرة غير المعلنة، مما ينقل القضية نحو المحاكمة مع تداعيات كبيرة على معايير الإفصاح التقني. *Content:* Translate section by section. *Executive Summary:* "أقر قاضٍ اتح