`, `
`, `
- `, `
- `, ``, ``, `
`, `class`, `style`. 5. **Reviewing Constraints:** * JSON output only. * No markdown code blocks around the JSON (usually preferred for strict JSON parsing, but often wrapped in ```json for readability. The prompt says "RESPOND IN JSON". I will output raw JSON text to be safe, or wrapped in code block if standard practice. Usually, for API-like responses, raw JSON is best. However, as a chat model, wrapping in ```json is standard for clarity. I will check the prompt "RESPOND IN JSON". I will provide the JSON block.) * Actually, looking at the system instruction "IDENTITY REMINDER", I need to make sure I don't slip up. But the task is translation. * Ensure all numbers ($94,500, percentages) are untouched. * Ensure class names (`market-snapshot`, `health-indicators`) are untouched. * Ensure style attributes are untouched. 6. **Constructing the JSON:** * Escape quotes within the content string properly. * Ensure newlines are handled (usually JSON strings shouldn't have literal newlines, they should be ``). However, since the content is HTML, it can contain newlines for readability within the string value, but strictly speaking, JSON strings should escape them. To be safe and valid JSON, I will minimize whitespace inside the string or escape newlines. Actually, standard practice for HTML content in JSON is to keep it as a single line string or escape newlines. I will keep the HTML structure intact within the string value. * *Self-Correction on JSON:* To ensure valid JSON, I need to escape double quotes inside the HTML attributes (e.g., `class='market-snapshot'` uses single quotes, which is good. `style='...'` uses single quotes. If there are double quotes inside the HTML, I need to escape them. The provided HTML uses single quotes for attributes mostly, but I need to check. * Input HTML: `
` (Single quotes - safe). * Input HTML: `` (Single quotes - safe). * I will wrap the HTML content in the JSON value. I need to make sure I don't introduce unescaped double quotes. I will use single quotes for the HTML attributes as provided. * I need to make sure the JSON itself uses double quotes for keys and string values. 7. **Final Polish (Turkish):** * Ensure "Altcoins" translates naturally -> "Altcoinler". * Ensure "Liquidity Inflow" -> "Likidite Girişi". * Ensure "Market Cap" -> "Piyasa Değeri". * Ensure "Fear & Greed Index" -> "Korku ve Açgözlülük Endeksi". * Ensure "HODLer" stays "HODLer". * Ensure "DXY", "RSI", "BTC", "ETH" stay same. * Ensure tone is professional. * *Title:* Bitcoin, Likidite Girişiyle Altcoinler Keskin Kazançlar Kaydederken Düşüşü Durdurdu * *Meta:* Bitcoin, likidite rahatlamasıyla altcoinler yükselirken mütevazı kazançlarla stabilize oldu. Makro gerilimler ve zayıf genel likidite koşulları nedeniyle piyasa trendi kırılgan kalıyor. * *Content Check:* * "Executive Summary" -> "Yönetici Özeti" * "What Happened" -> "Ne Oldu" * "Market Data Snapshot" -> "Piyasa Verileri Anlık Görünüm" * "Primary Asset" ->