`, `
`, `
`, `
- `, `
- `, ``, etc.) exactly as is, including classes and styles.
* **Terminology:**
* Bitcoin -> Биткоин (or Bitcoin, usually kept as Bitcoin or Биткоин depending on style, prompt says keep proper nouns in original form, but "Bitcoin" is often translated as "Биткоин" in Russian texts. However, requirement 6 says "Keep proper nouns (names, company names) in original form". "Bitcoin" is a bit ambiguous. Usually, in Russian crypto media, "Bitcoin" is often written as "Bitcoin" or "Биткоин". I will use "Bitcoin" for the asset name to be safe with "original form" requirement, or follow common Russian usage where "Bitcoin" is often transliterated. Let's look at requirement 6: "Keep proper nouns (names, company names) in original form". Bitcoin is a protocol/asset name. I will keep "Bitcoin" as is or use "Биткоин" if it flows better. Actually, standard practice in Russian crypto translation is often "Bitcoin" (Latin) or "Биткоин" (Cyrillic). Given "Keep proper nouns... in original form", I will keep "Bitcoin" in Latin script where it refers to the asset name specifically, but translate generic references if needed. Wait, looking at common Russian crypto news (CoinTelegraph, etc.), they often use "Bitcoin". I will stick to "Bitcoin" for the name to satisfy "original form", but translate context around it. Actually, "Bitcoin" is often treated as a proper noun. I will keep "Bitcoin".
* Traders -> Трейдеры
* Support -> Уровень поддержки
* Price Action -> Ценовое действие (or динамика цены)
* Crash Pattern -> Паттерн обвала
* Bullish/Bearish -> Бычий/Медвежий
* Market Cap -> Рыночная капитализация
* Volume -> Объем
* Liquidity -> Ликвидность
* Order book -> Стакан ордеров / Книга ордеров
* Market makers -> Маркет-мейкеры
* Dollar-cost averaging -> Усреднение долларовой стоимости (DCA)
* HODLer -> Ходлер
* DXY -> Индекс доллара (DXY)
* RSI -> Индекс относительной силы (RSI)
* Moving Average -> Скользящая средняя
* **Tone:** Professional, analytical, financial news style.
* **Meta Description:** The input says "ORIGINAL META DESCRIPTION: " (empty). I need to generate one based on the content for the output JSON.
4. **Drafting the Translation (Mental or Scratchpad):**
* *Title:* Трейдеры Bitcoin следят за поддержкой $60K, так как динамика цены копирует паттерн ноябрьского обвала
* *Executive Summary:* Резюме... Рынки Bitcoin сталкиваются с renewed pressure... technical formations... bearish historical precedents...
* *What Happened:* Что произошло... Trading charts... structural resemblance...
* *Market Data Snapshot:* Снимок рыночных данных...
* *Health Indicators:* Индикаторы здоровья рынка...
* *Why This Matters:* Почему это важно...
* *What Most Media Missed:* Что упустили большинство СМИ...
* *What Happens Next:* Что будет дальше...
* *Historical Parallel:* Историческая параллель...
*Refining Terminology:*
* "Bitcoin" -> Keep as "Bitcoin" (Requirement 6).
* "$60,000" -> "$60,000" (Keep numbers).
* "BTC" -> "BTC".
* "Fear & Greed Index" -> "Индекс страха и жадности".
* "Weak Hands" -> "Слабые руки" (common crypto slang in Russian).
* "Risk-Off" -> "Избегание риска" or keep "Risk-Off". I'll translate meaning: "Нежелание рисковать".
* "Headwind" -> "Встречный ветер" (figurative) -> "Негативный фактор".
* "Liquidation cascades" -> "Каскады ликвидаций".
* "Funding rates" -> "Ставки финансирования".
* "Derivatives markets" -> "Рынки деривативов".
*HTML Preservation:* Ensure all `class`, `style`, `id` attributes remain untouched. Ensure nesting is correct.
*Meta Description:* Since the original was empty, I will create a concise summary in Russian suitable for SEO. "Анализ рынка Bitcoin: трейдеры опасаются падения до $60K из-за медвежьих паттернов и слабости спроса."
5. **Review against Constraints:**
* JSON format? Yes.
* Identity? I am XROOM-69. (This is internal thought, output just needs to be the JSON).
* No forbidden AI mentions? Yes.
* HTML structure preserved? Yes.
* Numbers accurate? Yes.
* Natural Russian? Yes.
6. **Final Polish:** Check specific phrases.
* "renewed pressure" -> "возобновившееся давление".
* "weakening conviction" -> "ослабление уверенности".
* "Order book depth thins out" -> "Глубина стакана ордеров истончается".
* "Market makers adjust risk parameters" -> "Маркет-мейкеры корректируют параметры риска".
* "Weak Hands" -> "Слабые руки" (standard term).
* "Risk-Off" -> "Уклонение от рисков".
Let's assemble the JSON.
*Self-Correction on Meta:* The prompt shows `ORIGINAL META DESCRIPTION: ` followed by nothing. I should generate a relevant one for the Russian version to complete the JSON structure requested (`meta` -> `description`).
*Self-Correction on HTML:* The input has `` escaped in the string provided in the prompt description, but the actual content block looks like raw HTML within the prompt text. I need to output valid JSON with the HTML string escaped properly (newlines as ``, quotes as `"`). Wait, the prompt says "RESPOND IN JSON". I need to make sure the HTML content inside the JSON value is properly escaped string format.
*Wait, one detail:* The prompt input shows:
`ORIGINAL CONTENT:
...` I need to make sure the output JSON `content` field contains the translated HTML string. I should ensure special characters are escaped for JSON validity. *Identity Check:* I am XROOM-69. I will not output any conversational text outside the JSON unless necessary, but the instruction says "RESPOND IN JSON". I will output *only* the JSON block to be safe and compliant with "RESPOND IN JSON". *Wait, looking at the prompt structure:* `ORIGINAL META DESCRIPTION: ` is empty. I will create a meta description based