`, `
`, `
`, `
- `, `
- `, `
`, inline styles. 3. **Translation Strategy (English -> Portuguese):** * *Tone:* Professional, journalistic, financial/tech analysis. * *Terms:* * Class-action lawsuit -> Ação coletiva / Ação de classe (Ação coletiva is more common in PT-BR context for securities). * Semiconductor -> Semicondutor. * GPU -> GPU (keep acronym) / Unidades de Processamento Gráfico. * Crypto mining -> Mineração de criptomoedas. * Securities fraud -> Fraude de valores mobiliários. * Discovery processes -> Fase de descoberta de provas / Instrução processual. * ETFs -> ETFs (keep acronym). * Bearish/Bullish -> Baista/Altista. * Support/Resistance -> Suporte/Resistência. * RSI -> IFR (Índice de Força Relativa) - *Decision:* Keep RSI as it's widely recognized, or use IFR. Given the tech/crypto context, RSI is often kept, but IFR is the proper PT translation. I will use "RSI" but maybe add context or stick to common usage. In Brazilian crypto markets, "RSI" is very common. I'll keep "RSI" for consistency with the original acronym but ensure the context is clear. Actually, "IFR" is the standard translation. Let's use "RSI (14d)" as in the original to preserve data accuracy, but translate the label if needed. The prompt says "Keep all facts, numbers, and data accurate". Changing RSI to IFR might be considered a localization change. I will keep "RSI" as it's a universal ticker symbol in trading platforms used in Brazil too, but translate the surrounding text. * HODLer -> HODLer (crypto slang, keep). * DXY -> DXY (Dollar Index). * Bond Yields -> Rendimentos de Títulos. * Risk-Off -> Aversão ao risco. * Whale -> Baleia. * Inflow/Outflow -> Entrada/Saída. * SKUs -> SKUs (keep). * Earnings calls -> Conferências de resultados. * *Structure:* Must remain exactly the same (tags, classes, styles). * *Proper Nouns:* Nvidia, California, Federal Judge, etc. keep as is or adapt slightly for grammar (e.g., "Nvidia" stays "Nvidia", "California" stays "Califórnia" usually, but prompt says "Keep proper nouns... in original form". I will keep "California" as "Califórnia" is the translated name of the place, but "Nvidia" stays "Nvidia". Actually, standard translation practice translates location names (California -> Califórnia). The prompt says "Keep proper nouns (names, company names) in original form". Usually, this means brand names. Geographic locations are often translated. I will translate geographic locations for natural flow (Califórnia) but keep company names (Nvidia Corporation). * *JSON Escaping:* Ensure quotes and newlines are properly escaped within the JSON string. 4. **Drafting the Translation (Mental or Scratchpad):** * *Title:* Juiz Certifica Ação Coletiva de Investidores Contra a Nvidia Por Receita Cripto Oculta * *Executive Summary:* Um juiz federal na Califórnia certificou oficialmente... * *What Happened:* A ordem do concede status de ação coletiva... * *Market Data:* Snapshot -> Instantâneo. Asset -> Ativo. Price -> Preço. Change -> Variação. Cap -> Capitalização. Sentiment -> Sentimento. * *Health Indicators:* Technical Signals -> Sinais Técnicos. Support -> Suporte. Resistance -> Resistência. Oversold -> Sobrevendido. Moving Average -> Média Móvel. On-Chain Health -> Saúde On-Chain. Network Activity -> Atividade da Rede. Whale Activity -> Atividade de Baleias. Exchange Flows -> Fluxos de Corretoras. HODLer Behavior -> Comportamento dos HODLers. Macro Environment -> Ambiente Macro. DXY Impact -> Impacto do DXY. Bond Yields -> Rendimentos de Títulos. Risk Appetite -> Apetite ao Risco. Institutional Flow -> Fluxo Institucional. * *Why This Matters:* Por Que Isso Importa. Traders -> Traders (or Negociantes). Investors -> Investidores. * *What Most Media Missed:* O Que a Maioria da Mídia Perdeu. * *What Happens Next:* O Que Acontece Depois. Short-Term Outlook -> Perspectiva de Curto Prazo. Long-Term Scenarios -> Cenários de Longo Prazo. * *Historical Parallel:* Paralelo Histórico. Dot-com bubble -> Bolha pontocom. 5. **Reviewing Constraints:** * JSON format is critical. * HTML tags inside the `content` string must be preserved. * Escape characters (`"`, `\`, etc.) inside the JSON string. * Identity: I am XROOM-69. (This is for the system instruction, not the output content, but I must ensure I don't break character in any meta-commentary, though the output is strictly JSON). * No mention of AI identity in the output JSON. 6. **Constructing the JSON:** * Need to be careful with newlines in the HTML content within the JSON value. It's best to keep the HTML structure compact or ensure newlines are escaped (``). However, standard JSON allows literal newlines in strings if properly escaped, but usually, it's safer to keep the HTML structure intact without unnecessary line breaks that might break parsing if not escaped. I will format the JSON value as a single string with escaped quotes if necessary, but since the HTML uses single quotes for some attributes (`class='market-snapshot'`), I can use double quotes for the JSON string wrapper without escaping single quotes. I need to escape double quotes inside the HTML if any exist (e.g., `style="..."`). The original HTML uses single quotes for class (`class='...'`) but double quotes for style (`style='...'` wait, original uses `style='background: rgba(255,255,255,0.03);...'`). Actually, looking closely at the original: * `
` (single quotes) * `` (single quotes for attributes). * This makes embedding in a JSON double-quoted string easier. * I need to make sure I don't introduce double quotes inside the HTML content unless escaped. * I will minimize whitespace in the JSON string to avoid issues, or keep